Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Silent auto update not working. I've narrowed it down to the updater.exe not having user permissions to execute.. why?

  • 1 odgovor
  • 1 ima to težavo
  • 10 ogledov
  • Zadnji odgovor od philipp

more options

I install Firefox as Administrator.

When limited users run Firefox, it won't auto update silently (about:config is setup for it). When I run Firefox as Administrator with the same about:config, it updates silently.

I've narrowed this down to being that the [updater.exe] does not have user execution rights by default.

I can't just change the permissions on the executable due to netsec issues..

Why is this? Why doesn't it have user execute permissions.. As soon as i give a limited user execute permissions to updater.exe, it works.. so it's not the maintenance service, or anything else.

Thanks!!!

I install Firefox as Administrator. When limited users run Firefox, it won't auto update silently (about:config is setup for it). When I run Firefox as Administrator with the same about:config, it updates silently. I've narrowed this down to being that the [updater.exe] does not have user execution rights by default. I can't just change the permissions on the executable due to netsec issues.. Why is this? Why doesn't it have user execute permissions.. As soon as i give a limited user execute permissions to updater.exe, it works.. so it's not the maintenance service, or anything else. Thanks!!!

Vsi odgovori (1)

more options

hello, the maintenance service is not yet set up to run updates in the context of a limited user account - however it is worked upon and progress is tracked in bug #711475.