Hi,
Chrome was working fine,
Today PortableApps wanted to do an update.
then Chrome wanted to do an update.
Now Chrome cannot open any page including
chrome://chrome/settings/
Just sits with the anti-clockwise spinning hourglass thing in the tab name.
Is this a known problem?
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
Nothing new changed on our end in terms of the way it's packaged and portablized. Chrome's updater is incompatible with the portable version so what do you mean Chrome wanted to do an update? Or do you mean the PA.c Updater had an update for Chrome Portable available?
Sometimes, the impossible can become possible, if you're awesome!
You're right, the PA.c updater had an update as one was released recently.
I tried uninstalling and reinstalling but no luck.
http://postimage.org/image/d6tur5wxb/0b9f3407/
(Obviously IE continues to work as it did before....)
tried deleting the folder ..\AppData\Local\Temp\1\GoogleChromePortable
restarted, the folder was recreated but no joy.
tried deleting the folder ..\AppData\Local\Google\Chrome\
restarted, the folder wasn't recreated (might not even be related to the PA) but still no joy.
PS: I don't have admin rights on this machine (why I was using the portable version in the first place) and I run off a shared network drive.
Chrome doesn't support running from a network drive properly, even when it is mapped to a drive letter. It is a limitation of Chrome that comes and goes across multiple versions. It usually manifests like this or various components of chrome failing. If you install a new copy to your Desktop directory, for instance, you'll find that it'll work.
Sometimes, the impossible can become possible, if you're awesome!
(back from vacation)
Ahh, ok, I didn't realise that.
I'll try chrome from the local drive.
Is that mentioned to the user when installing Chrome, I didn't notice, but I don't always look very closely.
Is running PA from a network drive generally a bad idea?
The installer doesn't have code to detect network drive installs. And apps don't currently advertise whether they work on network drive to the installer or platform. We did add code into the PortableApps.com Launcher that will alert if it's not sure or error if it knows an app can't run from UNC. But Chrome doesn't use this yet. Even then, it wouldn't error for Chrome if you were running from a network drive mapped to a drive letter. It only detects UNC paths.
Chrome is unique though, as it somehow 'figures out' that it is running from a network drive mapped to a drive letter and still has issues. It's the only app with this issue. It could be due to the fact that it can't interact with the other Windows components when not run from a 'local' drive (unlike other browsers like Firefox or Opera, Chrome is not a self-contained browser and relies on Windows components for a number of things like proxy configuration, certificate storage, etc).
Sometimes, the impossible can become possible, if you're awesome!