![]() We are not using VMWARE so the vmware USB monitor reference does not apply. Now for the more recent event: Once eliminating Microsoft updates as a culprit, (bare metaal restore of server just before updates were applied on Sunday morning, we used the forum post link below this paragraph to rename the ctxusbm.sys to sysold. When it happened again yesterday, we re-visited our previous assertion. We made a note of it in 2015 but since it was a one-off event at the time, we moved on. Oddly enough, the blue screen error would persist in safe mode, no network before that driver was disabled in the registry. The first event required Microsoft's intervention to analyze the system registry and remove startup items until the Citrix receiver was identified as the culprit. This happened in 7/2015 on the first client with receiver version 4.7 or 4.9 (not certain on version) and yesterday with version 4.12. ![]() The receiver installed with no incident, but when restarting the server it displayed the PNP_DETECTED_FATAL_ERROR blue screen. We had two different clients running Windows 2012 R2 server with the Microsoft Remote Desktop Services Remote Session Host role and were asked to install the Citrix receiver so that some users could connect to another server for a specific software while inside their Microsoft Remote Desktop Session.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |