Thanks Kita. I've applied the workaround and it seems to work. ... View more

Found a workaround from link below to stop rempl, you may already know of it but it does work so far for me. I have 4023057 but remsh is still at 10019. The article below references 10020, but not sure how to get that.   https://support.microsoft.com/en-us/help/4098563/usb-device-drivers-are-removed-unexpectedly-after-windows-update-windo   USB device drivers are removed unexpectedly after Windows 10 is updated The applicability rules for the Windows update reliability tool have been improved. In addition, the latest version of this tool (10.0.14393.10020 or a later version) should not cause the issue. As a workaround, you can completely block the update reliability tool from running. To do this, run the following commands: takeown /f "C:\Program Files\rempl" /r /d y icacls "C:\Program Files\rempl" /grant administrators:F /t /q icacls "C:\Program Files\rempl" /deny system:F /t /q ... View more

Sorry, meant 4023057. ... View more

The million dollar question seems to be how to get the .20 version of remsh. We have 4023957 but remsh is still at .19. Does anyone here have remsh .20 and if so how did you get it? ... View more

Okay Pretambey, I was able to reproduce this. The shell portion triggers at 10am every day, so I wonder if this is the only task messing with the driverstore. The shell-unlock is triggered on workstation lock/unlock but my test PC had been thru this many times and still Pulse worked. I'll mess with it more and post any findings. ... View more

Thanks Pretambey. Just this morining my no-SEP machine gave the 1205, so like you've seen it does not appear to be SEP clobbering Pulse. Another check we did was with our Win7 boxes; same SEP/Pulse versions together and they have been and keep working perfectly. I'll try your suggestion and reply with reults, thanks. ... View more