Tuesday, May 2, 2017

Stable Channel Update for Desktop

The stable channel has been updated to 58.0.3029.96 for Windows, Mac, and Linux. This will roll out over the coming days/weeks.
In order to improve stability, performance, and security, users who are currently on 32-bit version of Chrome, and 64-bit Windows with 4GB or more of memory and auto-update enabled will be automatically migrated to 64-bit Chrome during this update. 32-bit Chrome will still be available via the Chrome download page.

Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.

This update includes 1 security fix contributed by external researchers. Please see the Chrome Security Page for more information.


[$500][679306] High CVE-2017-5068: Race condition in WebRTC. Credit to Philipp Hancke

We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.

A list of changes is available in the log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Krishna Govind
Google Chrome

Labels:

42 Comments:

Blogger Jim McAfee said...

This loaded on some of my machines and I keep getting the "Aw, snap!" message. Nothing is loading.

12:30 PM, May 02, 2017  
Blogger Krishna Govind said...

Jim McAfee@, Are you having McAfee installed? If yes, there is a known bug - https://bugs.chromium.org/p/chromium/issues/detail?id=713875#c14. Thank you.

1:17 PM, May 02, 2017  
Blogger Jim McAfee said...

Thanks, Krishna. We are seeing that issue as well. But the issue I am seeing since the latest stable release is, after it is installed, Chrome launches, but only shows "Aw, snap!". Nothing will launch. Cant even get to the browser settings.

2:06 PM, May 02, 2017  
Blogger Jim McAfee said...

This comment has been removed by the author.

2:59 PM, May 02, 2017  
Blogger Krishna Govind said...

Thank you Jim. Could you please report a bug for this under https://bugs.chromium.org/p/chromium/issues/entry with all details. Thank you.

4:52 PM, May 02, 2017  
Blogger Colin Aggett said...

I am also getting an Aw snap but from the users side on a citrix server

4:55 PM, May 02, 2017  
Blogger Oliver Stevens said...

We are also experiencing the same issue as Colin above.

Logged on the chrome forums under https://productforums.google.com/forum/#!topic/chrome/ptsYxZLowxM;context-place=forum/chrome

6:27 PM, May 02, 2017  
Blogger 0verlord said...

This comment has been removed by the author.

12:28 AM, May 03, 2017  
Blogger JeroenPot87 said...

This is caused by the X64 upgrade, you should uninstall and install the X86 version.

12:32 AM, May 03, 2017  
Blogger Fredrik Magnusson said...

EMET detected EAF+ (GuardPage) mitigation and will close the application: chrome.exe

EAF+ (guard page) check failed:
Application : C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Module : chrome_child.dll

Removed "+EAF+ eaf_modules:chrome_child.dll" for chrome.exe

1:30 AM, May 03, 2017  
Blogger Scot said...

Why is it every time Chrome browser updates the fonts change size? Nothing changed in the settings and now all my webpages are jacked up.

1:52 AM, May 03, 2017  
Blogger Srini said...

This comment has been removed by the author.

4:08 AM, May 03, 2017  
Blogger Srini said...

Hi Guys, We dont have McAfee installed but still facing the same issue after the 64bit AutoUpdate. Any permanent Fix for this issue ??

4:22 AM, May 03, 2017  
Blogger Andre said...

Chrome completely broken by this update. Won't even open settings page with no extensions running.

EMET detected EAF+ (GuardPage) mitigation and will close the application: chrome.exe

EAF+ (guard page) check failed:
Application : C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Module : chrome_child.dll

Removed "+EAF+ eaf_modules:chrome_child.dll" for chrome.exe

6:29 AM, May 03, 2017  
Blogger atch71 said...

As a temporary workaround our organization is instructing us to manually install the 32 bit version of Chrome. I can confirm this workaround is working in our environment.

7:10 AM, May 03, 2017  
Blogger cory church said...

same "aw snap" issue here too on multiple Citrix servers. the -no-sandbox works but impossible to roll that out for everyone and not efficient to install x86 version of chrome everywhere for our clients either. this needs fixed asap!

