YES!  It took me forever to figure out it was Webroot causing the issue.  But I can now recognize the problem and an uninstall/reinstall of Webroot does the trick.  I have about 110 endpoints and only had this happen twice.  What’s strange… in both instances they were new machines with fresh installs of Windows 10.  They worked fine when I built them, but Chrome stopped working once I gave them to the customer.  Once I uninstalled and reinstalled Webroot, the problem went away.  

Is there anything in log files or that gets reported in some alert that you know of? Or do we just have to recognize this and know that’s likely the issue?

I haven’t dug into this issue with support or looked at the logs, to be honest.  In both cases, I just needed to fix it  right away for the customer.  I wish I could reproduce it on one of my machines so that I could work with support to help them identify the issue.

I should clarify- there was nothing present in the Windows Events that I could find.  I never dug into the Webroot logs, though.

I have also experienced this exact same thing on new Windows 10 machines in the last year a few times.