Try running the new installer without first uninstalling Chrome. Does that reliably succeed?

Could you check for C:\Windows\Temp\chrome_installer.log and attach that?

That aside, the most reliable way to update Chrome is to simply run the new version's installer without first uninstalling the old version. Please try that and let us know how it goes.

In This way installation success.

Main requirement which i need to fulfill install version provided .
That's why uninstall is mandatory even the version was higher than i bring in .

Is there way to overwrite version of google chrome browser by special command line parameter provided to browser?

Deleted: chrome_installer.log 150 KB

chrome_installer.log 150 KB View Download

Thank you for providing more feedback. Adding requester "grt@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

You may have success in uninstall-then-install if you add some custom handling to ensure that no GoogleUpdate processes are running when you initiate the install. I'm not certain that this is the problem, but it would be my guess. I don't see any evidence in the logs you've provided that Chrome's installer is running into any errors, so I'm guessing there's a race with Google Update.

If your intention is to move machines with a higher version of Chrome to a lower version, then you should be aware that Chrome does not support loading User Data from a higher version. In other words, if you move a machine from Chrome 59 back to Chrome 57 via uninstall-then-install, you are likely to receive complaints from users that Chrome shows a dialog like "Your profile can not be used because it is from a newer version of Google Chrome." at startup.

The only robust way to move backward without bothering your users with this sort of dialog is to ensure that user data is erased upon downgrade. There is a feature in the Chrome MSI to accomplish a downgrade with user data wipe. To use it, run the MSI like this:

msiexec.exe /fvomus GoogleChrome.msi ALLOWDOWNGRADE=1

Be aware that this *will* result in loss of user data. If your users are not using Chrome sync, they may be upset with you that their data has been wiped.

Please note that use of this is generally "at your own risk" unless you are paying for enterprise support, in which case you should reach out to your contact to find out if it's really the right thing for you.

To reiterate: if you use this ALLOWDOWNGRADE=1 flag, users whose machines are downgraded from a higher version of Chrome to a lower one *WILL LOSE DATA*.

Ephemeral profile in use , so there are no data , and profiles are cleanup.
I will test proposal with Downgrade:) and update later this ticket. 

Parameters works as expected  

If we speaking about version 59 downgrade to 56  booth 64 bit  , it's working fine.
msiexec.exe /passive /log d:\my.log /i d:\---googlechromestandaloneenterprise64-56.0.2924.87.msi ALLOWDOWNGRADE=1

If we speaking about version 58  (32 bit ) to upgrade to version 59 (64 bit) ,
Upgrade working itself.  There are problem with Version not correctly updated at all ..  you can see it from attachment

Deleted: chrome-installer.png 214 KB

	chrome-installer.png 214 KB View Download

After re-run the installer i am getting something completely new.
"The Specific  Account already exists" 

Can you explain me , where i can shake more to make the google installer workable ? 

Deleted: chrome_installer.log 262 KB

chrome_installer.log 262 KB View Download

Deleted: One-more.png 15.1 KB

	One-more.png 15.1 KB View Download

Looks like not related to enterprise.

Can you reply in more technical details , without putting the perception judgement ? 
Log File present ,screenshot present. 

Initial problem
1) Uninstall older version , Install newer version will fail 
2) Got updated to use  "ALLOWDONWGRADE=1" with this approach it works only once and Registry value within UNINSTALL program not updated correctly
3) Additional run with ALLODOWNGRADE=1  lead to the LAST problem as reported

How to proceed ,and when the issue will be fixed?

"The specified account already exists." is the message text for the Win32 ERROR_USER_EXISTS error code. I think this is being shown to you by msiexec and not by Chrome or Chrome's installer. Is there any indication as to what is going wrong in the msiexec log (use "/l*vx my.log" to get a verbose log)? Also, it appears that you are not using the "/fvomus" option as indicated in comment 5. Does the update succeed if you use that option?

For the issue tried to reproduce there are no luck . for "The specified account already exists." .
One main problem for now is  with /fvomus  it's not update the value in registry.
As per my investigation when then 

32 bit version exists     upgrade to 64 bit version . in This time version will be never updated correctly .

The 32 bit installer and 64 bit installer using different registry.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall


So final temporary solution what i am using now :

1) Uninstall the google chrome completely
2) Install new one (it will fail )
msiexec /quiet /i  googlechromeStandaloneEnterprise64-59.0.3071.86.msi
3) Install second time (it will be succeed)
msiexec /quiet /i googlechromeStandaloneEnterprise64-59.0.3071.86.msi

Is there better way to proceed?

Thank you for providing more feedback. Adding requester "grt@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Thanks for the info. I've filed  issue 735459  for the DisplayVersion not being updated properly when /fvomus is used to run an update in maintenance mode. Will a fix for that be sufficient for you to run updates with /fvomus?

This looks very great :) it will be sufficient enough !

And please kindly let me know what release the change will be targeted ?

An update: a fix for 735459 will ship with the next stable update after the current one (which is 59.0.3071.115). My advice to use /fvomus was imprecise -- /fvomus may only be used when you're re-running the exact same MSI that was previously used on the machine. Otherwise, if a machine has Chrome 59 installed by the user from a normal download and you want to move it back to 57, use /i; for example:

msiexec /l*vx msi.log /i GoogleChrome.msi ALLOWDOWNGRADE=1

i did check there are no problem with 64->64 bit  i am using the   
msiexec /passive /i "D:\ChromegooglechromeStandaloneEnterprise64-59.0.3071.86.msi" ALLOWDOWNGRADE=1

Chrome 60.0.3112.78 and newer have the aforementioned fix. Closing out this issue. Cheers!