I am not able to update starting from 11.1. I currently have 11.0.1.
Updater terminated at 97% and nothing happens.
When I download and run installer it tells me "Windows cannot access the specified device, path or file".
New: Kanri (Oct 9, '24), Platform 29.5.3 (Jun 27, '24)
1,100+ portable packages, 1.1 billion downloads
No Ads November!, Please donate today
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 usually indicates a logical error on the device you are installing to. Please check it for errors and fix any you find. Barring that, ensure you have a valid TEMP directory setup with free space.
Sometimes, the impossible can become possible, if you're awesome!
I have administrative rights on my machine and have platform installed in C: and have 10Gb available
I did following:
1. Run checkdisk
2. Checked existence and access to all Temp folders
Problem remains.
At the same time I am able to install portable apps updates (directly or using modified updater shared by you some posts earlier).
Please manually download the latest release, run the installer and point it to the directory that contains your Start.exe file as well as the PortableApps and Documents folders.
Sometimes, the impossible can become possible, if you're awesome!
John, installer can not run. It immediately pops up message box with text "Windows cannot access the specified device, path or file. You may not have appropriate permissions to access them". Running installer as admin doesn't help.
It's some sort of configuration issue with the computer, then. It doesn't do anything special on startup other than attempt to instantiate it's plugin directory within TEMP which is named ns?????.tmp (where ????? are random characters).
The message "Windows cannot access the specified device, path or file" indicates that something isn't working right. It's either a permissions issue (ie permissions are broken on the PC), an antivirus issue, or some other configuration issue. I would suggest following these steps:
http://support.microsoft.com/kb/2669244
http://helpdeskgeek.com/help-desk/windows-cannot-access-the-specified-de...
Sometimes, the impossible can become possible, if you're awesome!
This has annoyed me for quite some time. I can't take advantage of automatic updates for the platform as they fail everytime. Also when I download them they fail with the same message "Windows cannot access the specified device,path, or file". I have found through trial and error and reading a few other posts for ideas that removing extra periods "." from the file name before manually running it will allow it to run. Going through this again today trying to update to 11.2 I narrowed it down to the actual period preceding "com" being the problem. I am currently on a Win7x64 machine that has McAfee enterprise on it however I don't see any McAfee notifications stating it is blocking (other posts have suggested McAfee). I successfully run it on a Win7x32 Virtual machine that has the same Enterprise McAfee running on it so don't really know what the deal is
So I change "PortableApps.com_Platform_Setup_11.2.exe" which fails with that error to be "PortableApps_com_Platform_Setup_11.2.exe" which successfully runs.
I don't know why this is, but has been plaguing me for quite a while and of course bothersome that I can't utilize autoupdate for the platform.
I am sure I am not the only one - Perhaps someone could determine the true root cause or start naming differently without the "." before com:
Sorry, probably sounds like a rant - you can tell I've had to find/remember this a few times...
(hope it helps any others looking for such a manual workaround)
That would be a bad antivirus configuration. Some early antivirus products tried to do this to stop things like QuarterlyReport.xls.exe. They quickly learned that this actually broke all kinds of things and is a truly awful, shortsighted and technically inept thing to do. Likely, it's an old configuration file that wasn't properly updated.
Things won't be changing as .paf.exe is the standard and is used by thousands of files. I'd suggest reporting the issue to McAfee.
Sometimes, the impossible can become possible, if you're awesome!
John, it affects just platform installer. Applications' installers with .paf.exe are not affected.
I have latest McAfee build.
That means the McAfee would be blocking every single installer that includes a version number at the end of the filename. I think that may be even worse. And technically... well... dumb. Say you want to go download Pidgin... Oops, it's pidgin-2.10.6.exe, so that's blocked.
How about if you rename it to PortableApps.com_Platform_11.2_Setup.exe. Does that work?
Sometimes, the impossible can become possible, if you're awesome!
It doesn't.
So McAfee blocks every EXE with a version in it? That can't possibly be right as everyone would quickly stop using it. Are you using some restrictive non-default settings?
Sometimes, the impossible can become possible, if you're awesome!
1. I can not change my McAfee settings because they are locked
2. McAfee doesn't block ALL files with the version number in the file name. I just downloaded FastCopyPortable_2.11.paf.exe and it runs well.
I know that, because of the .paf.exe. What about an installer like Pidgin's I mentioned above? And you're sure renaming it to PortableApps.com_Platform_11.2_Setup.exe failed? How about PortableApps.com_Platform_11.2.Setup.exe and PortableApps.com_Platform_Setup_11.2.paf.exe (please try both)?
Sometimes, the impossible can become possible, if you're awesome!
I downloaded pidgin-2.10.6.exe from Pidgin site and it works.
None of your 3 name options for the platform worked.
What if you remove the word setup from it? What naming options for it DO work? Does it only work if your remove the . in .com?
Also, are you sure it is McAfee? No other McAfee users are reporting this, so it could be a specific corporate restriction.
Sometimes, the impossible can become possible, if you're awesome!
It worked in the variant suggested by richrec: PortableApps_com_Platform_Setup_11.2.exe
Looks like the dot before "com" creates the problem.
I can not prove that this is McAfee, logs are not available for me. But looks like my symptoms are same as richrec's.
Ok, cool. We can work with that at least. Sounds like an exceedingly buggy definition setup in McAfee to block .com as if it were a .com file, which is just... odd.
Sometimes, the impossible can become possible, if you're awesome!
I tested your method and it works. I was able to run installer manually. I also have Win7x64 and McAfee.