To run the health check you need to first download and install Microsoft's PC Health Check app.In case your system meets the above-mentioned criteria, you need to run a health check to keep your system ready to install Windows 11. Can't wait to learn the actual pattern here.(Image credit: Future) Windows 11 compatibility check Usually what I like about computers is predictability. And given that the tinfoil hat I've started wearing (in combination with that exclusion using the md5 for chrome, but I think its the tinfoil that is actually changing things) is working, I think we're now safe until Webroot comes up with a more permanent fix. The only explanation I've come up with is that some disgruntled ex-employee (or maybe current-who am I to judge) has taken up the dark arts and has deployed some sort of computer-equivalent of a voodoo doll that causes random havoc. I can't find any pattern that connects the impacted users and excludes the unimpacted users (which lines up with what Webroot told me yesterday about what they're hearing from other customers). Even in our environment we've got 30 machines identically configured and fewer than half have had this problem. Webroot has a team working on this issue but one of the biggest problems is that the problem seems to be randomly manifested. Strangest thing is we just replaced the computers so we are talking about brand new machines that aren't running much yet. at least this is better than the previous (name-change) fix. Hopefully Webroot gets this fixed soon as this is a major PITA and cost my clients in both downtime and in my time remedying the issue. If it happens that all of the affected users are on the same version, that's not a big deal but as soon as one updates it may break things again and you'll need to add the next version's MD5. There is one snag, however-the MD5 is different for each version of Chrome. Copy the MD5 into that pop up and then have the users right-click on the webroot symbol in their notifications and refresh the configuration. In that log there will be a line that includes both the SHA256 and MD5 hashes. When the scan finishes there will be a button to "Save Scan Log" which creates a text file of the log. The easiest way to generate an MD5 for Chrome is to browse to the application (chrome.exe), right-click it, and select Scan with Webroot. That will bring you to a popup that needs the MD5 for the program. To do that one selects the computer or computers in their organization to apply the exclusion, then select Agent Commands::Identity Shield::Allow Application. The solution is to manually exclude chrome.exe from that protection from within the Webroot management console. The issue is in their Identity Protection.
They reported that the issue is not uniformly appearing-that it pops up seemingly randomly-but that they are working to find a solution and have a working work-around. I called Webroot support today and learned that Webroot has known about this issue for a couple of months but still doesn't have a solution for it. He and I compared configs and found only one common denominator: Webroot (anti-virus). Then, after a couple of weeks, users reported that Chrome suddenly worked again.
After struggling with it for a while he gave up and moved his users to a different browser. I spoke to a colleague the other day who told me that a couple of months back he had a similar issue. To answer your question-no Chrome related GPOs.