Is it possible to allow Firefox to auto update?

[cornflake2]

I have Sandboxie on a computer that's used by several people and it forces the Firefox process. When a user launches Firefox, if there's been an update there will be a message that Firefox cannot be updated in the sandbox. I would like Firefox to update automatically without any intervention, but it doesn't seem that this is possible unless a user is running Firefox outside of the sandbox. What this means is that each time there's an update I have to manually intervene. It's a bit annoying.

Is there a workaround in Firefox's update service or in Sandboxie that will allow Firefox to be updated even if it hasn't been running outside a sandbox?

Thanks

[CPB]

You could turn off the option to have Firefox check for updates and only update manually when a final version has been released (outside the sandbox, of course). There have only been 6 updates this year (v18 to the current v23).

I've never had Firefox update automatically. If it wants to update each time a new beta version is released then that *would* be rather annoying, as that would probably be close to 50 updates so far this year.

[Guest10]

With the automatic check for updates turned off, as CPB suggests, people would have to do a manual check for updates.
Also uncheck: "Automatically update: Search Engines"

And in Tools > Add-ons > Settings (Gear symbol)
Uncheck: "Update Add-ons Automatically", if you don't allow direct access to the entire Firefox profile folder in the Sandbox Settings.
----
I don't know if there's a way to keep Sandboxie from telling you that you should not update, because that message appears during the update process if the Firefox program file is located outside of the sandbox.

Even if you could get rid of that message, you would have to allow Direct File Access to (at least) the Mozilla Firefox program files folder to update those files, if not other folders as well.

It's hard to follow exactly what the updater does, but it plays games with folders by first creating a temporary folder:
C:\Program Files\Mozilla Firefox.bak
Then moves the files from C:\Program Files\Mozilla Firefox, into that folder.
Then it patches the necessary files and saves them to:
C:\Program Files\Mozilla Firefox.bak\updated

Finally, it moves the patched and any unpatched files back to the:
C:\Program Files\Mozilla Firefox
folder, and then deletes the temporary folders.

I'm not at all sure that you want to try adding sandbox settings for that.

[cornflake2]

It's just that it's so annoying. I have the same problem with Chrome. Chrome is forced to run in a Sandbox and will not update itself unless I specifically invoke it outside the Sandbox. This means users are using less secure versions of the browser until a manual update is initiated.