When your Windows clock shifts forward or backward by several hours every time you reboot from Linux into Windows, the two operating systems are interpreting your motherboard's hardware Real-Time Clock (RTC) using different time standards. By default, Windows 10 and Windows 11 assume the hardware RTC stores local time, while most Linux distributions assume the hardware RTC stores Coordinated Universal Time (UTC) and apply a time zone offset at boot. To fix this permanently on Windows 10 and Windows 11, you must either configure Linux to maintain the hardware RTC in local time using timedatectl set-local-rtc 1 or configure Windows to read the hardware RTC as UTC by setting the RealTimeIsUniversal registry value under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation, then resynchronize the Windows Time service (w32time). Applying only one of these two adjustments ensures both operating systems agree on what the motherboard clock represents.

A Windows and Linux desktop comparison shows both systems’ clocks and calendars synchronized to 14:00. Why Dual-Booting Breaks the System Clock​

Every PC motherboard includes a battery-backed hardware clock—called the Real-Time Clock (RTC) or CMOS clock—that keeps track of elapsed time while the machine is powered off. The RTC stores only basic date and time values (Year, Month, Day, Hour, Minute, and Second) without storing an active operating system time zone offset.

Because the hardware clock has no built-in time zone awareness, each operating system must assume a convention when reading from or writing to it:

  • Windows default (Local Time): Windows reads the value in the RTC and displays it directly as your local wall-clock time. When Windows synchronizes with an Internet time server (NTP) or shuts down, it writes your local time back into the RTC.
  • Linux default (UTC): Most Linux distributions (and macOS) treat the value inside the RTC as Coordinated Universal Time (UTC/GMT). When Linux boots, it reads the RTC, applies your configured regional time zone offset (such as UTC-5 for Eastern Standard Time or UTC+1 for Central European Time), and displays the calculated local time. When Linux syncs with an NTP server, it writes the UTC time back to the hardware clock.

If you live in New York (UTC-5) and boot into Linux at 2:00 PM local time, Linux synchronizes its clock via NTP and writes 19:00 (7:00 PM UTC) into the motherboard's RTC. When you restart into Windows, Windows reads 19:00 from the RTC, assumes that value is already Eastern Time, and displays 7:00 PM in your system tray until the Windows Time service eventually triggers a background sync. Conversely, if you live in a positive offset (such as UTC+2), Windows will appear two hours behind after booting from Linux.

Prerequisites and Pre-Flight Checks​

Before changing how either operating system handles the hardware clock, verify your privileges and choose which convention you want your system to use.

  • Administrator or root access: Modifying the Windows Registry or controlling the Windows Time service requires a local Administrator account in Windows 10 or Windows 11. Modifying the RTC convention in Linux requires sudo or root privileges.
  • Active Internet connection: Required to perform a final Network Time Protocol (NTP) resynchronization after aligning the clock standard.
  • Choose only one convention: You must either set Linux to use local time or set Windows to use UTC. Do not apply both procedures, or you will invert the mismatch and recreate the exact same offset problem in reverse.

Deciding Which Operating System to Change​

Both methods work reliably on modern systems, though each carries minor trade-offs documented by the systemd project and the Arch Linux documentation:

  • Method 1: Configure Linux to use Local Time (Simplest from the Windows side): Avoids undocumented Windows Registry modifications and keeps the UEFI/BIOS setup screen showing your familiar local wall-clock time. However, the timedatectl manual pages note that maintaining the RTC in local time on Linux is not fully supported by all early-boot kernel services and can occasionally cause daylight saving time (DST) double-adjustments or UTC timestamp discrepancies on FAT32/exFAT partitions mounted in Linux.
  • Method 2: Configure Windows to use UTC (Recommended by ArchWiki for multi-boot setups): Keeps the hardware clock in universal time, preventing daylight saving time conflicts between operating systems and ensuring consistent behavior across time zone changes if you travel with a laptop. As a side effect, the clock displayed inside your motherboard's UEFI/BIOS firmware utility will show UTC time rather than local time.

Verify Time Zone Settings and Current RTC Status​

Before changing registry keys or Linux configuration files, verify that both operating systems are actually set to the same geographical time zone. Sometimes an apparent RTC conflict is simply one OS still configured for Pacific Time (UTC-8) or UTC after a fresh OS installation.

Check Time Zone Settings in Windows 11​

