Extensions fail to install properly on Google Chrome Portable 8.0.552.215. This appears to be an unresolved issue from Google Chrome Portable 7.0.517.44.
For example, when attempting to install Adblock, I got the following error:
"Could not create directory for unzipping E:\PortableApps\GoogleChromePortable\Data\PROFILE\Temp\scoped_dir_25818\CRX_INSTALL"
I"m running Windows XP SP3 without Chrome installed on the PC itself.
This is pretty much a deal-breaker for me. As others have noted, previous versions of GoogleChromePortable managed extensions flawlessly for me.
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
As mentioned, I can not reproduce this bug at all. Not on any OS nor on any FAT32 nor NTFS. I just installed Google Chrome Portable in a fresh XP virtual machine, then installed Adblock from this page and it worked flawlessly, as it has on every single test I've ever done.
Please remember that no amount of "this is a deal-breaker" or "unresolved from x" will help solve this if no one apart from the handful of PA.c people this is affecting is able to reproduce it (if there is a portable component to it, which it appears there may not be). There have been 5 PA.c users reporting this problem. In some cases UNC paths were an issue (Chrome doesn't like UNC paths).
There is a huge unresolved bug in Chromium/Chrome itself with this issue seemingly tied to everything from UNC paths, encrypted drives mapped to folders, junction points, moving your TEMP directory, not having TEMP in root, moving My Documents, the list goes on.
In short, this isn't a Google Chrome Portable bug. It's an unresolved Chrome bug that hasn't been figured out. But it does explain why Chrome local will work on one PC but not Chrome Portable (since they use different TEMP etc).
Sometimes, the impossible can become possible, if you're awesome!
I'm just one of the lucky ones, I guess. I'll keep monkeying with it, and on the off chance that something changes, I'll report back.
Edit: problem disappeared with update to 8.0.552.224. See below.
Have the same problem (repeatedly). It is fixed for a day or two by uninstalling and reinstalling. Using Chrome sync means I do not lose any customisations but it is a little irritating.
FWIW, I'm running it off a thumb drive on a XP SP3 machine without admin rights.
I updated to 8.0.552.224 today, and extensions are magically working again. Don't know if that helps anyone else, but it's fixed for me now.
I experienced this problem last night for the first time. In my case the path in the error message began "D:2\..." which of course doesn't make any sense.
I do have a drive D: but it's not where Google Chrome Portable is installed. It should have started "P:\..."
Apparently this is a known issue with Google Chrome (affecting the standard version, too).
http://www.google.co.uk/support/forum/p/Chrome/thread?tid=4eb96d95fd17c9...
Unfortunately the workaround proposed there is not suitable for the PortableApps version as it involves editing the environment variables on the host machine.
Regards
Nick
You'll not that the TMP set to C:\TEMP only had 1 of 3 saying it was helpful. The very next comment it worked for the user a few times and then stopped working. So it's not a solution. There is no solution until the Chrome team fixes it in their code.
Sometimes, the impossible can become possible, if you're awesome!
I have started getting the same error, although I am getting
D:1\when it should beO:\.It had been working fine for weeks, but this started happening a couple of days ago, and continues after the recent update.
Did you find a solution in the end?
I reported this problem with 8.0.552.224 back in December of last year - see https://portableapps.com/comment/reply/25824/166535#comment-166535
After a while the problem went away. I think the next upgraded build fixed it. However it has now (current build 10.0.648.204) returned.
Latest error message:
Package is invalid. Details: 'Could not create directory for unzipping: D:0\PortableApps\GoogleChromePortable\Data\profile\Temp\scoped_dir78
79\CRX_INSTALL'
A few points to note:
1. My Google Chrome installation is on drive P:
2. I do have a drive D: and PA.c is running on that drive, but Google Chrome is not installed on that drive.
3. If I copy my P:\PortableApps\GoogleChromePortable\ directory tree to D:, refresh the app icons for the PA.c menu running on drive D:, run Google Chrome from there and then install extensions, all works fine. I can then copy it back to P: and the newly installed extensions work (of course). Bit of a PITA but a workaround nonetheless. Wonder if that yields any clues?
Regards
Nick
I ended up making a fresh copy, replying on Chrome's ability to sync all history, -passwords, settings, extensions, etc.
I guess that I'm one of the "lucky" individuals too. I'm currently having this same issue in version 9.0.597.84 *sigh* I'm going to try installing the local version and see if I still get this issue there. I just wanted to play with a couple Chrome apps....EDIT: Ok now this is odd. My local copy of Google Chrome is unaffected by this bug but my portable copy still is. Also, I've tried the Stable, Beta, and Dev releases and I see the same for all three, the portable version not working and the local version installing themes and extensions just fine.
From the new master of the cards, have a wonderful animé filled day ^_^
I was having the same issue and noticed that the path in the error message said PROFILE (uppercase) but the folder in my portable chrome was profile (lowercase). I renamed the folder to be in uppercase and it actually fixed my issue. I'm not going to pretend to know why, (maybe something unrelated to the folder name case updated when I did that?), but I can install now...
I just upgraded from a very old version of Chrome Portable to the most recent stable version, and then couldn't install extensions. I found this thread, changed the name of my profile folder from "profile" to "PROFILE", and now extensions will install again with no problem.