Contribute
Register

Mac OS X resets time in Windows 7

Status
Not open for further replies.
Joined
Jan 3, 2011
Messages
11
Motherboard
Windows 8.1 Pro, Mac OS X Mavericks 10.9
CPU
Intel Haswell Xeon E3 1230v3 3,30Ghz
Graphics
AMD Radeon HD7950
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. Android
  2. iOS
Hi guys,

got a little problem here after successfull installed Mac OS X Lion.
When reboot or shutdown from Mac OS the clock in Windows is always set 2 or 1 hour back.

E.G.: In Mac OS the time is 12:00, then I boot into Windows the time is 10:00, so I have to manually sync the time clock with the servers and its really annoying.

I got this problem since I installed Mac OS, so Leopard, Snow Leopard and now Lion.

Anyone who also has this problem or already solved?

Cheers
 
This worked for me:

1. Click Start, type services.msc and hit ENTER.
2. Locate Windows Time.
3. Right-click and select Restart (or Refresh).

Update: did not work.
 
LINGja said:
Hi guys,

got a little problem here after successfull installed Mac OS X Lion.
When reboot or shutdown from Mac OS the clock in Windows is always set 2 or 1 hour back.

E.G.: In Mac OS the time is 12:00, then I boot into Windows the time is 10:00, so I have to manually sync the time clock with the servers and its really annoying.

I got this problem since I installed Mac OS, so Leopard, Snow Leopard and now Lion.

Anyone who also has this problem or already solved?

Cheers
You now have a working installation dual booting with OS X and Windows 7 on the same hard drive. Which has a problem with the clock - Windows 7 wants to use local time and OS X wants to use UTC. To fix this problem:

1. Boot Windows

2. Click Start -->type regedit in the 'Search Programs and Files' box. Click on regedit.exe in the box above that appears. Type in passward if popup appears and asks for one. When the "Do you want to allow this program to change your machine" box pops up click yes.

3. The Windows Registry Editor should pop up.
Navigate within the explorer to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

4. Click on the TimeZoneInformation "folder" from the navigation pane if you haven't already done so.

5. This assumes the correct key doesn't exist. If it does, you will just change the existing key's value: Right click on the white space within the folder (If you don't have a right mouse button, you may need to download a program called applemouse to emulate the "control-click" of the apple 1-button mouse).
Select new --> DWORD Value. Title the key "RealTimeIsUniversal" (No quotes). Set the value to "1" (No quotes again).

6. Either reboot and set the clock in MacOS or set the clock in Windows. You should now be able to reboot into either OS and have a correct clock.
 
@Going Bald
I have the two systems on seperate hard drives, but anyway it worked.
A nother question:

I have a 64-Bit system (Lion and Windows), does it make a diffrence if I use QWORD instead of DWORD? Because it says "DWORD(32bit)" and "QWORD(64bit)" ?

Thanks for the reply.

The solution from JackArrgon isn't solving the problem at his root, its just a walk around, but still nice, it also work. :D

Cheers
 
If your Windows is 64 bit use the DWORD 64Bit value.
 
LINGja said:
@Going Bald
I have the two systems on seperate hard drives, but anyway it worked.
A nother question:

I have a 64-Bit system (Lion and Windows), does it make a diffrence if I use QWORD instead of DWORD? Because it says "DWORD(32bit)" and "QWORD(64bit)" ?

Cheers
Makes no difference whatsoever. I am running 64-bit Win7 Ultimate and Lion 64-bit and my RealTimeIsUniversal fix is 32-bit dword done back when I was running Snow Leopard.
 
You now have a working installation dual booting with OS X and Windows 7 on the same hard drive. Which has a problem with the clock - Windows 7 wants to use local time and OS X wants to use UTC. To fix this problem:

1. Boot Windows

2. Click Start -->type regedit in the 'Search Programs and Files' box. Click on regedit.exe in the box above that appears. Type in passward if popup appears and asks for one. When the "Do you want to allow this program to change your machine" box pops up click yes.

3. The Windows Registry Editor should pop up.
Navigate within the explorer to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

4. Click on the TimeZoneInformation "folder" from the navigation pane if you haven't already done so.

5. This assumes the correct key doesn't exist. If it does, you will just change the existing key's value: Right click on the white space within the folder (If you don't have a right mouse button, you may need to download a program called applemouse to emulate the "control-click" of the apple 1-button mouse).
Select new --> DWORD Value. Title the key "RealTimeIsUniversal" (No quotes). Set the value to "1" (No quotes again).

6. Either reboot and set the clock in MacOS or set the clock in Windows. You should now be able to reboot into either OS and have a correct clock.


Microsoft support has stated over and over that this is an unsupported and unstable workaround. There is a Microsoft knowledge base article that states the downfall of using this workaround. Two biggest issues: Windows update may fail to start, or Windows update may run with the wrong timestamp and produce a system that will not start (except in safe mode).
 
Microsoft support has stated over and over that this is an unsupported and unstable workaround. There is a Microsoft knowledge base article that states the downfall of using this workaround. Two biggest issues: Windows update may fail to start, or Windows update may run with the wrong timestamp and produce a system that will not start (except in safe mode).

Been running Windows 7 Ultimate 64 bit with this fix since December of 2009. I have run every Windows update between then and now and have never had any problems. Time stamps are correct in my logs and it has never had any problem booting.

Please link the knowledge base article you are referring to.
 
Been running Windows 7 Ultimate 64 bit with this fix since December of 2009. I have run every Windows update between then and now and have never had any problems. Time stamps are correct in my logs and it has never had any problem booting.

Please link the knowledge base article you are referring to.

Nice to know. I've been looking for a more up-to-date workaround, but no one else seems to have a solution.

Microsoft Knowledge Base Article: http://support.microsoft.com/kb/2687252
 
i use that method, and have noticed no issues on windows 7 home premium 64bit
 
Status
Not open for further replies.
Back
Top