Issue metadata
Sign in to add a comment
|
Attempted to install chrome For Windows 10/8.1/8/7 64-bit, installer failed but gave no notice.
Reported by
phre...@gmail.com,
Aug 10 2017
|
||||||||||||||||||||||||
Issue description
Chrome Version : <Copy from: 'about:version'>
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari:
Firefox:
IE:
What steps will reproduce the problem?
(1) Run ChromeSetup.exe
(2)
(3)
What is the expected result?
to see the 64 bit version of chrome installed.
What happens instead?
The installer seems to be working fine, and then completes, but there is nothing in the c:\program files\chrome\ directory, except a shortcut to a 32 bit version of chrome in the x86 program files directory.
Please provide any additional information below. Attach a screenshot if
possible.
Background:
I just installed a fresh version of Windows 10 Home 64 bit OS, completely wiping the hard drive. Since I was doing a clean installation of windows, I thought it a good time to install the 64 bit version of the OS, which I did. I was forced to do this clean installation because of errors introduced into my system by the automatic upgrade to windows 10 creators edition (1703), which caused all my metro-style apps to flicker/refresh constantly, making them unusable. Calls to Microsoft tech support, and posts on their forums provided no solution, so I had to do the wipe-and-clean installation.
I then used the microsoft suggested application Laplink PCMOVER to copy over my files and applications from my previous installation (windows 10 home 32 bit}.
The net result of the installation and copy of the data and programs back into windows seems to be successful, but I am slowly migrating applications from 32 bit to 64 bit versions. This was an attempt to do that for chrome, and it failed.
I suspect that the reason was that the installer saw the 32 bit version on the system, and then either stopped or did a roll-back of the 64 bit version. However, it gave NO notice that this had occurred. I won't be the only one migrating between 32 bit and 64 bit versions of the OS this way. Microsoft itself recommends use of the PCMOVER application.
I recommend that you make a change to the Chrome installer to either deal with the upgrade by removing the old version of 32 bit version chrome and installing the new (albeit 64 bit) version, just like it would do if were upgrading the 64 bit version. If that's not possible, then at least put out some kind of message indicating the reason the installation is being terminated, and don't just leave the end-user hanging there wondering what happened.
Thanks,
Philip
,
Aug 17 2017
Hi. Thanks for the detailed report. 64-bit Chrome installs into the 32-bit Program Files directory at the moment. You can verify that you're running the 64-bit build by navigating to chrome://version. The top line will have "64-bit" in it somewhere for the x64 build. I'm marking this issue a duplicate of the existing one about 64-bit Chrome being installed into the wrong directory. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by mmanchala@chromium.org
, Aug 11 2017Components: Internals>Installer
Labels: Needs-Milestone