A few years back I already wrote about picadm.sys issues: https://www.carlwebster.com/the-curious-case-of-the-slow-file-transfer/

Citrix has been updating picadm.sys numerous times since then, and also did in the latest release: HRP06. And before that in XA650R05W2K8R2X64015 too.

However, it seems that XA650R05W2K8R2X64015 introduced a new(?) bug, that was also present in HRP06. That’s actually quite logical as HRP06 supersedes XA650R05W2K8R2X64015, so XA650R05W2K8R2X64015 is included in HRP06.

Just try this PowerShell oneliner in a XenApp session with client drives enabled and see for yourself:

get-process | out-file -filepath “\\client\c$\temp\proclist3.txt” -Append

Obviously, you need to have a c:\temp folder for this to work.

The first time you run this, a file will be created.

When running this a second the time you will find that the file on your c:\temp is not updated. Most of the time it will also throw an error: Out-File : The handle is invalid.

The HRP06 version throws an error but XA650R05W2K8R2X64015 just does “nothing”.

Uninstalling XA650R05W2K8R2X64015 resolves the problem, I have not yet uninstalled HRP06 yet.

So… what’s next? I didn’t recommend installing HRP06 yet anyway, you should wait for XA650R06W2K8R2X64001, which contains the fix for rpm.dll crashes.

But in the meantime, I’ve opend yet another Citrix Support Case on picadm.sys. Let’s hope it gets resolved faster now…

Thanks

Bart Jacobs

I have been looking at this announcement with a kind of special interest, my first curious case, which you can read here.

And what did I see in the presentation?

What does Citrix mean by this? “Some customers have reported issues in Client Drive Mapping related performance, and this is vastly improved in FP2.”

Way to go, Citrix! But wait a minute… Citrix just turned a bugfix into a feature…what’s up with that?

In the end, let us all hope that we can finally resolve the issue at stake here. It’s been too long already.