How to fix Google Chrome not working with Symantec Endpoint

How to fix Google Chromium-plate not workings with Symantec Endpoint

Matthew is a freelancer who has produced a form of articles along several topics related to technology. His main focus is the Windows OS and all the things surrounding information technology. He is impassioned near... Read more

In October 2019, users started posting connected the Symantec indorse forum about an Aw Snap error that arises in Chromium-plate when they start the web browser.

The Aw Snap crash error isn't something inexperienced. However, in this showcase, it occurs because Chrome 78 and 79 are not compatible with Symantec Endpoint Security software versions.

The inconsistency issue arises on any Windows political program that includes a Symantec Endpoint version that predates 14.2 RU2 MP1.

The issue largely pertains to Windows 2016 and Windows 10 RS1 platforms with SEP and Google Chrome browsers installed. Note, however, that Edge Chromium 78 and 79 are too incompatible with Symantec Endpoint Protection.

How can I fix Chromium-plate's incompatibility with Symantec Endpoint?

1. Update Symantec Endpoint Aegis

Symantec's official fix for SEP's Chrome incompatibility is to update Symantec Endpoint to the a la mode 14.2 version.

You can get the stylish patch update for Terminus Protection (build 5569) from the RU2 MP1 client-only patches Thomas Nelson Page. That Thomas Nelson Page includes instructions for how you can download the current patch and update the software with it.

2. Deactivate Chrome's renderer code

Right-click Google Chrome's desktop crosscut and select Properties.
Select the Shortcut tab.
Then enter the followers line in the Target textual matter box every bit shown directly below:
- -disable-features=RendererCodeIntegrity
Blue-ribbon the Apply option.
Click the OK button.

If you'atomic number 75 fed up Google Chromium-plate's incompatibilities, check out this article for some good alternatives

3. Edit the registry

Press the Windows key + R hotkey, which opens Run.
Stimulation 'regedit' in the Unstoppered corner and press Enter to open the Registry Editor.
Attend this register key: HKLM > Package > Policies > Google Chromium-plate.
Treble-click the RendererCodeIntegrityEnabled DWORD on the right of the window.
Variety its evaluate to 0 in the Edit Dword windowpane.
Click the OK selection.

If you stimulate issues opening the Registry Editor program, check out this detailed guide for some quick fixes.

4. Found Chrome with no sandbox

Right-click a shortcut icon for Chrome happening the screen background and select Properties.
Click the Shortcut tab connected the windowpane that opens.
Past add –no-sandpile to end of the Target box as below
Select the Apply alternative.
Dawn the OK button.

Edit Chrome's exe file cabinet title

Launch File Explorer with the Windows key + E keyboard shortcut.
Open the folder that includes Chrome's EXE file.
Right-clink Chrome's EXE and select Rename.
Enter Chrome as the new file title, but don't change the EXE data format at the end.

Those are a fewer of the resolutions confirmed to fix Google Chrome's Aw Snap inconsistency error with Symantec Endpoint.

Remember, however, that you can always swop to browsers that don't have whatsoever compatibility issues with Endpoint Protection, so much as Firefox or Opera.

Which one of the many solutions traded above fixed the issue for you? Let us experience by leaving a message in the comment scetion below.