Update on July 24th, 2020: The post below is in reference to behavior observed by Windows 10 users during the Chrome M78 and M79 releases, which occurred in late 2019. If you are reading this posting after that time period and are seeing “Aw, Snap!” messages, the root cause of the behavior may be different. We recommend reviewing our help center article for more information.
Hello everyone,
We’re investigating reports of an increase in Aw, Snap! crashes following the Chrome M78 update. If you are experiencing this behavior, please see the following information for assistance.
If you are seeing the behavior on a work computer, or while on a connection provided by your workplace, this may be related to a known incompatibility between Chrome and older versions of Symantec Endpoint Protection. You can reach out to your IT department for more assistance, and share the below:
You should update Symantec Endpoint Protection to version 14.2 or later. You can also disable the added protection that triggers this incompatibility using the RendererCodeIntegrityEnabled policy in Chrome. More information is available in our Enterprise Release Notes.
If you are seeing this behavior on a personal computer at home, additional information will help our team continue to investigate. If you are able, please reply to this thread and share the name and version number of the anti-virus software you use on your computer. Please note that responses are public, so please do not share personal information.
Thanks!
Craig, Chrome Support Manager
Note: This message was edited on December 10th, 2019 to update the title to include M79, and again on July 24th, 2020 to provide an update at the top of the message.
Hey everyone, thanks for taking the time to share your anti-virus information!
We have confirmed that in addition to the known incompatibility with specific versions of Symantec Endpoint Protection, some additional software applications may be causing “Aw, Snap!” messages in the latest Chrome M78 release.
We are investigating reports of incompatibilities with the applications listed below. You can follow along with each of them using the development bug provided:
We have temporarily disabled the new Chrome feature that is resulting in the incompatibility while we partner with these software providers to improve compatibility. If you were affected by the incompatibility of a product listed above, please contact the application’s provider to understand their timelines for a fix.
We plan to re-enable the feature in the near future, and will provide another update here once we have. To ensure you are not affected, please keep software up to date.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
We’re following up to let you know that we plan to enable the underlying feature (Renderer Code Integrity) that resulted in the previous incompatibilities with the release of Chrome M79 today.
We are continuing to partner with affected software providers to improve compatibility. If you begin to see Chrome provide “Aw, Snap!” errors following an update to Chrome M79, we recommend the following:
Ensure all installed anti-virus software is up to date.
Reach out to your anti-virus software provider to understand their compatibility timelines.
If you are able, please reply to this thread and share the name and version number of the anti-virus software you use on your computer.
Please note that responses are public, so please do not share personal information.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
2114
Relevant Answer Relevant Answers (0)
Our automated system analyzes the replies to choose the one that's most likely to answer the question.
On a home PC and Chrome crashes immediately on load created a new profile on the machine and ran the install again and once complete it Aw snapped again. Unable to do much of anything in Chrome to troubleshoot. Windows logs so far have not been helpful.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
I am using PCMatic. I have no idea exactly what version of Chrome since all I get when hitting the 3 dots the Aw Snap message. I think I have the current version as I downloaded it today. I've changed to Firefox which works great.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
IT Manager. We are already on Symantec version 14.2 on all computers and we are experiencing it on only some PCs. So in our case being on 14.2 or later does not matter. Putting Chrome in Windows 8 Compatibility mode has been our work around to get Chrome working.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
I had Mcafee on my computer but also installed PC Matic after my McAfee license expired. I took the McAfee off my computer today. Chrome launched once after that but started to crash again. I uninstalled and reinstalled Chrome today, but it crashed after doing that as well.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
I have Avast anti virus and PC matic installed. Avast auto renewed before I could stop it. I have run both but they found no malware. It all started yesterday
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Same issue on personal laptop and desktop with win 10, and Symantec Endpoint Protection version 14 (140 37521000). Antivirus provided by university software.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Hi Craig, reading on above thread non if your suggestion working..can you or your team provide quick response with solution or else we have to move to Mozilla..
Also request you to introduce update button in chrome... Y he existing one without clicking on update it got updated to newer version...
My 1200 machines are having trouble with latest chrome 78
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Please check this article and make the required registry changes in your machine if upgrade is not possible immediately.If there is users count high please go with GPO deployment.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
I have the aww snap problem. Never heard of Symantec and pretty sure I don't have it installed. My antivirus is PCMatic and I don't know the version number though I just updated it so its current. When I pause pcmatic chrome works again. But if not every page including extensions and settings aw snap me. Hope this helps.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Google user
Recommended Answer
Relevant Answer
Workaround of "Compatibility" fix is currently working fine.
But can not get this done for every user in my organization.
Need permanent resolution to this issue... quickly !!!
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Symantec Endpoint Protection 14.0 over here. We created an exception for the Chrome program folder on the SEP management server (as indicated by the Symantec tech article ) for now until the issue is fixed or we decide to update SEP.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
My chrome has stopped working, and the message "Cisco WebEx Extension has crashed. Click this balloon to reload extension"
I have clicked balloon and it does nothing, I have rebooted computer more than once, turned it off and back on, uninstalled and reinstalled chrome a few times and none of the advice I read works because no buttons within chrome work so I cannot clear browser or extensions...etc
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Close the Chrome browser, and then press "Windows-E" on the keyboard to launch Windows Explorer.
Enter "%LOCALAPPDATA%\Google\Chrome\User Data\" (without quotes) in the address bar at the top of the window.
Find the folder named "Default" in the window that opens, right-click the folder and select "Rename." Name the folder "Backup Default" (without quotes).
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
worked using User 17539290470823488439's suggestion. Set Compatibility to Windows 8. chrome.exe > right-click > properties > compatibility tab > "Change settings for all users" (because it reverts back after session) > Run this program compatibility for: Windows 8.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Open Taskmanager and END TASK all the Google Chrome processes, after this right-click on Chrome shortcut and go to Properties. At the end of Target field, type this: -no-sandbox Then click on apply and close Properties and reopen Chrome.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Apparently everything I write in here is against community policy. Even the solution, well done Google. (Originaly the sentence below was supposed to be in this post, but it's against community policy)
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Laptop running SEP 14.2. Chrome crashes on startup consistently. Temporary yWorkaround: Changed name of application to Chrome1.exe (workaround suggested on another thread) & it runs correctly!
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Seriously! Over 24 hours now and still no sign of a fix?? This is ridiculous
Mixture of computers in a business environment, none using Symantec protection at all, this issue is not related to Symantec.
Webroot AV here, Chrome Version 78.0.3904.70
Compatibility mode works but that's not a practical solutions, users switching over to Edge now and will probably never go back to Chrome! Well done Google!!
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
IT University college here: we have tons of users (+1000) who are using google chrome. Steadily they're contacting servicedesk with this issue. We're being swamped here. Please provide a solution asap!
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
I had the same issue as soon as I opened Google chrome this morning. I have a work PC, and I have just upgraded my Symantec to 14.2 and restarted my PC. Before opening google chrome, I uninstalled google chrome and restarted my PC again. I then installed the google chrome and its all working fine now. If this helps :)
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
NO matter the Key reg or other the only workaround I've found was to uninstall M78, install another previous version ( in example Enterprise 77) and as soon the installation is completed, open msconfig from start exevcute ( with admin rights ) and in services disable the Google Updates Services, then reboot.
Chrome will work and auto updates will be blocked.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Google user
Recommended Answer
Relevant Answer
My whole company is using the Symantec Endpoint Protection 14.2 but only 5-10 people out of 1000 have this issue. I can guess that some of them didn't upgrade chrome yet but even my pc and (other IT people around me) upgraded chrome and they didn't have this issue.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
For me it was caused by the PC Matic Super Shield. I was able to temporarily pause Supershield on my machine and load any number of tabs, which I can then use, even after Supershield is turned back on but as soon as I turn Supershield on any new tabs crash when they open.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
I have mad many users having this issue, reinstalling seems to fix the problem
Edit: I have now had at least 50+ users affected by this update, None of these users are using SEP or any Symantec products. Just running the Chrome installer corrects the issue, don't even need to uninstall
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
I'm experiencing Aw Snap error with 2 machines in my workplace. I tried all above TS with no luck!. I cleared the Cache files, uninstall/install. Updated SEP and disabled SEP. Nothing fixes it.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
PC Matic. Aw Snap message says adobe acrobat is missing and execution file or something like that. I have repeatedly downloaded Chrome but it fails to open after download and sends the same message again.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
I work in the Ti department and we have some computers with the Chrome issue, we checked the SEP version and so far we are working with chrome in compatibility mode, let's try using the command line:
"HKEY_LOCAL_MACHINE \ SOFTWARE \ Policies \ Google \ Chrome" / V RendererCodeIntegrityEnabled / T REG_DWORD / D 0 / F
and we'll see how the system behaves from this point
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Two laptops, HP and Asus having this issue. On Asus, fully uninstalled chrome, did a cold reboot, and reinstalled chrome (fresh downloaded via FireFox which still works). Same issue after reinstall - all extensions fail and no pages can be displayed.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
In the Google Chrome browser: Aw Snap! Something went wrong while displaying this webpage.
In the Microsoft Edge Chromium browser: Page Cannot be displayed.
Cause: In version 78.0.x of Google Chrome (chrome.exe) and 78.0.x of Microsoft Edge Chromium, Microsoft's Code Integrity feature is enabled. SEP Application Control technology is not compatible with this feature in Chrome/Chromium.
Solution: Symantec will update this article once more information is available. Click the Subscribe button to be notified of future updates through email.
On any OS other than Windows Server 2016, SEP can be upgraded to 14.2 or later to address the incompatibility.
If upgrading SEP is not an option, or the OS is Windows Server 2016, the incompatibility can be worked around by adding an Application Control exception for Chrome (Chrome.exe) and/or Microsoft Edge Chromium (MSEdge.exe).
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
I get" Aw Snap" crash on all Chrome supported programs. It crashes my PC Matic virus software. I have uninstalled and reinstalled Chrome several times and still get the" Aw Snap" crash response. Is there a solution to this probem?
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Corporate environment running Webroot. We had four users with the issue this morning. As I was sending out an update email, I watched my Chrome update itself and once I relaunched I was then affected.
I'm running version 78.0.3904.70 using the "--disable-features=RendererCodeIntegrity" workaround since I refuse to use Edge.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Symantec EP 14. But disabling does not change anything to Chrome crashing on every site. Don't put the blame on SEP, but keep it where it should be: Google Chrome ..
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
I can confirm that Nikki B has the correct answer by adding --disable-features=RendererCodeIntegrity. It is also on other websites. And we are running endpoint 14.0. I thought about upgrading to 14.2 until I saw others were still having problems with that.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
"Awe, Snap" crashes including extensions like Ublock, Symantec Endpoint Protection Version 12.1.6 (12.1 RU6 MP6) build 7061 (12.1.7061.6600) Good luck troubleshooting and God speed!
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Using PC matic. I have uninstalled multiple times. I can't try usual troubleshooting steps as everything has the snap page. but putting the app into running app in Win 8 compatibility is working for now
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Chrome just auto-updated to v78 & now experiencing the same Aw Snap! issues. I'm on a work network, but my Symantec Endpoint Protection is showing it's already updated to v14.2 (build 1031). Any other suggestions on how Google plans to solve this issue? Is there a way to revert back to v77 of Chrome? Right now, I'm only online because I changed the filename on the .exe file to "chrom" (sans the e), which can't be a healthy long-term solution.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
I have multiple systems experiencing this issue all with Symantec Endpoint...however they had 14.2. Marking Chrome in compatibility mode is what worked for the systems that started experiencing this issue so far. Each system only had this issues after updating to the latest version.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
same issue here, windows 10 user and do not use Symantec. Nothing works in chrome at all, cant even get to settings or anything. I went into properties on the desktop shortcut and ran compatibility with windows 8. It works fine now.
UPDATE: ...wrong...now isn't working so I tried what Helpdesk Agent suggested by adding -disable-features=RendererCodeIntegrity to target path and it worked.
I have opened and closed and retried it several times now. Its still working fine with that workaround.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Same here is happening. My Laptop runs Windows 10 Home (1909). My all 4 tabs and 4 extensions just crashed after relaunch of updated chrome. Please help us As Soon As Possible.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our lots o users are beginning to receive the update starting yesterday. (SEP 14.0) Granted, it isn't necessarily Googles fault here, but neither them nor Symantec seemed to release any fair warning about this before it happened.
Compatibility mode for all users looks to be a workaround but what happens when we update SEP? Turn back off compatibility mode on all machines?
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.
Found a work around. Right click and select properties for the Google chrome desktop shortcut. At the end of the Target path add -no-sandbox with a space in front: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -no-sandbox. Select OK. Chrome will now open without issue.
Our automated system analyzes replies to choose the one that's most likely to answer the question. If it seems to be helpful, we may eventually mark it as a Recommended Answer.