Could it be this windows update? https://support.microsoft.com/en-au/help/4098563/usb-device-drivers-are-removed-unexpectedly-after-w...
Let us know if this was it. thanks
Pulse TAC suggested the same fix from that KB. It's a task from task scheduler which seems to be deleting the jnvra drivers. Start task scheduler, Task Scheduler Local -> Task Scheduler Library -> Microsoft -> Windows -> rempl
If you run the two tasks under there, it will start deleting the jnvra drivers. I was able to confirm it when I was using a software to monitor DriverStore folder. However, on my another user's machine, this didn't happen when we ran the tasks manually.
If you can try this and let me know then that would be great. Hopefully others who are having this issue can chime in too.
We did not have that particular KB installed for most of the machines. The last time someone had it installed was in december 2017.
Some further info from other engineers that are working on this issue.
KB4023057 is not a MS patch update instead it an APP. Since it is an APP/Program it will not appear under Installed Updates, instead it will be seen under Installed Programs as shown below:
So it looks like previous versions (older than 10.0.14393.10020) of this reliability tool (C:\Program Files\rempl) from MS is errorneously deleting the drivers for Pulse Secure resulting in the 1205 errors.
If anyone is seeing this issue with newer versions of the relaibility tool as well please let us know.
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?
I do not believe there is a method to download the version 19 of the reliability tool. The MS KB has stated this is not available in the Windows Catalog for download.
At this moment, the recommendation is to apply the workaround suggested by Microsoft to disable the REMPL tool. We are engaging Microsoft to better understand if there is other options outside of what is suggested in the current KB.
Thanks Kita. I've applied the workaround and it seems to work.
Thank you for the confirmation, Corkboard. We are seeing positive results from others as well. We will continue to follow up with Microsoft to understand the root cause and see what Pulse Secure can do to prevent this issue in the future.