I've just updated to the new "PA.c Platform 'Next' Pre-Release 4.1", which I know is a test and is expected to have issues. One issue I've found is an error message that displays upon every platform launch. It reads: "The PortableApps.com Updater must be run from the PortableApps.com Platform. It will not function properly when run directly."
I've tried installing the latest update by clicking Manage Apps -> Check For Updates, and also by downloading the full install directly from the PortableApps.com site, but I get this error message on every launch regardless. Anyone have an idea what's gone wrong?
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
Bug reports are here: https://portableapps.com/node/28593 This bug is being investigated.
Sometimes, the impossible can become possible, if you're awesome!
You can stop the message from popping up each time you open the application by going to Options-->Advanced tab and unchecking the Check for updates on platform startup option. However, this is not a good thing since you then have to be checking for updates manually. Hopefully the bug will be fixed soon.
I've tried this "fix" several times, and I still get the error message. It appears that even when I deselect the option to check for updates, the platform still attempts to update and then produces the error message again.
This didn't seem to be getting much attention in this thread, so I thought I'd move the fix I'd posted here to the Pre-Release Bug Reports Thread.
The New Post is HERE
~3D1T0R
The error message correctly indicates the PortableApps Updater could not start. As a result, we are back to having to run the Updater manually to get any PortableApps updates anyway. Does this also imply that the only way people can get rid of the error is to know to run the updater manually, to get a new PortableApps platform, once the bug is fixed and the update is ready? So basically you busted the ability to fix the wrong. Hmmm.
Auto-updating on startup has always been a bit buggy which is why it is disabled by default. There is an existing bug that forces the platform to minimize on startup when the option is enabled as well.
Sometimes, the impossible can become possible, if you're awesome!