Hello all,
I have been facing a weird problem since a couple of months. The system clock toggles between UTC and my local time.

I have a dual boot HP laptop running Windows 10 and Windows 11. There is no problem here.

For the last couple of years, I have been carrying a "Portable" Windows 11 in a USB drive when I go on a tour. The WindowsToGo is created using WinToUSB app and has been serving me well. There were no issues.

Now, for the last couple of months or so, I have noticed that the Time shown in the Windows clock, running the USB WinToGo and the regular laptop Windows, differ by a 5.30 hours, the difference between UTC and my Regional time.
If I sync my clock in the WinToGo, then the clock is Advanced by 5.30 hours when I run the laptop OS.
If I sync my Laptop OS, then the clock in the WinToGo is delayed by 5.30 hours.
I have spent quite some time following the advice in the Microsoft sites, but have not come across any solution.

I am quite certain that I have not erred in creating the WinToGo OS, I have been doing it for a couple of years and the issue is recent. Maybe the latest release of Windows 11 having this issue?

Any lead is welcome. Thanks.

 

Things like that usually happen when the actual computer hardware time clock is not set to always be UTC. Keep the computer hardware on UTC and just use timezones to offset to local for display and program usages. Likely buggy windows programming that don't do this correctly is also a problem

 

Things like that usually happen when the actual computer hardware time clock is not set to always be UTC. Keep the computer hardware on UTC and just use timezones to offset to local for display and program usages. Likely buggy windows programming that don't do this correctly is also a problem

Surprising. First time I'm hearing about the Hardware Clock being required to be set to UTC . For the last 20 years I've been using computers, the clock has always been on the local time. Never had any issues.
The present kink, I suspect, is a bug in the Windows updates.

 

Surprising. First time I'm hearing about the Hardware Clock being required to be set to UTC . For the last 20 years I've been using computers, the clock has always been on the local time. Never had any issues.
The present kink, I suspect, is a bug in the Windows updates.

My Linux machined all have the HW clock set to UTC that is disciplined by a gps time standard.
https://answers.microsoft.com/en-us...-windows/a9914172-c857-451f-882f-cb06325eb39d

All my windows machines use the Linux ntp time server to sync their local clocks with TZ offsets for the correct local time

Windows is the oddball here