Issue 380177 in chromium: upgrade from 32bit to 64bit stays in Program Files (x86)

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Cr-Internals-Installer Pri-2 Via-Wizard Type-Bug OS-Windows
Arch-x86_64

New issue 380177 by ghost...@gmail.com: upgrade from 32bit to 64bit stays
in Program Files (x86)
http://code.google.com/p/chromium/issues/detail?id=380177

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/37.0.2024.2 Safari/537.36

Steps to reproduce the problem:
1. Install Chrome 32bit
2. Upgrade to Chrome 64bit

What is the expected behavior?
The installation is moved from Program Files (x86) to Program Files

What went wrong?
The installation is still in Program Files (x86)

Did this work before? N/A

Chrome version: 37.0.2024.2 Channel: dev
OS Version: 6.3
Flash Version: Shockwave Flash 14.0 r0

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Status: Assigned
Owner: w...@chromium.org

Comment #1 on issue 380177 by g...@chromium.org: upgrade from 32bit to 64bit

stays in Program Files (x86)
http://code.google.com/p/chromium/issues/detail?id=380177

Thanks for the report. This is intentional for now. Future work will be
done to move Chrome to the 64-bit Program Files folder.

[chro...@googlecode.com]

Comment #9 on issue 380177 by suf...@gmail.com: upgrade from 32bit to 64bit

stays in Program Files (x86)
http://code.google.com/p/chromium/issues/detail?id=380177

v38.0.2096.0 released still using x86 program folder.

[chro...@googlecode.com]

Comment #10 on issue 380177 by suf...@gmail.com: upgrade from 32bit to

64bit stays in Program Files (x86)
http://code.google.com/p/chromium/issues/detail?id=380177

v38.0.2096.0 dev-m (64-bit) released still using x86 program folder.

[chro...@googlecode.com]

Updates:
Cc: pkas...@chromium.org

Comment #11 on issue 380177 by pkas...@chromium.org: upgrade from 32bit to

64bit stays in Program Files (x86)
http://code.google.com/p/chromium/issues/detail?id=380177

Anything you can share about the rationale for this?

When coupled with the fact that the version string on about:version doesn't
say x64 or 64-bit, it misled me into reinstalling the 64-bit version before
I finally checked the process type in Task Manager.

[chro...@googlecode.com]

Comment #12 on issue 380177 by w...@chromium.org: upgrade from 32bit to

64bit stays in Program Files (x86)
http://code.google.com/p/chromium/issues/detail?id=380177

The version string is displayed on chrome://chrome or Menu->About Google
Chrome, which is the way that most users get their browser version, and
also it's possible to determine x64 by looking at the user-agent
for "Win64; x64".

[chro...@googlecode.com]

Comment #13 on issue 380177 by hue...@gmail.com: upgrade from 32bit to

64bit stays in Program Files (x86)
http://code.google.com/p/chromium/issues/detail?id=380177

this question relate to "google update", "google update" didn't have
windows 64 bit

[chro...@googlecode.com]

Comment #14 on issue 380177 by hue...@gmail.com: upgrade from 32bit to

64bit stays in Program Files (x86)
http://code.google.com/p/chromium/issues/detail?id=380177

This question relate to "Google Update", "Google Update" don't have Windows
64 bit version. Google Chrome 64 bit is sole windows 64 bit software in
Windows.

[chro...@googlecode.com]

Comment #15 on issue 380177 by hue...@gmail.com: upgrade from 32bit to

64bit stays in Program Files (x86)
http://code.google.com/p/chromium/issues/detail?id=380177

This question relate to "Google Update", "Google Update" don't have Windows

64 bit version. Google Chrome 64 bit is sole windows 64 bit software by
google.

[chro...@googlecode.com]

Comment #16 on issue 380177 by pcha...@gmail.com: upgrade from 32bit to

64bit stays in Program Files (x86)
http://code.google.com/p/chromium/issues/detail?id=380177

Absolutely not understood anything to the last answer #15 (???)
The only thing named "Google update" is a NPAPI plugin 32 bits which does
not exist in 64 bits. I never undersood which use it was
The problem here is : when Chrome is updated to 64 bits, it should be
transfered from program files (x86) to program files

[chro...@googlecode.com]

Comment #18 on issue 380177 by w...@chromium.org: upgrade from 32bit to

64bit stays in Program Files (x86)
http://code.google.com/p/chromium/issues/detail?id=380177

The discussion on DIR_PROGRAM_FILESX86 vs DIR_PROGRAM_FILES is in issue
338706.

The discussion over adding (64-bit) the about page is in issue 381246.

The Chrome installer/upgrade logic is designed around in-place upgrades to
the same directory that Chrome is currently installed into. While it might
be possible to support new installs to DIR_PROGRAM_FILES and then upgrade
in place to this directory, having to support potential moves from x86 to
x64 and also x64 to x86 would mean that much of the logic would have to be
changed in order for the browser_distribution code to understand that this
entire directory could potentially move.

