As a result, hard-to-track bugs can sometimes appear. While this generally works well, some applications rely on motherboard time being local time. This tweak will cause Windows to interpret the time stored on the motherboard as UTC, which macOS can then interpret as the correct time zone. You can also change the way that Windows views system time. Without changing the way one of the operating systems interpret the motherboard time, you’ll never get them to agree.įix Windows and macOS Showing Different Times When the operating systems are forced to share a time store, the clocks won’t sync.
The problem occurs when you dual boot a system, running Windows and macOS off the same motherboard.
Universal Time Code or Greenwich Mean Time) and apply a timezone offset to display local time.īoth of these systems work perfectly fine independently. macOS, on the other hand, will interpret the time on the motherboard as UTC (a.k.a. Windows assumes the local time is stored in the motherboard, so it doesn’t apply any kind of time zone offset. To account for time zones, different operating systems use different methods. This allows the computer to keep track of time even when turned off. Your computer stores the current time in a clock on your motherboard. You will need to make some registry changes in Windows, but if you follow the instructions carefully you shouldn’t have any problems. Fortunately, there’s a relatively easy fix for Windows and macOS showing different times when dual booting. This is because of a disagreement about time-keeping methodology between Windows and Unix-based operating systems. No matter how you change the clock in one OS, it doesn’t fix the problem with the other OS. If your system dual boots both Windows and macOS, you might notice that it’s impossible to get the system clocks to sync.