(All versions) Whonix Updates forbidden due to needing to wait several hours for the update to be "available"?

[gimmy]

Sdwdate says it’s done it’s thing and loaded the whonix firewall, but never allows me to download it because it says I’m supposed to wait several hours for the updates to become available. I wait the 7 hours, press update, and it tells me I have to wait 7 hours for the update to be available to me.

Every version of Qubes for years does this to me

[apparatus]

This seems to be a problem with timezone:

Understanding and fixing issues with time/clock

Architecture Timezone The system’s timezone is set in dom0. VMs can read the system’s timezone value from dom0 through the QubesDB qubes-timezone key. On Linux VMs with qubes-core-agent installed the time zone is set at boot time by the /usr/lib/qubes/init/qubes-early-vm-config.sh script. Clock synchronization “ClockVM” One of the VMs is defined globally as “clockVM”, from which other VMs and dom0 will synchronize their clock with. The following command in dom0 shows which VM has this role…

[gimmy]

But when I wait the 7 hours, it immediately resets and says I need to wait another 7 hours. So what geographic location suits dom0?

[apparatus]

What is your time in BIOS? Is it set to UTC or to your local time?

@taradiddles

MS Windows was used before installing Qubes OS (or in the case of dual-boot installations). Windows stores the time in the hardware clock as “local time” while Linux stores the time as UTC.

[gimmy]

Local I think, but I can check tomorrow. Thanks

[gimmy]

Changing it to UTC didn’t survive rebooting and restarting the systems clock sync had no effect

*No reboot and resetting to UTC fixed it. Thanks