In this text, we’ll contemplate why the system clock shows incorrect time and date after a shutdown, restart or resuming from hibernation of a laptop computer/laptop/server. Time is reset every time and you’ve got to set it manually. We’ll dwell on the most common case: a rundown BIOS battery and extra attention-grabbing ones involving Windows/Linux twin boot on one laptop, and a firmware bug on HPE ProLiant G9 /G8 servers with Windows Server OS.
System Not Saving Data/Time Due to Weak BIOS/CMOS Battery
The typical reply to the query “Why are the time and date reset on my laptop after reboot?” is the BIOS (CMOS) battery rundown. This battery is accountable for conserving BIOS/UEFI settings when your laptop or laptop computer is unplugged, and supplies autonomous operations of the built-in clock.
If the battery has run down, when the motherboard isn’t powered, BIOS can not hold its settings and all of them are reset, together with present date and time. If your laptop is kind of outdated, it is extremely doubtless that your battery is useless. We strongly suggest to substitute it. It isn’t onerous, and the method doesn’t require any particular engineering abilities. In most dwelling and even enterprise units an ordinary 3V CR2032 battery is utilized in BIOS.
If the battery alternative hasn’t helped, examine the state of the jumper used to reset BIOS settings (The jumper is positioned shut to the battery bay and is marked as CMOS / CLEAR / RESET). Somebody could have left it within the RESET place. Thus, every time when your motherboard is powered, BIOS settings are reset. Move the jumper to its regular place.
The subsequent choice is to replace BIOS firmware of your motherboard. See how to do it on the web site of your vendor. Newer firmware typically has completely different bugs mounted.
Windows: Set Clock Synchronization with time.home windows.com
If your date/time settings in Windows are consistently altering, initially it’s best to examine the present time zone settings and the parameters of time synchronization with the exterior time server. In Windows 10, you’ll be able to see the present time settings within the Control Panel -> Clock and Region -> Date and Time. In this instance, you’ll be able to see, that the time zone UTC + 01 is specified, and Daylight Saving Time is enabled.
If your laptop isn’t joined to the AD area, examine its time synchronization settings with the exterior time supply (NTP time server). To do it, click on Internet Time tab and guarantee that the automated synchronization with time.home windows.com server is about.
Troubleshooting time synchronization for AD domain-joined computer systems
If your laptop is a part of an Active Directory area, you want to perceive the structure of time synchronization within the AD area.
The following time synchronization scheme is used within the Active Directory area:
- The root area controller within the AD forest, to which the FSMO position of the PDC emulator belongs, is a time supply for all different DCs of this area;
- Other DCs synchronize time with PDC;
- Ordinary area members (servers and workstations) synchronize time with the closest accessible area controller in accordance to the AD topology.
Root PDC can synchronize its time with each an exterior supply and with itself (by default).
You can discover a area controller with the PDC position with the command:
netdom /question fsmo
To configure time synchronization with an exterior NTP server on the PDC, the next instructions are used.
Configure exterior time sources:
w32tm /config /manualpeerlist:"zero.nl.pool.ntp.org,0x1 1.nl.pool.ntp.org,0x1 2.nl.pool.ntp.org,0x1 three.nl.pool.ntp.org,0x1"
Make this DC a dependable time supply for the purchasers:
w32tm /config /dependable:sure
Restart w32 time server to synchronize DC time with nl.pool.ntp.org time servers:
internet cease w32time && internet begin w32time
You can view the synchronization supply and standing:
w32tm /question /friends
Start synchronization in handbook mode:
w32tm /resync /rediscover
Windows & Linux Showing Different Times When Dual Booting
We ought to individually contemplate the instances when two operation programs (Windows & Linux) are put in on a pc in Dual Boot configuration. You can come throughout the issue that after booting to one other system (booting to Linux after Windows) the time is a number of hours forward or late of the particular time.
Windows and Linux work with BIOS time in a different way. They are utilizing two completely different time codecs: UTC and localtime.
GNU/Linux operation programs (together with Mac OS X) assume the time in BIOS is in UTC format (GMT). Accordingly when booting, Linux converts the UTC time by including (or distracting) the offset of the present time zone chosen by the person. It implies that so as to get the native time for Athens time zone UTC+2, Linux will add 2 hours.
Windows thinks that point in BIOS is saved within the localtime format, and when you have specified a brand new time zone or synchronized time with the exterior supply, the system will make corresponding adjustments to the native time in BIOS. Linux (Ubuntu, in my case) thinks that point in BIOS is laid out in UTC format and provides further time zone offset. This is the rationale why time will get flawed when switching from Linux to Windows and vice versa.
To repair it, it’s best to make Windows use UTC time format in ActualTimeIsUniversal registry parameter.
reg add "HKLMACHINESystemPresentControlSetControlTimeZoneInformation" /v ActualTimeIsUniversal /t REG_DWORD /d 1 /f
reg add HKLMSYSTEMCurrentControlSetControlTimeZoneInformation /v ActualTimeIsUniversal /t REG_QWORD /d 1
Also, disable time synchronization with the Internet in Windows, since at every time replace Windows will reset UTC time to native.
sc config w32time begin= disabled
Restart your Windows.
Or you can also make Linux use native time. In Ubuntu 15.04 or increased, you are able to do it utilizing this command:
timedatectl set-local-rtc 1
HPE Servers with Windows Server: Offset within the System Time After Restart
One of my distant clients got here throughout an attention-grabbing drawback after a time zone change on HPE DL/ML Gen9 servers operating Windows Server 2008 R2 / 2012 R2. As it turned out, when altering a system time or a time zone on HP ProLiant Gen9 servers (and on one in all HP ProLiant DL580 Gen8 servers), system time was not saved and was reset to the earlier one after the restart. The drawback occurred on the servers, on which Windows Server booted within the Legacy mode (with native UEFI boot, there weren’t any time change issues).
The following occasion appeared within the system log:
The system time has modified to 2019-01-29T12:12:28.500000000Z from 2019-01-29T13:12:27.923115700Z.
Change Reason: System time synchronized with the clock.
As an answer of this drawback, HP suggests to replace ROM model to not less than 1.5. This is the model of ROM-Based Setup Utility (RBSU) that has no time reset bug.
Or as a workaround resolution, you’ll be able to set that BIOS supplies Windows the UTC system time (as an alternative of the native time). To do it, as now we have already instructed above, it’s essential to create a parameter with the identify ActualTimeIsUniversal and the worth 1 within the registry key HKLMSYSTEMCurrentControlSetControlTimeZoneInformation.