![]() ![]() I do however have unmistakable evidence on my side that after having set both Chrome and Firefox to 'Allow' under Application Protection, that I am now able to use both browsers without any problem. How do you explain the many users this is affecting who aren't running I understand your reasoning. After reading all the posts in that thread, I'm thinking this is more a Windows/Browser problem than a Webroot one. How do you explain the many users this is affecting who aren't running funny. ![]() This off course is not an ideal solution as Chrome.exe is then no longer protected by Webroot. Webroot has to be Shutdown, and then re-launched. I have tried to just set it to 'Allow' without restarting Webroot, but that doesn't work. After re-launching Webroot, I'm able to use Chrome with the Task Manager open and it's working fine without freezing up. Customer reading the last few posts from this Microsoft Forum:, I can confirm that the problem is definately to do with the way Webroot's Identity Protection 'Protects' Chrome (and possibly firefox as well).Ī work-a-round is to temporarily change the ' chrome.exe' entry in Webroot's ' Identity Protection' > 'Application Protection', from 'Protect' to ' Allow', then right click Webroot and choose ' Shut Down Protection'.OpenText NetIQ Advanced Authentication Tips & Info 0.OpenText NetIQ Access Manager User Discussions 0.OpenText NetIQ Self Service Password Reset 0. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |