Wrong time by 7 hours... in the future?

[Fierelier]

@UCyborg I've tried to make a fix, but I've not been able to reproduce the correct behavior with bTimeAdjustmentDisabled set to FALSE via MinGW. After one hour, the time is still changed.

It's hard to check if applying the property succeeded as well, because GetSystemTimeAdjustment fails with error 203 - ERROR_ENVVAR_NOT_FOUND - "The system could not find the environment option that was entered".

If anyone is interested in looking into it, I've shared the source code here: https://git.lumen.sh/Fierelier/winutcfix
.EXE (sha256: f594d6112c8c64928b74bcff5c0c608d27a2c7003bf7d4548c2b503ecf1d8507): http://fier.me/software/winutcfix.exe

Maybe this just doesn't work with MinGW but I'm trying not to spend too much time on one project right now, and I don't feel like installing Visual Studio.

Edited July 1 by Fierelier

[tekkaman]

I had this problem with a Gigabyte AM3 motherboard I bought back in 2014. In 2023 it started having those symptoms. It would go into the future. I would fix it and then the next day it was in the future again. Later I would physically see the clock moving faster and XP would behave weirdly like if it was in fast forward. Like even the Loading bootscreen would move very fast. Anyways it lasted for a few months like that until eventually it died and wouldn't boot anymore. I'm just giving the example because it could be a hardware issue. Linux didn't show the problem because it would sync online immediately at boot.