Webroot chrome

Webroot chrome DEFAULT

Beginning yesterday and spreading today, Windows 10 Pro users on our network are suddenly unable to launch Google Chrome. When looking at Task Manager Chrome is running and each time the user attempts to open it another instance appears in task manager. Closing Chrome from the notification bar doesn't have any impact. Ending task on each instance in Task Manager doesn't fix things. Uninstalling and reinstalling doesn't fix things. The only thing I've found that will fix things (though not an elegant solution) is browsing to the installation (C:\Program Files\Google\Chrome\Application) and renaming the application and pointing shortcuts to the new name and then rebooting. The problem with that fix is, while I can point the icon for the shortcut to the changed program, when the program loads a blank icon appears on the task bar. Is anyone else having this problem? Anyone know why this is occurring? Anyone know how to fix it more elegantly than what I've come up with?


Best Answer

arielbenjamin

Poblano

OP

Thanks for you help, jcLAMBERT​. To answer your question--no Chrome related GPOs.

Looks like I have found the answer. I spoke to a colleague the other day who told me that a couple of months back he had a similar issue. After struggling with it for a while he gave up and moved his users to a different browser. Then, after a couple of weeks, users reported that Chrome suddenly worked again. He and I compared configs and found only one common denominator: Webroot (anti-virus). 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. 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.

The issue is in their Identity Protection. The solution is to manually exclude chrome.exe from that protection from within the Webroot management console. To do that one selects the computer or computers in their organization to apply the exclusion, then select Agent Commands::Identity Shield::Allow Application. That will bring you to a popup that needs the MD5 for the program. 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. When the scan finishes there will be a button to "Save Scan Log" which creates a text file of the log. In that log there will be a line that includes both the SHA256 and MD5 hashes. 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.

There is one snag, however--the MD5 is different for each version of Chrome. 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. 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. Anyhow... at least this is better than the previous (name-change) fix. Thanks again for your help!

View this "Best Answer" in the replies below »

12 Replies

· · ·

jcLAMBERT

Habanero

OP

  • Kill Chrome instances.
  • Look under %localappdata%\Google\Chrome.  Rename the user data directory.  
  • Relaunch Chrome

1

· · ·

arielbenjamin

Poblano

OP

Thanks jcLAMBERT for your quick response. That worked for the first time launch after performing that task, but if the user closes the browser and reopen the original problem returns. This seems to suggest that the User Data folder is corrupted each time, right? Any idea how to determine what might be behind that?

0

· · ·

jcLAMBERT

Habanero

OP

Are the user's signing into Chrome?  If so, then the reason for your issue is probably syncing in the background..  After they logon successfully, try doing a reset within the browser.  Then tweak the UI.  Now, close and reopen

1

· · ·

arielbenjamin

Poblano

OP

I had a user who was logging in and another who wasn't and tried resetting in both following the renaming of the user data folder. No luck. Same result following the change and opening once successfully, closing and attempting to reopen and having it not open the second time.

0

· · ·

arielbenjamin

Poblano

OP

Here's another symptom. Performing the name change breaks the connection in programs like Outlook. Now if the user, after doing the name-change, attempts to click on a link from inside outlook they get a " Your organization's policies are preventing us from completing this action for you. For more info, please contact your help desk." error message. If we change the default browser to another, links open just fine (in other words, no group policy on this domain preventing users from opening links). If we switch back to chrome the error returns about policies. Sounds like that further points to something going wrong under the hood in chrome. Thoughts?

0

· · ·

jcLAMBERT

Habanero

OP

Do you have a Chrome related GPO?

0

· · ·

arielbenjamin

Poblano

OP

Best Answer

Thanks for you help, jcLAMBERT​. To answer your question--no Chrome related GPOs.

Looks like I have found the answer. I spoke to a colleague the other day who told me that a couple of months back he had a similar issue. After struggling with it for a while he gave up and moved his users to a different browser. Then, after a couple of weeks, users reported that Chrome suddenly worked again. He and I compared configs and found only one common denominator: Webroot (anti-virus). 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. 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.

