Description: Google Chrome Portable does not work when installed in paths containing space(s), e.g. C:\Program Files\
In addition to the x64 platform testing reported in my previous post, I did some more testing in two (2) independent plain XP SP3 32-bit VMs, and Chrome did not work there either.
Then I started trying older 8.0x versions with the same results, both in x64 and in x32. During these tests, I installed Chrome in either C:\Program Files (x86)\ for x64 or in C:\Program Files\ for x32.
Then, in one of these previous versions installations, I accidentally installed Chrome in C:\ and it worked! Then I copied this installed Chrome into C:\Program Files\ and it didn't work!
Provided that I use several portable apps, and they always work in whatever dir I install them, I dare call this behaviour a Chrome Portable bug. Obviously the developers did their testing on flash disks and did not attempt installing in the usual place, i.e. Program Files. However, dear developers, please take into account that many users like me prefer to install portable versions, when available, on their desktop/laptop/main PCs, because they want to keep their registry lean and clean. Therefore, it does make sense to take the time to test the "conventional" installation paths too 
Solution: Don't install in directories whose names contain space(s).
=================
Initial Subject: Google Chrome Portable 8.0.552.224 on Win7 x64 does not work
As the title says, after installing successfully, double-clicking on the app does nothing. The same applies to the Test version.
I checked with Process Explorer, nothing relevant to Chrome was running. Disabling myantivirus (ESET SS) had no effect.
I replicated the problem in a clean (with nothing installed) Win7-x64 VMWare virtual machine, it does not work.
Chrome standard (non-portable) runs OK.
Note: In both Win7 machines UAC was turned off.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
This is still true in GCP 13.0.782.107.
There used to be a bug like this in Stellarium as well, but that was fixed; I assume it's the same (or a similar issue here).
As has been noted in other threads, many people use Portable Apps on one machine exclusively (often under c:\Program Files\), but we use PA instead of regular so that when it comes time to reformat, etc., all settings are not lost.
Discussions have taken place in other threads on issues occurring when installing PortableApps to C:\Program Files\ on Windows 7, and this is more than likely the cause.
I would suggest testing this problem on Windows 7 in a directory with spaces in the title that is not C:\Program Files\, and then report whether it is actually a bug, or a Windows issue that has already been reported, and cannot be fixed by us, or even by the developers of Chrome.
Interesting point. I haven't seen any, but I generally only look when I have a problem, and the 41 other applications that I have from PortableApps.com all work just fine.
I just tested, and you are correct; it's _not_ a function of the spaces, but apparently of Program Files.
Interestingly, by opening a command prompt, going to c:\progra~1\portableapps\portableapps\googlechromeportable, and running GoogleChromePortable.exe, it _does_ work. Running from c:\program files\ does not.
you should never install any portable apps into som eof those protected spaces like Program Files on drive C or similar.
Current operating systems like w7 will not be pleased with programs not installed properly via operating system to run clean from such location.
So the rule is: place your portable versions on some data folder which is not protected by windows. Do not use c:Program Files for storing any portable apps.
Otto Sykora
Basel, Switzerland
Surely, this will be fixed in newer Chrome PA releases, right? Or is it that they won't?
Installing to the Program Files directory is not now and never has been supported. Windows Vista and Windows 7 impose restrictions that make it incompatible with portable apps. In addition, many apps detect Program Files and use that to enable 'local' mode instead of portable mode.
Sometimes, the impossible can become possible, if you're awesome!
do you know why all other applications I have work just fine? Is Google Chrome one of these applications that specifically detects "program files"?
FWIW, because of company policy, UAC is completely disabled.
As I said, some apps specifically detect when they run from Program Files and operate differently. Combine that with portablization and you either wind up with an app just running in local mode (Sumatra PDF always used to do that), an app that won't start (see Google Chrome), or just random bugs. So, we've always recommended against it, we've never supported apps actually running from there and we specifically tell people not to do it whenever anyone asks.
We'll be disabling the ability to install to Program Files at some point in the PortableApps.com Installer to prevent further issues. I'd highly suggest using C:\PortableApps instead.
Sometimes, the impossible can become possible, if you're awesome!
I know this is not supported (and won't be), but if anyone else wants to try this...
I created a batch file called GoogleChromePortable.bat containing:
cd "%~ps0"
start /b GoogleChromePortable.exe
This changes to c:\progra~1\portab~1\... (or whatever the correct directory is, obviously) using the short paths, and runs GoogleChromePortable.exe from there. It works from the command line, windows explorer, and launchy.