How to Fix Google Chrome Not Working With Symantec Endpoint

Browsers give us the comfort of browsing various things round the clock. There are various protection suites available in the digital market that is appreciated by users. One such security software suite is “Symantec Endpoint” developed by Broadcom Inc. However, while using this software, some of the users face various issues. One of the prominent issues among them is the “Aw Snap” crash error. This error arises on launching browsers, especially Google Chrome, and the prominent reason is incompatibility with endpoint security of Symantec software edition.

These error issues occur on various versions of Chrome, such as 78 and 79, and can appear on any of the Windows platforms consisting of Symantec Endpoint edition dated back to 14.2 RU2 MP1. This error is also seen in various Chrome editions, such as 78 and 79.

Updating Symantec Endpoint Protection

The issue of the Google Chrome incompatibility issue can be fixed by updating the latest edition of Symantec Endpoint 14.2. One can navigate to the patch page of RU2 MP1 for updating Endpoint protection. Install the latest and recently updated patch of the Endpoint and update the same for better functioning.

Abide by the offered instructions to fix this error issue on Google Chrome browser:

Deactivating Google Chrome-based Renderer Code

• In the beginning, apply right click on the desktop shortcut of Google Chrome.
• Now, hit the Properties tab there.
• Hit the “Shortcut” section.
• Now, insert these keywords into the provided text bar:

“- disable-_features=Renderer_Code_Integrity.”

• After that, tap on Apply.
• Next, hit the “OK” tab to proceed.

Modifying Registry Entries

• Firstly, hit Window logo and R keys at one go to launch the Run dialog box.
• Now, type the keyword “Regedit” into the text box, followed by the Enter key. This action will launch the Registry Editor window on your screen.
• Next, navigate to the registry key “HKLM.” Then, hit the Software tab.
• After that, tap on the Policies option.
• Hit the tab, “Google Chrome.”
• Locate the DWORD option “Renderer_Code_Integrity_Enabled” and double click on it. This option will be situated on the right-hand side of your desktop screen.
• After that, change the data value to “0” in the editing section.
• Next, press the OK button to proceed.

Note: In case you are facing issues in launching your Registry Editor page, then you can take the support of a detailed guide as a help.

Opening Google Chrome Having Sandbox Disabled

• First of all, search the Google Chrome icon and then apply right-click on it. It will be located somewhere on your desktop or apps section.
• After that, press the option “Properties.”
• A new window will expand on your desktop, then click on the Shortcut tab there.
• Navigate to the targeted box and add “no-sandbox” into the provided bar.
• Now, press the Apply tab to proceed.
• Next, hit on OK to save all the changes.

Editing the Title of Google Chrome Extension File

• In the beginning, open File Explorer by pressing Window and E keys simultaneously.
• Next, launch the Google Chrome EXE file directory.
• After that, apply the right mouse click on the EXE file, and after that, choose the option “Rename.”
• Then, insert the keyword “Chrome” into the provided file title name box.

Note: It is recommended not to modify the format of EXE at last. One can switch to your desired web browser that is not flashing such an error. You can expand any of your preferred browsers like Opera or Mozilla Firefox.

Aida Martin is a creative person who has been writing blogs and articles about cybersecurity. She writes about the latest updates regarding mcafee.com/activate and how it can improve the work experience of users. Her articles have been published in many popular e-magazines, blogs, and websites.

Source:- https://truemcafee.com/how-to-fix-google-chrome-not-working-with-symantec-endpoint/