The issue is in their Identity Protection. The solution is to manually exclude chrome.exe from that protection from within the Webroot management console. To do that one selects the computer or computers in their organization to apply the exclusion, then select Agent Commands::Identity Shield::Allow Application. That will bring you to a popup that needs the MD5 for the program. 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. When the scan finishes there will be a button to "Save Scan Log" which creates a text file of the log. In that log there will be a line that includes both the SHA256 and MD5 hashes. 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.

There is one snag, however--the MD5 is different for each version of Chrome. 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. 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. Anyhow... at least this is better than the previous (name-change) fix. Thanks again for your help!

3

· · ·

jcLAMBERT

Habanero

OP

Hmm.  We are also Webroot users, and haven't seen an issue in over a year with Chrome.  I wonder if you can move a specific PC to a special group  and tweak the associated profile until it works. 
Maybe Webroot has some insight into the component/setting that may be flagging things

0

· · ·

arielbenjamin

Poblano

OP

Not sure. Strangest thing is we just replaced the computers so we are talking about brand new machines that aren't running much yet. Webroot has a team working on this issue but one of the biggest problems is that the problem seems to be randomly manifested. Even in our environment we've got 30 machines identically configured and fewer than half have had this problem. 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). 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. 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. Still--very odd thinking about this. Usually what I like about computers is predictability. Can't wait to learn the actual pattern here.

1

· · ·

spicehead-l118p

Pimiento

OP

My google chrome was not opening and I had just got my psu upgraded with a local pc response shop and once I got it back I was terrified that he has caused the issue. Then I changed chrome.exe from protect to allow in the webroot identity protection and now it works. I’m so glad I found your response, now I know my pc is running fine. What’s odd is I have webroot installed on other PCs with chrome and there’s no issue whatsoever. I hope webroot finds a solution soon.

1

· · ·

WNI

Sonora

OP

FYI, I did find another "fix", although it's far from perfect.

If you put a command-line switch at the end of the launch command for it, it will work. It doesn't matter what the switch says. Mine currently uses /thisisstupid. But for some reason, the switch seems to allow it to launch.

The problem is with this solution is that it doesn't fix not having a command-line to add the switch to. So, putting Chrome on your taskbar? Not going to work. Setting Chrome as your default browser? Not going to help. So it's of limited utility, but it was an interesting discovery.

0

· · ·

Oldsmobile_Mike

Thai Pepper

OP

Saw Webroot released build 9.0.31.84 on Sept. 28th. I didn't see any notification about the update, just happened to notice it when I saw four of my systems had updated to it. Googled the release notes and it appears they've included more bugfixes for the issue with Chrome not loading when Identity Shield is enabled. Let's hope they got it right this time!

1

Sours: https://community.spiceworks.com/topic/2303167-chrome-suddenly-won-t-load
Summary
Chrome not starting on Windows devices with Webroot installed.

Product Information & Environment
Google Chrome, Webroot SecureAnywhere and Microsoft Windows

Status: Open

Description
An issue has been reported where the Webroot agent may prevent Google Chrome from starting. Webroot is aware of this problem and is investigating a permanent solution.

Workaround
Creating an Identity (ID) Shield override for chrome.exe has been shown to resolve the issue. This workaround is effective until Chrome is updated. When that happens, a new override needs to be issued to cover the new version of chrome.exe.

Creating an ID Shield override 
To be notified once a permanent fix has been released, open a Support ticket.

Thanks for your feedback!

All Contents Copyright © 2021

Powered by noHold, Inc. U.S. Patent No. 10,659,398

Sours: https://answers.webroot.com/Webroot/ukp.aspx?pid=17&vw=1&app=vw&solutionid=1916
  1. Are foxes cannibals
  2. Filipino traditional dress female
  3. Dana sawyer tennessee
  4. Sherwin williams cadet
  5. Universal socket walmart
Summary
Google Chrome not starting on Windows devices with Webroot SecureAnywhere installed.

Product Information & Environment
Google Chrome, Webroot Business Endpoint Protection and Microsoft Windows

Status:Open

Description
An issue has been reported where Google Chrome may not start on some systems where both Google Chrome and the Webroot Business agent is installed. Webroot is aware of this problem and is investigating a permanent solution.

