We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

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

  • 1 отговор
  • 1 има този проблем
  • 10 изгледи
  • Последен отговор от 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!!!

Всички отговори (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.