New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 596077 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

MSI installer not upgrading anymore

Reported by mackride...@gmail.com, Mar 18 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36

Steps to reproduce the problem:
1. Currently using 48.0.2564.116 (installed via MSI installer)
2. Installing 49.0.2623.87 (MSI installer again)
3. Chrome won't start anymore

What is the expected behavior?

What went wrong?
Users can't start chrome anymore. They're getting 01.png ("class not registered").

"Run as administrator" is working - Chrome seems to be fine, when running this way.

Did this work before? Yes Every upgrade before including 48.0.2564.116 was installed this way.

Chrome version: 49.0.2623.87  Channel: stable
OS Version: Server 2012
Flash Version: Shockwave Flash 20.0 r0

Nothing special about the way I'm installing: just using the MSI file without any parameters.

Completely uninstalling and reinstalling Chrome isn't working either.
 
chrome_installer.log
11.9 KB View Download
msilog.log
212 KB View Download

Comment 1 by emaxx@chromium.org, Mar 28 2016

Cc: saswat@chromium.org emaxx@chromium.org dskaram@chromium.org
Owner: grt@chromium.org
Status: Assigned (was: Unconfirmed)
Greg, assigning to you. Please prioritize.

Comment 2 by grt@chromium.org, Jul 13 2016

Components: Internals>Installer
Labels: Needs-Feedback
I believe this is a duplicate of  issue 596930 , which has links to articles to resolve the problem. If I understand correctly, the problem should disappear once you update to Chrome 50. Please let me know if this is not the case, and we will dig deeper.

Comment 3 by grt@chromium.org, Aug 8 2016

Status: Fixed (was: Assigned)
Closing this out. Please re-open if you experience this again in the future. Thanks!

Sign in to add a comment