Windows 11 Settings on Time & language > Date & time — showing Set time automatically, Set time zone automatically, and the Time zone selector (the manual Change button is hidden w

  • Press Win + I to open the Settings app.
  • Select Time & language in the left sidebar, then click Date & time.
  • Check the Time zone dropdown menu and confirm it matches your exact regional time zone (for example, (UTC-05:00) Eastern Time (US & Canada)).
  • If your time zone supports daylight saving time, verify that Adjust for daylight saving time automatically is toggled On.
  • Leave Set time automatically toggled On.

Check Time Zone Settings in Windows 10​

  • Press Win + I to open Settings, then click Time & Language.
  • Select Date & time in the left navigation pane.
  • Verify the Time zone dropdown menu shows your correct local region.
  • Ensure Adjust for daylight saving time automatically (if applicable to your region) and Set time automatically are both switched On.

Check Time Zone and RTC Mode in Linux​

Some Linux installers (including certain versions of Ubuntu and Linux Mint) automatically set Linux to use local time if they detect an existing Windows Boot Manager partition during installation. To see what your Linux distribution is currently doing:

  • Boot into your Linux distribution and open a terminal window.
  • Run the following status command:
    timedatectl status
  • Inspect the output lines:
  • Time zone: Confirm this matches the same geographic region configured in Windows.
  • RTC in local TZ: If this reads no, Linux is treating the hardware clock as UTC (the default). If it reads yes, Linux is already configured to use local time.

Method 1: Configure Linux to Use Local Time (Matches Windows Default)​

If you prefer to leave Windows 10 or Windows 11 in its default factory configuration and keep your motherboard BIOS/UEFI clock displaying local time, instruct your Linux system's systemd time manager to store local time in the RTC. This procedure works on Ubuntu, Debian, Fedora, Linux Mint, Arch Linux, openSUSE, Red Hat Enterprise Linux, and any other Linux distribution using systemd.

  • Boot into your Linux installation and open a terminal.
  • Run the following command to switch the RTC convention to local time and immediately recalculate the system clock from the RTC:
    sudo timedatectl set-local-rtc 1 --adjust-system-clock
  • Enter your user password if prompted. This command updates /etc/adjtime so the setting persists across reboots.
  • Verify the change took effect by running:
    timedatectl
  • Check the bottom of the output. The line RTC in local TZ will now display yes, followed by a standard warning from systemd noting that local RTC mode is not fully supported for daylight saving changes.
  • Restart your computer and boot into Windows 10 or Windows 11.
  • Once inside Windows, follow the steps in the Resynchronize the Windows Clock and Time Service section below to write the verified local time to the motherboard RTC.

Rollback: Restore Linux to UTC Mode​

If you later remove Windows or decide to switch to the Windows UTC registry method instead, revert Linux back to the UTC hardware clock standard by opening a Linux terminal and running:

sudo timedatectl set-local-rtc 0 --adjust-system-clock

Method 2: Configure Windows 10 and Windows 11 to Use UTC (Matches Linux Default)​

If you prefer to keep your hardware clock in UTC—or if you dual-boot with a Linux distribution where you want to avoid systemd local-RTC warnings—you can instruct Windows 10 and Windows 11 to treat the motherboard RTC as UTC.

Warning: Modifying the Windows Registry incorrectly can cause system instability. Follow the exact key path and value name below, and do not modify other values under TimeZoneInformation. When RealTimeIsUniversal is enabled, your motherboard's UEFI/BIOS setup screen will display UTC time instead of local time.

Configure UTC Mode via Elevated Command Prompt or PowerShell​

The fastest and least error-prone way to add the registry value is using the built-in reg command.

  • In Windows 10 or Windows 11, press Win + X and select Terminal (Admin), PowerShell (Admin), or Command Prompt (Admin). Alternatively, press Win + S, type cmd, right-click Command Prompt, and select Run as administrator.
  • Click Yes at the User Account Control (UAC) prompt.
  • Run the following command to create the RealTimeIsUniversal 32-bit DWORD value set to 1:
    reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation" /v RealTimeIsUniversal /d 1 /t REG_DWORD /f
  • Confirm that the console outputs The operation completed successfully.
  • Restart your computer so the Windows kernel loads the new RTC interpretation at boot.

Configure UTC Mode via Registry Editor (GUI Alternative)​

If you prefer to inspect the registry key visually using Registry Editor:

  • Press Win + R to open the Run dialog, type regedit, and press Enter.
  • Click Yes at the User Account Control prompt.
  • In the address bar at the top of Registry Editor, paste the following path and press Enter:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
  • Right-click an empty area in the right-hand pane and select New > DWORD (32-bit) Value. (Note: Even on 64-bit editions of modern Windows 10 and Windows 11, REG_DWORD is the standard value type supported by the OS. Only legacy 64-bit Windows 7 and early 2015 builds of Windows 10 required a 64-bit QWORD value.)
  • Name the new value exactly:
    RealTimeIsUniversal
  • Double-click RealTimeIsUniversal, enter 1 in the Value data field, leave the base set to Hexadecimal, and click OK.
  • Close Registry Editor and restart Windows.

Rollback: Restore Windows to Local Time Mode​

To return Windows 10 or Windows 11 to its default behavior (interpreting the hardware clock as local time):

  • Open an elevated Command Prompt or Terminal (Admin).
  • Run the following command to delete the RealTimeIsUniversal value:
    reg delete "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation" /v RealTimeIsUniversal /f
  • Restart your computer and resynchronize your Windows clock.

Resynchronize the Windows Clock and Time Service​

After aligning the RTC convention in either Linux or Windows, the hardware clock may still hold the old shifted timestamp from your previous boot. You must force an immediate NTP synchronization so the correct time is written to both the OS clock and the motherboard RTC.

Resynchronize via Windows Settings​

On Windows 11​

  • Press Win + I and go to Time & language > Date & time.
  • Confirm Set time automatically is toggled On. (If your clock has not updated after a reboot, toggle Set time automatically to Off, wait two seconds, and toggle it back On.)
  • Scroll down to the Additional settings section and click the Sync now button.
  • Wait for the checkmark and the updated timestamp under Last successful time synchronization beneath Sync now.

On Windows 10​

  • Press Win + I and go to Time & Language > Date & time.
  • Ensure Set time automatically is toggled On.
  • Scroll down to the Synchronize your clock heading and click the Sync now button.
  • Confirm a recent timestamp appears below the button indicating the sync completed.

Force Resynchronization via Command Prompt (w32tm)​

If the Sync now button in Settings hangs or reports that time synchronization failed, use the Windows Time command-line utility (w32tm) to restart the service and force an immediate update.

  • Open Command Prompt or Windows Terminal as an administrator.
  • Start or restart the Windows Time service by running:
    Code:
    net stop w32time
    net start w32time
  • Force an immediate clock resynchronization:
    w32tm /resync
  • Verify the output reads:
    Code:
    Sending resync command to local computer
    The command completed successfully.

Verification of Success​

To confirm the dual-boot clock conflict is permanently resolved, perform a round-trip reboot test across both operating systems:

  • In Windows, check the system tray clock and verify the time and date are accurate.
  • Open an elevated Command Prompt and check the current registry and NTP status by running:
    w32tm /query /status
    Verify that Last Successful Sync Time shows a current timestamp and Source lists a valid NTP server (such as time.windows.com or pool.ntp.org) rather than Local CMOS Clock.
  • Restart the computer (use Restart, not Shut down, to bypass Windows Fast Startup caching) and boot into Linux.
  • Confirm the Linux desktop clock displays the exact same local time, and run timedatectl status in a terminal to ensure System clock synchronized: yes is active.
  • Restart from Linux back into Windows.
  • Check the Windows lock screen and taskbar clock immediately upon login. The clock should show the exact local time immediately at boot without jumping or waiting for a manual sync.

Troubleshooting Common Dual-Boot Clock Failures​

If your clock continues to drift, show the wrong hour, or fail synchronization after applying one of the methods above, match your symptom to the fixes below.

  • Symptom: w32tm /resync fails with "The service has not been started. (0x80070426)"
  • Cause: The Windows Time service (W32Time) is set to Manual or Disabled and has stopped running in the background.
  • Fix: Press Win + R, type services.msc, and press Enter. Scroll down to Windows Time, double-click it, change Startup type from Manual (or Disabled) to Automatic, click Start if the service is stopped, and click OK. Then re-run w32tm /resync in an elevated Command Prompt.
  • Symptom: w32tm /resync fails with "The computer did not resync because no time data was available"
  • Cause: Your ISP, router, or corporate firewall is blocking outbound UDP port 123 to time.windows.com, or the default Windows time server is unresponsive.
  • Fix: Configure Windows to use the public NTP pool alongside Microsoft's server. Open an elevated Command Prompt and run the following commands in order:
    Code:
    w32tm /config /manualpeerlist:"time.windows.com,0x8 pool.ntp.org,0x8" /syncfromflags:manual /reliable:YES /update
    net stop w32time
    net start w32time
    w32tm /resync /rediscover
  • Symptom: The clock is still off by the exact same number of hours after a reboot
  • Cause: Either both operating systems were changed at the same time (for example, setting RealTimeIsUniversal=1 in Windows and set-local-rtc 1 in Linux), or on an older Windows 10 build, RealTimeIsUniversal was created in the wrong registry path.
  • Fix: Run timedatectl status in Linux and reg query "HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation" /v RealTimeIsUniversal in Windows. If RTC in local TZ: yes is active in Linux, RealTimeIsUniversal must not exist (or must be 0) in Windows. If RTC in local TZ: no is active in Linux, RealTimeIsUniversal must be 0x1 in Windows.
  • Symptom: The clock resets to a specific old year (such as 2000, 2018, or 2021) whenever the PC is unplugged or powered off overnight
  • Cause: The CR2032 coin-cell CMOS battery on the motherboard is depleted and can no longer power the RTC chip when standby power is removed.
  • Fix: Software settings cannot preserve time on an unpowered RTC. Power down the PC, unplug the power cable, open the chassis, and replace the motherboard CR2032 battery. Afterward, set the date and time inside the UEFI/BIOS setup utility and boot into Windows to resynchronize.
 

Last edited by a moderator: