PVS Target devices stuck on Shutting Down

[Wayne Fisher1709160944]

Using PVS 2203LTSR on VMWare 6.7 with Windows 10 21H2 and on logoff or when restarting, the target device hangs on Shutting Down or just a blank blue screen, the only way to "recover" the machine is to reset it in VMWare. Using Cache in device RAM with overflow to disk, CD ROM is disconnected and running IDE not SATA. Windows update and CCMexec are disabled

Nothing gets posted in the event log either, 

[Kelan Rowe]

There is a known issue in 2203 LTSR, corrected in 2203 LTSR CU1, where shutdown can have an extra 60-90 seconds added to what might be expected.
The description is a little different, but its the same casue and same fix.
https://docs.citrix.com/en-us/provisioning/2203-ltsr/whats-new/cumulative-update-1/fixed-issues.html
Citrix Provisioning server failover takes a long time when you use a 2203 target device. [CVADHELP-20173]
 

[Wayne Fisher1709160944]

It isn't delaying shutdown, it just doesn't shutdown, I can leave it overnight and the VM is still the same, blue screen or stuck at Shutting Down.

[Kelan Rowe]

There are some reconnect issues also fixed in PVS 2203 CU1, so worthwhile updating to it.

If the issue persists then, can a memory dump be captured once the VM is in that state?
Theres a guide here for VMware, suspend VM, save off vmem and vmss, and convert to dmp
https://kb.vmware.com/s/article/2003941
Then open a support case with citrix then to get it analysed.

[Wayne Fisher1709160944]

Thanks, will update to CU1 and see if the issue persists

[Darryl Sakach]

Have you tried to temporarily disable or uninstall your AV to see if the problem goes away? We have seen this with 2203 and blue screen crashes on restart. With AV the target device crashes on restart, without AV it restarts without issue. We are working on updating our AV exclusions to meet the latest recommendations at https://docs.citrix.com/en-us/tech-zone/build/tech-papers/antivirus-best-practices.html#antivirus-exclusions. 

[Tomas Libenek]

Hi Wayne,

 

we are hitting the same issue, have you found the fix?

Regards,

Peter