Ugh, well this is a bit annoying. It seems that when update elevation is cancelled, we simply retry the update _without even attempting_ to use the Maintenance Service ([here](https://searchfox.org/mozilla-central/rev/898d40036b2646daea9b44fd2e2fc44dc050158d/toolkit/mozapps/update/UpdateService.sys.mjs#1717)). So once this problem happened the first time, it sort of perpetuates itself. I've filed Bug 1885195 to look into changing this behavior because, at first glance, that doesn't seem like the right thing to do. So the most recent `update_messages` logs are telling the updater not to use the Maintenance Service for that reason. Could you attach the older `update_messages`? I'm hoping that one of the older ones will have the _original_ cause of using a UAC when we shouldn't be. Maybe consider zipping them or something just to keep the number of attachments on this bug from getting ridiculous.
Bug 1828245 Comment 42 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Ugh, well this is a bit annoying. It seems that when update elevation is cancelled, we simply retry the update _without even attempting_ to use the Maintenance Service ([here](https://searchfox.org/mozilla-central/rev/898d40036b2646daea9b44fd2e2fc44dc050158d/toolkit/mozapps/update/UpdateService.sys.mjs#1717)). So once this problem happens the first time, it sort of perpetuates itself. I've filed Bug 1885195 to look into changing this behavior because, at first glance, that doesn't seem like the right thing to do. So the most recent `update_messages` logs are telling the updater not to use the Maintenance Service for that reason. Could you attach the older `update_messages`? I'm hoping that one of the older ones will have the _original_ cause of using a UAC when we shouldn't be. Maybe consider zipping them or something just to keep the number of attachments on this bug from getting ridiculous.