8:21 AM, May 03, 2017  
Blogger Brantley Larew said...

Reverting to installing the 32 bit version repaired this on our 64bit citrix servers. Does anyone know if this will automatically update to 64bit at next upgrade cycle?

8:35 AM, May 03, 2017  
Blogger cory church said...

@Brantley, it probably will auto update unless you stop and disable the google update service(s)

8:52 AM, May 03, 2017  
Blogger Julian Pastarmov said...

Hi,

everyone experiencing issues on Citrix please consult this help article about the configuration changes required to run Chrome 64 bit on Citrix 6.5: https://support.google.com/chrome/a/answer/7380899

Some more information and discussion can be found here: https://productforums.google.com/forum/#!topic/chrome-admins/3-5s_N0fYjU

Best,
Julian

10:01 AM, May 03, 2017  
Blogger cory church said...

the fix for those in a citrix environment is:

create or update the string value with name ExcludedImageNames with the text chrome.exe,nacl64.exe in HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook.

https://bugs.chromium.org/p/chromium/issues/detail?id=432595#c15

10:12 AM, May 03, 2017  
Blogger Will said...

Regarding the EMET 5.5 EAF+ mitigation, Microsoft official guidance is to disable EAF+ for module chrome_child.dll for chrome.exe. The guidance is here: https://support.microsoft.com/en-us/kb/2909257 and step-by-step to do this is here: https://www.chromium.org/Home/chromium-security/chromium-and-emet

3:34 PM, May 03, 2017  
Blogger dane gregory said...

For server 2008 R2 with citrix add the following reg key

HKEY_local_MACHINE\SOFTWARE\Citrix\CtxHook\

Add

Name Type Data
ExcludeImageNames REG_sZ chrome.exe,nacl^$.exe

This has worked for me on multiple servers

2:53 AM, May 04, 2017  
Blogger HD said...

So my 32-bit version of Chrome has been migrated to a 64-bit version when i automatically got the update 58.0.3029.96.

As 32-bit Chrome is still available via the Chrome download page. I've now reverted back (for testing purposes) to 32-bit Stable Channel 58.0.3029.96.

My question is what will happen when the next stable channel update for desktop is released and installed automatically. Will my 32-bit version remain or will it migrate to 64-bit.

PS. I know i'm better off with a 64-bit version due to stability, performance, and security

3:11 AM, May 04, 2017  
Blogger Will Harris said...

@HD - if you go and download and install the 32-bit version from the download page then it will stay on 32-bit even when it updates to the next Chrome version. Same for the 32-bit MSI.

9:12 AM, May 04, 2017  
Blogger DrBOP said...

T H E

W O R S T

C H R o M E

U P D A T E

EEEEEEEEEEEEEVVVVVVVVVVVVVVVVVVVEEEEEEEEEEEERRRRRRRRRRRRR!!!!!!!!!!!!!!!

Thanks VERY much for causing my computers to NOT WORK on A QUARTER of the net.

Abobe Flash permission "allow" button won't EVEN work ON THE ADOBE SITE.....AT ALL!!!



GOOD JOB!!!

9:28 AM, May 04, 2017  
Blogger HD said...

@Will Harris Thanks, i suspected that was the case but could not prove as 58.0.3029.96 is the latest version.

9:33 AM, May 04, 2017  
Blogger Krishna Govind said...

This comment has been removed by the author.

11:04 AM, May 04, 2017  
Blogger Krishna Govind said...

@DrBop, please visit our help center page for Flash issue - https://support.google.com/chrome/answer/6258784?hl=en. Thank you.

11:06 AM, May 04, 2017  
Blogger Nowshad said...

Every time I update .. I feel like google keeps messing with the popup blocker... I get more popups & i have to use/fix extensions to close those damn intrusive popup ads

12:45 PM, May 04, 2017  
Blogger Mask said...

I have 64-bit system but I was not automatically migrated to 32-bit? I have also enabled auto-update.

12:36 AM, May 05, 2017  
Blogger SteeeveB said...

