![]() This assumes the correct key doesn't exist. Click on the TimeZoneInformation "folder" from the navigation pane if you haven't already done so.ĥ. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformationĤ. ![]() The Windows Registry Editor should pop up. The short solution for people who know how to edit the registry:Ī DWORD key called HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\RealTimeIsUniversal needs to have the value of "1"Ģ. I am not responsible if you mess something up. *** WARNING: Editing your registry improperly can render your Windows installation inoperable. To fix this, you need to add a key to your Windows system registry to tell Windows that your hardware clock will always be GMT. If the hardware clock is being set to "GMT," when it's actually the local time, Windows will pick this setting up as local time as it did before. This explains why the people who set their MacOS clock to GMT got the right time in Windows. When you boot Windows, Windows assumes your clock is set to your local timezone because that's what Windows does by default. The problem with the Windows clock being off is because the hardware clock (the one on your actual motherboard) is being set to "Universal" time, or GMT, when you shut down your MacOS bootup. Maybe this will help others with the same issue: Luckily, I found this after doing a google search. ![]() I had an issue with my system clock wherein the time was almost always wrong at startup for either Windows XP or OSx86.
0 Comments
Leave a Reply. |