For the second time within two months I had a problem with Google Chrome Portable: after doing an update Chrome won't work.
Removing and re-update is not possible; there is one file that I cannot remove (not even as an administrator).
That file is C:\PortableApps\GoogleChromePortable\App\Chrome-bin/chrome.exe
After several attempts I realised that this file might be corrupted. Performing a CHKDSK /F (which runs at least an hout on my PC) solved the problem: CHKDSK removed the file.
I think it's quite strange that two times within a short time the same file appeared to be corrupted. Did anyone have the same problem?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Corruption like that is nearly always indicative of an issue with the drive it's on. When an update is done, it's just a standard installer, which is basically a glorified unzipping process and then some specialized file handling for moving those files around and updating settings and such. There's nothing at all in the installer that would cause drive corruption.
Sometimes, the impossible can become possible, if you're awesome!
I've had the same problem twice since my first post. It always is the same file:
C:\PortableApps\GoogleChromePortable\App\Chrome-bin/chrome.exe
Today I had the same problem with this file.
But today I had the same problem with the similar file of FirefoxPortable:
C:\PortableApps\FirefoxPortable\App\Firefox64\firefox.exe
I cannot remove it and only a CHKDSK solves the problem.
I now don't think the files are corrupted; I'm think the access rights to the files are blocked.
Two similar files that get corrupt after an update on a harddrive that never gives me any similar problems. That cannot be a coincidence. There must be something in your installer that is causing this problem.
I'm afraid I have to stop using these portable apps. Hopefully other apps don't have the same problem.
There's nothing in the installer that does anything with regards to rights on files. Not a line of code. You can look at it all in our code repository to verify.
If it requires a CHKDSK, it's not an access rights issue. That's a disk error issue. If there were an access rights issue you'd simply be unable to remove the files.
Sometimes, the impossible can become possible, if you're awesome!