Windows time stays at the time of the last shutdown time

[s1t2y3a3m6]

Windows time stays at the time of the last shutdown and starts from last shutdown time when I turn ON

Basically date and time paused after every shutdown

replaced cmos battary, flashed bios, reset windows time registry but nothing worked

Everytime I have to synchronise time after PC turn on.

If anyone have solution and knowledge to this issue then please share.

 

[tachniki]

Can you please check if bios time is working correctly and issue is only with windows?

If bios time is correct, see if time service in services.msc is running and set to automatically start?

 

[s1t2y3a3m6]

Can you please check if bios time is working correctly and issue is only with windows?

If bios time is correct, see if time service in services.msc is running and set to automatically start?

Problem is with BIOS only but if BIOS corrupted or any issue related to BIOS then how it could able to store exactly same shut down time and starts from same shutdown time when I turn on ? Not even a second mismatch.

 

[Mruseless]

Problem is with BIOS only but if BIOS corrupted or any issue related to BIOS then how it could able to store exactly same shut down time and starts from same shutdown time when I turn on ? Not even a second mismatch.

Check its CMOS battery may be battery is dead

 

[Mruseless]

Replace it with new one

 

[s1t2y3a3m6]

Replace it with new one

Already done bro

 

[cardy]

Solutions
First of all if you don't know about system management much, don't apply/use any settings or cmd or powershell that you can't restore.

In that case contact a technician. Otherwise proceed by first backing up important files.

If you use desktop for storing files and folders be extra cautious and make backup to drives other than c drive.

Then create a system restore point.

And try the following for troubleshooting and see if works one by one.

1. Re-register and restart Windows Time Service
Run Command Prompt as Administrator and execute:
net stop w32time
w32tm /unregister
w32tm /register
net start w32time
w32tm /resync
Then restart the PC. This rebuilds Windows' time synchronization configuration


2. Disable Fast Startup
Go to Control Panel → Power Options → Choose what the power buttons do.Click “Change settings that are currently unavailable.”Uncheck “Turn on fast startup (recommended)” → Save changes.
Disabling this removes any hibernated time state.

3. Verify BIOS jumper and RTC clockEnsure the CMOS/CLR jumper is not left in the “RESET” position. Enter BIOS setup and confirm the clock increments normally after a few minutes with the system off .

4. Adjust RTC/Windows Time UTC Matching

If the device used to dual-boot with Linux or macOS:Boot into BIOS and check that the RTC clock is set to Local time, not UTC.Alternatively, run PowerShell (Admin):

reg add "HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTimeZoneInformation" /v RealTimeIsUniversal /t REG_DWORD /d 0 /f

This resets Windows to local RTC interpretation.

5. Enable automatic NTP resync
Open “Services.msc”, locate Windows Time, set:Startup type: Automatic (Delayed Start).Service status: Running.
Click Apply → OK.
You can also configure resync upon boot using Task Scheduler to run:w32tm /resyncat logon.


6. Check firmware or OS corruption

If all else fails, consider:Updating the motherboard BIOS again with the latest version.SFC scan:sfc /scannowDISM repair😀ISM /Online /Cleanup-Image /RestoreHealthThese resolve time service corruption or driver-level RTC sync bugs.


If this issue persists even with the above steps, the problem likely lies in BIOS-level RTC communication — a BIOS bug or rare hardware fault where the RTC read function fails during cold boot. In that case, contact the motherboard manufacturer to check for firmware updates addressing RTC read delay or offset issues.

 

[cardy]

Already done bro

Oops.
I am late it seems

 

[s1t2y3a3m6]

Solutions
First of all if you don't know about system management much, don't apply/use any settings or cmd or powershell that you can't restore.

In that case contact a technician. Otherwise proceed by first backing up important files.

If you use desktop for storing files and folders be extra cautious and make backup to drives other than c drive.

Then create a system restore point.

And try the following for troubleshooting and see if works one by one.

1. Re-register and restart Windows Time Service
Run Command Prompt as Administrator and execute:
net stop w32time
w32tm /unregister
w32tm /register
net start w32time
w32tm /resync
Then restart the PC. This rebuilds Windows' time synchronization configuration


2. Disable Fast Startup
Go to Control Panel → Power Options → Choose what the power buttons do.Click “Change settings that are currently unavailable.”Uncheck “Turn on fast startup (recommended)” → Save changes.
Disabling this removes any hibernated time state.

3. Verify BIOS jumper and RTC clockEnsure the CMOS/CLR jumper is not left in the “RESET” position. Enter BIOS setup and confirm the clock increments normally after a few minutes with the system off .

4. Adjust RTC/Windows Time UTC Matching

If the device used to dual-boot with Linux or macOS:Boot into BIOS and check that the RTC clock is set to Local time, not UTC.Alternatively, run PowerShell (Admin):

reg add "HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTimeZoneInformation" /v RealTimeIsUniversal /t REG_DWORD /d 0 /f

This resets Windows to local RTC interpretation.

5. Enable automatic NTP resync
Open “Services.msc”, locate Windows Time, set:Startup type: Automatic (Delayed Start).Service status: Running.
Click Apply → OK.
You can also configure resync upon boot using Task Scheduler to run:w32tm /resyncat logon.


6. Check firmware or OS corruption

If all else fails, consider:Updating the motherboard BIOS again with the latest version.SFC scan:sfc /scannowDISM repair😀ISM /Online /Cleanup-Image /RestoreHealthThese resolve time service corruption or driver-level RTC sync bugs.


If this issue persists even with the above steps, the problem likely lies in BIOS-level RTC communication — a BIOS bug or rare hardware fault where the RTC read function fails during cold boot. In that case, contact the motherboard manufacturer to check for firmware updates addressing RTC read delay or offset issues.

Have already done 1,2,4,5,6
Done 3 now but issue persist

Thinking same, a rare hardware level fault
Now main issue is with MSI service, they literally take months to repair and seems no option left

 

[aayusharyan]

Also check whether that machine is connected to the internet and NTP servers are configured correctly... Might help as a blanket fix.