PSA - 10/23/2019 Chrome update Win10 compatibility issues ("Aw Snap" error)

[Brad Johnson]

Chrome is my primary browser but this morning I came in to a bunch of "Aw Snap, Can't Load That Page" messages. Appears to be an issue related to this morning's Chrome app update. If the Chrome user forum is any indication, it's hosed Win10 compatibility for more than a few users.

The short term solution seems simple enough... right click on the Chrome icon, go to Properties, select the Compatibility tab, and click the box in the Compatibility Mode section. Seems to be a one-shot solution as I've had to repeat the procedure each time I wanted to open Chrome. I'm dealing with that by simply having multiple tabs open that I'm pulling out into separate Windows.

Brad

[230RN]

If everything were perfect, this would be heaven.  And as we all know, this ain't heaven.

[MillCreek]

This PSA was very helpful; this is affected my wife's Win10 laptop.  Brad's suggestion fixed it while we wait for the Chrome update.

[Boomhauer]

I hope it doesn’t do this to my work computer our work order system runs exclusively on Chrome.

[Brad Johnson]

Looks like the root cause was an incompatibility between Chrome's latest update and Symantec EndPoint Protection (versions earlier than 14.2). The university released their "approved" SEP 14.2 package this morning. A quick download & install later, everything is back to normal.

Brad