UpdateVM pref not sticking

[Micah Lee]

When I installed Qubes 4.0 I chose to install all of my updates over Tor. Since then, I've opened Qubes Global Settings and changed UpdateVM to sys-firewall.

When I install dom0 updates, this seems to work fine. It says `Using sys-firewall as UpdateVM to download updates for Dom0`.

But when I try installing updates in my templates, such fedora-26, it still uses sys-whonix as the UpdateVM. I'm sure because as soon as I try installing updates, sys-whonix starts, and if I shut it down in the middle of updates, the updates fail. (And also the downloads are very slow.)

I'd like to be able to control which UpdateVM my templates use to update. Any idea how I can troubleshoot what's going on?
​

[Micah Lee]

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

Looking at another thread going on right now, I found this useful:
https://groups.google.com/forum/#!searchin/qubes-users/Whonix%7Csort:date/qubes-users/gLqORddxb-Y/mDxXDi3cAwAJ

I can edit /etc/qubes-rpc/policy/qubes.UpdatesProxy, and change target=sys-whonix to target=sys-net. After I do that, my template seems to use sys-net as the UpdateVM.

This seems like a bug though. Shouldn't this file change when I change Qubes Global Settings?

[Unman]

This has come up before - it's the same situation as in 3.2 with "Global
Settings" in Qubes manager.
The term "Global" here, doesnt mean "across the board": it's what
applies to dom0. I think this is somewhat misleading, but it's how it
is.
So not a bug, but misleading.

[MirrorWay]

I was confused by the same thing - https://github.com/QubesOS/qubes-issues/issues/3527