Solved Clock Jumps Ahead 5 Hours After Dual-Booting

[bishop101]

I have a dual-boot setup with W7 and linux distro, for some reason whenever I boot into Windows 7 after being in Linux my clock is always 5+ hours ahead. I end up having to synchronize it with the time.windows.com server.

This only happens if I go from Linux to Windows. If I use Windows and shut off and restart multiple times the time stays correct, this only happens after I log off from Linux and restart into Windows 7.

Any ideas?

 

[123386761]

Have you tried hitting ESC (upper right on the keyboard) when shuttng down Linux and see if there's anything about a time change?

Good luck
~123386761

 

[Sedril]

Is the clock in your bios set correctly?

 

[bishop101]

Have you tried hitting ESC (upper right on the keyboard) when shuttng down Linux and see if there's anything about a time change?

Good luck
~123386761

No messages regarding the clock appear, only messages like 'stopping kernel'.

Is the clock in your bios set correctly?

I went into the BIOS and the clock was incorrect, I changed it to the correct time and then booted into Linux. After shutting down and rebooting I went into BIOS and discovered that it was changed back to the incorrect time. It seems that Linux is changing the time in BIOS.

 

[seekermeister]

It seems obvious that Linux is resetting your BIOS's clock and when you syncronize time in Windows, it is resetting the BIOS time. I can't remember clearly the details, but during installation of Linux, it gave the option of what time it was to use. Again, I'm not sure of the remedy, but somewhere in Linux, there is a way to reset this characteristic.

 

[bishop101]

Ok thanks, I will ask on a Linux forum.

 

[logicearth]

It is Linux, it is setting the BIOS time to UTC while Windows sets the BIOS to local time.
Why does Windows keep your BIOS clock on local time? - The Old New Thing - Site Home - MSDN Blogs

 

[Mark Phelps]

IF you're the same person who posted this to the Ubuntu forums, I answered your thread there already. The fix is to force Ubuntu to use "local" time, not UTC time.