Change reason: system time synchronized with the hardware clock.

In this short article, we’ll think about why the device clock display screens incorrect time and day after a shutdvery own, rebegin or resuming from hibernation of a laptop/computer/server. Time is reset each time and also you have to set it manually. We’ll dwell on the most typical case: a rundown BIOS battery and also even more exciting ones involving Windows/Linux dual boot on one computer system, and a firmware bug on HPE ProLiant G9 /G8 servers through Windows Server OS.

You watching: Change reason: system time synchronized with the hardware clock.


System Not Saving Data/Time Due to Weak BIOS/CMOS Battery

The typical answer to the question “Why are the time and also date reset on my computer after reboot?” is the BIOS (CMOS) battery rundown. This battery is responsible for maintaining BIOS/UEFI settings when your computer or lappeak is unplugged, and offers autonomous operations of the built-in hardware clock.

If the battery has run down, when the motherboard is not powered, BIOS cannot keep its settings and also all of them are reset, including existing day and also time. If your computer is quite old, it is extremely most likely that your battery is dead. We strongly recommend to replace it. It is not tough, and also the process doesn’t need any unique engineering skills. In most home and also also enterpclimb gadgets a standard 3V CR2032 battery is supplied in BIOS.

*

If the battery replacement hasn’t assisted, examine the state of the jumper provided to reset BIOS settings (The jumper is situated cshed to the battery bay and also is noted as CMOS / CLEAR / RESET). Somebody may have actually left it in the RESET position. Thus, each time once your motherboard is powered, BIOS settings are reset. Move the jumper to its normal position.

The next option is to upday BIOS firmware of your motherboard. See how to do it on the website of your hardware merchant. Newer firmware regularly has different bugs resolved.

Windows: Set Clock Synchronization via time.home windows.com

If your date/time settings in Windows are constantly changing, initially of all you must check the present time zone settings and the parameters of time synchronization via the outside time server. In Windows 10, you can see the current time settings in the Control Panel -> Clock and also Region -> Date and Time. In this example, you have the right to see, that the time zone UTC + 01 is mentioned, and also Daylight Saving Time is enabled.

*


Tip. You deserve to set your time zone in Windows from the command prompt making use of tzutil tool or PowerCovering.

If your computer is not joined to the ADVERTISEMENT doprimary, check its time synchronization settings through the outside time source (NTP time server). To execute it, click Web Time tab and also make certain that the automatic synchronization with time.windows.com server is collection.

*

Troubleshooting time synchronization for ADVERTISEMENT domain-joined computers

If your computer system is component of an Active Directory domain, you have to understand also the architecture of time synchronization in the ADVERTISEMENT domain.

The complying with time synchronization scheme is used in the Active Directory domain:

The root domain controller in the ADVERTISEMENT woodland, to which the FSMO duty of the PDC emulator belongs, is a time resource for all various other DCs of this domain;Other DCs synchronize time via PDC;Ordinary domajor members (servers and workstations) synchronize time via the nearest obtainable domajor controller according to the ADVERTISEMENT topology.

Root PDC can synchronize its time through both an exterior resource and also via itself (by default).

You can discover a domajor controller through the PDC role through the command:

netdom /query fsmo

To connumber time synchronization through an outside NTP server on the PDC, the adhering to regulates are offered.

See more: Systems Deployment : Windows Cannot Access The Installation Sources

Connumber exterior time sources:

w32tm /config /manualpeerlist:"0.nl.pool.ntp.org,0x1 1.nl.pool.ntp.org,0x1 2.nl.pool.ntp.org,0x1 3.nl.pool.ntp.org,0x1"

Make this DC a trustworthy time resource for the clients:

w32tm /config /reliable:yes

Restart w32 time server to synchronize DC time with nl.pool.ntp.org time servers:

net soptimal w32time && net start w32time

You can see the synchronization source and also status:

w32tm /query /peers

Start synchronization in hands-on mode:

w32tm /resync /rediscover

Windows & Linux Showing Different Times When Dual Booting

We need to individually think about the instances when two procedure systems (Windows & Linux) are set up on a computer system in Dual Boot configuration. You have the right to come across the trouble that after booting to an additional device (booting to Linux after Windows) the moment is several hrs ahead or late of the actual time.

Windows and Linux occupational via BIOS time in different ways. They are making use of 2 different time formats: UTC and also localtime.

GNU/Linux operation units (including Mac OS X) assume the moment in BIOS is in UTC format (GMT). Accordingly when booting, Linux converts the UTC time by adding (or distracting) the counter of the current time zone selected by the user. It means that in order to get the regional time for Athens time zone UTC+2, Linux will certainly add 2 hrs.

Windows thinks that time in BIOS is maintained in the localtime format, and if you have actually stated a brand-new time zone or synchronized time via the external source, the system will make matching transforms to the neighborhood time in BIOS. Linux (Ubuntu, in my case) thinks that time in BIOS is specified in UTC format and adds extra time zone balance out. This is the factor why time gets wrong as soon as switching from Linux to Windows and vice versa.

To solve it, you should make Windows usage UTC time format in RealTimeIsUniversal registry parameter.

reg include "HKLMACHINESystemCurrentControlSetControlTimeZoneInformation" /v RealTimeIsUniversal /t REG_DWORD /d 1 /f

*


Tip. In 64-little Windows versions, you have to produce QWORD-form parameter rather of DWORD ones:

reg include HKLMSYSTEMCurrentControlSetControlTimeZoneInformation /v RealTimeIsUniversal /t REG_QWORD /d 1


Also, disable time synchronization with the Net in Windows, given that at each time upday Windows will reset UTC time to local.

sc config w32time start= disabled

Restart your Windows.

Or you can make Linux use local time. In Ubuntu 15.04 or better, you deserve to use the timedatectl tool:

timedatectl set-local-rtc 1

*

HPE Servers through Windows Server: Offset in the System Time After Restart

One of my remote customers came throughout an amazing difficulty after a time zone adjust on HPE DL/ML Gen9 servers running Windows Server 2008 R2 / 2012 R2. As it turned out, as soon as transforming a mechanism time or a time zone on HP ProLiant Gen9 servers (and also on one of HP ProLiant DL580 Gen8 servers), system time was not conserved and was reset to the previous one after the rebegin. The problem arisen on the servers, on which Windows Server booted in the Legacy mode (via indigenous UEFI boot, tbelow weren’t any type of time readjust problems).

The following event appeared in the device log:The mechanism time has readjusted to ‎2019‎-‎01‎-‎29T12:12:28.500000000Z from ‎2019-‎01‎-‎29T13:12:27.923115700Z.Change Reason: System time synchronized through the hardware clock.

As a solution of this problem, HP argues to update ROM variation to at leastern 1.5. This is the variation of ROM-Based Setup Utility (RBSU) that has no time reset bug.

See more: Nslookup Pulls Comcast Dns 2001:558:Feed::1, 2001:558:Feed::1

Or as a workapproximately solution, you can collection that BIOS provides Windows the UTC device time (instead of the local time). To carry out it, as we have currently told over, you need to create a parameter via the name RealTimeIsUniversal and the value 1 in the registry key HKLMSYSTEMCurrentControlSetControlTimeZoneInformation.