Share via

Windows 11 time wrong if the system is off for more than a few hours after upgrade to 25H2

Robert Williams 0 Reputation points
2025-12-09T00:11:22.31+00:00

I have a handful of windows 11 laptops that, since upgrading to 25H2, consistently lose their system time if the system has been turned off for at least a couple of hours. Because we use 2FA to log into our windows systems, this causes the 2FA to fail due to the time being off. The only way i can fix it is to RMM into the laptop and either reset the time or sometimes (but not always) use the w32tm /resync command to update the time. IF it works, then they can log on and it's not a problem. Sometimes it doesn't work and gives an error like "no time data is available" which to me sounds like the windows time service is turned off. When i go check it, the service shows as running, and if I try to sync again it gives the same error. If I stop/start the time service, then it works fine. This pretty consistently happens to these particular laptops nearly every day. I've tried running a scheduled task to stop/start the service after boot (not login) but it still doesn't run until the user logs in, so i haven't been able to get this issue resolved. The rest of our laptops that are the same model, don't have this issue. I've checked the windows time settings and they are all correct, I've checked our domain NTP service and it's working correctly. It's just these 4 computers, one of which just started having this issue this morning after it ran the 25H2 upgrade/patch through windows update.

Has anyone else seen this issue or happened to find a way to resolve this? Any guesses are welcome at this point.

Any ideas would be appreciated.

Thanks

Bob

Windows for business | Windows Client for IT Pros | Devices and deployment | Other
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Brian Huynh 2,965 Reputation points Microsoft External Staff Moderator
    2025-12-09T01:00:58.9333333+00:00

    Hello,

    Based on the symptoms, this usually points to a conflict with Secure Time Seeding or Fast Startup features in the new Windows update (likely 24H2).

    Here is the solution to resolve this:

    Step 1: Disable "Secure Time Seeding"

    1. Open Registry Editor (regedit) as Administrator.
    2. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
    3. Locate UtilizeSslTimeData.
    4. Change the value to 0.
    5. Restart the laptop.

    Step 2: Reset the Windows Time Service Configuration

    Run the following commands in an Administrator Command Prompt:

    net stop w32time
w32tm /unregister
w32tm /registernet start w32time
w32tm /resync /rediscover

    Step 3: Disable Fast Startup

    1. Open Control Panel > Power Options > Choose what the power buttons do.
    2. Click Change settings that are currently unavailable.
    3. Uncheck Turn on fast startup.
    4. Save changes.

    Please let me know if this stabilizes the time on your laptops. I am happy to follow up if you need further assistance.

    If this answer solved your issue, please click "Accept Answer". This helps others with the same problem find the solution.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

  2. AI answer

    2025-12-09T00:11:34.9466667+00:00

    It seems that you are experiencing issues with the Windows time service on your laptops after upgrading to Windows 11 version 25H2. This problem can occur due to various reasons, including issues with the Windows Time service itself or the Secure Time Seeding feature.

    Here are a few troubleshooting steps you can consider:

    1. Check Windows Time Service: Ensure that the Windows Time service is set to start automatically. You can do this by running services.msc, locating the Windows Time service, and checking its properties.
    2. Force Resynchronization: If you encounter the "no time data is available" error, you might want to try stopping and starting the Windows Time service manually using the following commands in an administrative Command Prompt: 
         net stop w32time
   net start w32time
   w32tm /resync /force
      This may help in cases where the service appears to be running but is not functioning correctly.
    3. Registry Settings: If the issue persists, consider checking the registry settings for the Windows Time service. You can clear the W32time registry values to force synchronization with the internal NTP server. This can be done by running the following commands: 
         net stop w32time
   w32tm.exe /unregister
   w32tm.exe /register
   net start w32time
   w32tm.exe /resync /force
    4. Secure Time Seeding: If your laptops are in an environment where they may not have consistent internet access, consider disabling the Secure Time Seeding feature. This can be done by modifying the registry: 
         reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config /v UtilizeSslTimeData /t REG_DWORD /d 0 /f
      After making this change, restart the computer and then run the synchronization commands again.
    5. Scheduled Task: Since you mentioned that a scheduled task to restart the service after boot does not run until the user logs in, you might want to set the task to run at system startup instead of user login. This can be configured in the task properties under the "Triggers" tab.

    If these steps do not resolve the issue, it may be worth checking for any specific updates or patches related to the 25H2 version that address time synchronization issues.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.