Workaround
Creating an ID Shield override for chrome.exe has been shown to resolve the issue. This workaround is effective until Chrome is updated. When that happens, a new override needs to be issued to cover the new version of chrome.exe.

+Using the Webroot agent to create the ID Shield override
Note: In order for the agent to allow these actions, the Unmanaged endpoint policy needs to be applied. For help with endpoint policies, see:
  1. Open the Webroot agent.
     
  2. Click the gear icon next to Identity Protection.
     
  3. Select the Application Protection tab.
     
  4. Find chrome.exe in the Application list and change the setting to Allow.
     
  5. Provide the required input and click Continue.
     
  6. The override becomes active immediately, no reboot is needed.

+Adding the ID Shield override using the Webroot Management console
  1. Log in to the Webroot Management console.
     
  2. Find the site that you want to modify.
     
  3. On the right side of the screen under Subscriptions, hover your mouse over the E to open the Endpoint Protection call-out, then click the box and arrow icon to open the Endpoint Protection console.
     
  4. In the Endpoint Protection console, select the Group Management sub-tab, then click the Group that contains the devices that need ID Shield overrides.
     
  5. Check the boxes for the devices, click the Agent Commands drop-down menu, choose Identity Shield, then Allow Application.
     
  6. Enter the MD5 for chrome.exe and click Submit.
     

    To find the MD5 of a file

    1. Right-click the file and select Scan with Webroot.
    2. When the Scan Results window appears, click Save Scan Log in the bottom left.
    3. Name the file and save it to the desired location. This log contains the MD5 value of the file scanned.
      
  7. Agent commands are received and processed by devices as they check-in.
    • For information on forcing a device to check-in, click here.

 
To be notified once a permanent fix has been released, click hereto open a Support ticket.

Thanks for your feedback!

All Contents Copyright © 2021

Powered by noHold, Inc. U.S. Patent No. 10,659,398

Sours: https://answers.webroot.com/Webroot/ukp.aspx?pid=17&app=vw&vw=1&solutionid=3997&t=Chrome-not-starting-on-Windows-devices-when-Webroot-is-installed-Business
Chrome Does Not Open - Could Be Anti-Virus

Webroot® for Chromebook

Webroot® Security for Chromebook™ offers powerful protection specifically designed for Chromebook to proactively protect you and your kids from the latest cyber threats.

The enhanced antivirus protection is always on, running seamlessly in the background and alerting you about malicious activity. Use Webroot’s proprietary secure browser to run on-demand scans and browse safely or download Webroot Web Threat Shield to be alerted of dangerous sites while browsing in Google Chrome™.

Top Features:

Enhanced Antivirus Protection: Always-on, automatic scans of your device and files for viruses and malware.
On-Demand Scans: Leverage the Webroot browser interface to easily run additional on-demand scans at the click of a button.
Identity Protection: Blocks malicious websites that try to steal your personal info or harm your device.
Made for Chromebook: Extra security that’s specifically designed to protect your Chromebook™ and close any security gaps.
Secure Web Browsing: Identifies and blocks unsafe websites while using the Webroot browser or Google Chrome™.

After installing and opening the app, you will be prompted to create a customer account using your keycode, email, and password. Your keycode is provided in your purchase receipt.

Download Webroot Web Threat Shield to safely browse while using Google Chrome™. Web Threat Shield warns you about high-risk websites before you click, and automatically blocks bad ones trying to install anything dangerous on your Chromebook. Download the extension from the Chrome Web Store.

An Extra Layer of Protection:

Chromebook’s built-in security offers only limited protection against malware and phishing attacks. Webroot offers full protection against fake apps, malicious downloads and unsafe websites.

Webroot® Security for Chromebook™ is tailored for the Chromebook operating system, so you know you’re getting ideal protection for your device. It proactively alerts and protects you from security threats, providing extra security features and identity protection for ultimate peace of mind.

Webroot uses machine learning and artificial intelligence backed by 20 years of historical data and experience to provide the most advanced protection available for your Chromebook device.

Download today!

Sours: https://play.google.com/

Chrome webroot

.

Safer Searches With Webroot Browser Extension - Detected Malware Website Example

.

You will also like:

.



367 368 369 370 371