So, it appears we are having issues related to the following on multiple clients, multiple endpoints: (Note, we aren't just having the issue on Windows 10; Windows 7 is having issues too, and it appears to do with Winlogon/Netlogon).  We believe it is related to the issue listed below.

 

https://community.webroot.com/t5/Known-Issues-KB/Netlogon-is-not-starting-after-Reboot/ta-p/316119

 

I offered to help our team by writing a script within our RMM software that would set the Registry key per Webroot's recommendations as described in the workaround in the article.  Only one problem:  I cannot create a DWORD to the WKrn service key.  Just for fun, I tried using the same commands to write the IFP key noted by Webroot to another spot in the Windows Registry, and it went off without a hitch, making me think Webroot has set the HKLMSYSTEMCurrentControlSetServicesWKrn key to have specific permissions, preventing me from writing the key.

 

With the affect this is having on multipile clients (we are an MSP), I am hearing rumblings from our tech team about "we should try competing products".  This problem creates all sorts of unpredictable issues, and is a very serious one for us, regarding group policy processing, user logon, file shares, etc.  We have opened Ticket 155126 for the issue; this is a serious priority for us.  It took us the better part of a week to determine that Webroot was the main cause of the issue (and rule out Windows itself).  We also found another person with similar experiences here:

 

https://community.spiceworks.com/topic/2114911-netlogon-5820-endpoint-duplicate-windows-10

 

Is anyone having similar issues where it appears file shares aren't connecting or working properly, or group policy errors are occurring?  This does not make us look good as an MSP to our clients.