The update rolled out to our university in the UK yesterday and randomly broke about 10% of chrome deployments over about 4000+ PCs / Laptops. All failing with the "Aw Snap" error. We fixed our citrix environment with the ExcludedImageNames registry key fix, but nothing we do seems to fix desktop / mobile deployments. Do we have any indications that Google are taking this problem seriously and if so when can we expect a fix.

3:33 AM, May 05, 2017  
Blogger Editor said...

Chrome 58 should be renamed AW SNAP because I am getting that error CONSTANTLY.

Especially happens in Gmail.

Very, very sad day for all of us.

10:04 AM, May 05, 2017  
Blogger Will Harris said...

hi @SteeveB and @Editor - if you are having 'Aw Snap' issues can you file a new bug on https://new.crbug.com/ and we will work with you to try and determine the root cause here.

10:34 AM, May 05, 2017  
Blogger D Rome said...

58.0.3029.96 is broken, it's wiped out all my extensions and if i try to manage them remove or install it's locks up and if i click on anything i just get a splat sound. only way to close is to end task. can i roll back?

5:27 AM, May 06, 2017  
Blogger asianime said...

DON'T UPDATE TO THIS VERSION PEOPLE!

I ALWAYS GET AWW SNAP ERROR

4:51 PM, May 06, 2017  
Blogger Unknown said...

This comment has been removed by the author.

12:13 AM, May 08, 2017  
Blogger max said...

Try uninstall Chrome then install Chrome "32 bits".

12:18 AM, May 08, 2017  
Blogger Axel Dürrbaum said...

When dowenloading and isntalling Google Chrome for Debian amd64 from
https://www.google.com/chrome/browser/desktop/index.html

md5sum google-chrome-stable_current_amd64.deb
13a77d042f8b8967744d22f5ff6d26d3 google-chrome-stable_current_amd64.deb

dpkg -i google-chrome-stable_current_amd64.deb
(Reading database ... 581807 files and directories currently installed.)
Preparing to unpack google-chrome-stable_current_amd64.deb ...
Unpacking google-chrome-stable (58.0.3029.96-1) over (58.0.3029.96-1) ...
Setting up google-chrome-stable (58.0.3029.96-1) ...

it always claims to be (dtill) version 53:

/opt/google/crome/chrome -> More -> Help -> About Google Chrome
gives "Version 53.0.2785.92 (64-bit)"

Whats going wrong and which version is now really installed?

3:18 AM, May 08, 2017  
Blogger Matt Bidwell said...

We are also experiencing aw snap errors with this update.

2:38 PM, May 08, 2017  
Blogger Christopher Tocci said...

Hi,

Also started getting the "Aw, snap!" dialog page on Windows 7 (64-bit) OS and Chrome browser. Will not load Webroot or Adblocker Plus extensions unless you keep hitting the reload slide-out dialog about 8 times for each one. Eventually, the extensions load and it is different each time you start the Chrome browser. We also get the "Aw, snap!" dialog when we attempt to go into the "setting" or "More tools" menus.

Best to use another browser until version 58.0.3029.96 gets repaired. My Firefox and Palemoon browsers are working OK and will use them for now.

7:04 AM, May 09, 2017  
Anonymous Anonymous said...

This chrome update is horrible I agree with other posters Aw Snap! Stop doing so many updates if you can't do it properly.

7:47 AM, May 09, 2017  
Blogger Martin Cunningham said...

I am having the same issue with Chrome 58 not launching. When clicking the shortcut 2 instances appear in task manager but no window opens. If I kill 1 process, Chrome opens and I somehow end up with 4 instances in task manager. I have looked at fix here, https://bugs.chromium.org/p/chromium/issues/detail?id=713875#c14, however we do not use the policy that is required to be updated with the Chrome Version.xml file. So Web Post Protection is not available to be altered.
Also Chrome 58 only fails to open on a small percentage of machines onsite, probably less than 5%.
Any other fixes available for this?
Thank you

7:36 AM, May 15, 2017  

Post a Comment

Subscribe to Post Comments [Atom]

<< Home