Due to the default values in the sections [SinglePortableAppInstance] and [SingleAppInstance] it's possible, that
- two portable instances of Firefox can run simultaneously
- it's impossible, that a portable and locally installed instance of Firefox can run simultaneously
The reason for the impossibility in the second case is obviously, that therefore will be prevented, that after the closure of the portable instance of Firefox were not deleted the settings of the locally installed instance of Firefox, which are stored in the folder %AppData%\Mozilla. My question now is, whether it is still possible to start a portable and locally installed instance of Firefox simultaneously? Accordingly should be avoided in this case, that after the closure of the portable instance the folder %AppData%\Mozilla will be deleted. Is this feasible?
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
Firefox Portable doesn't even use PAL. Issues with multiple Firefox instances have been discussed to death at this point. The only way you can do it is to set multiple instances on and then all bets are off as to how well it will work as it is an unsupported feature.
Sometimes, the impossible can become possible, if you're awesome!
The main problem seems to be, that it must be avoided, that after the closure of the portable instance will be deleted the folder %AppData%\Mozilla. Is there a way to realize that?
It's not deleted unless it didn't exist in the beginning. And, even then, it's only deleted if it is empty.
Sometimes, the impossible can become possible, if you're awesome!
Your statement is inaccurate. After the run of Firefox will be created the folder %AppData%\Mozilla. And this folder isn't empty, because it contains the subfolder "Crash Reports", which isn't empty. Yet the folder %AppData%\Mozilla will be deleted after closing Firefox.
because crash reports is also handled specially as well. out of curiosity, why do you keep making wild assumptions about how apps work?
Sometimes, the impossible can become possible, if you're awesome!
I am last night come across this problem. Surely this is a more theoretical question without much practical relevance. But still, it has interests me.
Check out the included code to see how it handles things.
Sometimes, the impossible can become possible, if you're awesome!