In addition, Chrome supports a 'background upgrade' while the browser is
running, and then renames new_chrome.exe to chrome.exe or chrome.exe to
old_chrome.exe on next run - all this logic would have to be aware that the
newest (or most recent) version might be in a totally different directory.

Please feel free to comment on both of those issues, especially if you feel
a clearer 64-bit indicator is needed in chrome://version page
(chrome://version is not linked from the UI anywhere, and is mostly for
developers).

[chro...@googlecode.com]

Comment #19 on issue 380177 by pkas...@chromium.org: upgrade from 32bit to

64bit stays in Program Files (x86)
http://code.google.com/p/chromium/issues/detail?id=380177

@18: Thanks for those links, they're very useful. In particular the level
of detail on the first bug is good to be able to read.

I hope you aren't upset that I reopened the second bug, since it was only
closed recently and was assigned to you, in order to also get the string on
chrome://version updated. If for some reason you'd prefer this work to
happen on another bug, I'd be happy to re-close and file the new bug, but I
figured this way was easier. It does need to be updated, though -- it has
been the canonical version page since the beginning of Chrome's life
(chrome://chrome was added much more recently), so many people do still use
it, especially web authors as well as Chrome's developers.

[chro...@googlecode.com]

Comment #20 on issue 380177 by w...@chromium.org: upgrade from 32bit to

64bit stays in Program Files (x86)
http://code.google.com/p/chromium/issues/detail?id=380177

nope I'm very happy to add to chrome://version as well! Thanks for the
comments.

[chro...@googlecode.com]

Comment #22 on issue 380177 by pcha...@gmail.com: upgrade from 32bit to

64bit stays in Program Files (x86)

https://code.google.com/p/chromium/issues/detail?id=380177

The new stable
Version 37.0.2062.94 unknown-m (64-bit)
is contained in program files (x86) too

[chro...@googlecode.com]

Comment #23 on issue 380177 by joao.ped...@gmail.com: upgrade from 32bit to

64bit stays in Program Files (x86)
https://code.google.com/p/chromium/issues/detail?id=380177

@22: Fresh installation also has the problem?

[chro...@googlecode.com]

Comment #24 on issue 380177 by pcha...@gmail.com: upgrade from 32bit to

64bit stays in Program Files (x86)
https://code.google.com/p/chromium/issues/detail?id=380177

@Joao post #23
Yes it has, absolutely : i have just uninstalled-reinstalled chrome 64 bits.
Version 37.0.2062.94 unknown-m (64-bit)
The program is in program files (x86)/google/chrome
programmes/google is empty

[chro...@googlecode.com]

Comment #25 on issue 380177 by edambasu...@gmail.com: upgrade from 32bit to

64bit stays in Program Files (x86)
https://code.google.com/p/chromium/issues/detail?id=380177

it is very unprofessional, to go against common standards

[chro...@googlecode.com]

Comment #26 on issue 380177 by w...@chromium.org: upgrade from 32bit to

64bit stays in Program Files (x86)
https://code.google.com/p/chromium/issues/detail?id=380177

Please see earlier comments in this bug, and also comments in issue
338706. Although there is a convention on 64-bit to install native
applications in DIR_PROGRAM_FILES, and WOW64 applications in
DIR_PROGRAM_FILESX86 this is by no means required and many applications do
not conform to this convention (including some MS applications). This also
has no visible user impact.

We are continuing to assess whether the technical complexity of moving the
Chrome files into DIR_PROGRAM_FILES is worth it or not given the lack of
user impact. If this happens, it will be automatic upon an update to
Chrome in the future, so no further action will be required by users.

[chro...@googlecode.com]

Comment #27 on issue 380177 by pcha...@gmail.com: upgrade from 32bit to

64bit stays in Program Files (x86)
https://code.google.com/p/chromium/issues/detail?id=380177

@ wfh #26
Yes but it is not "beautiful" : (x86) means 32 bits (of course lol) and the
user/customer may think there is an error (I thought so).
Timid 64 bits Firefox editions were always contained in programmes folder
IE too
It doesn't seem so complicated because currently an installation is
necessary (but I am not a specialist of course)

[chro...@googlecode.com]

Comment #29 on issue 380177 by VYV03...@nifty.ne.jp: upgrade from 32bit to

64bit stays in Program Files (x86)

https://code.google.com/p/chromium/issues/detail?id=380177

> #7 w...@chromium.org

> Yes, we made a conscious decision for the first Dev/Canary 64-bit
> releases to keep the installation directory in DIR_PROGRAM_FILESX86 for
> both 64-bit and 32-bit for both upgrades and fresh installs. This will
> be changed in a future release.

Could you please update the summary? At present it says nothing about fresh
installs.