Have you turned on your laptop and the date on the screen is 2015, or is the time off by several hours? This problem is familiar to many users, but its causes are not always obvious. A time glitch can be either a harmless system glitch or a symptom of a serious hardware problem. In this article we will look at all possible reasonswhy the date and time on a laptop is lost - due to a dead battery CMOS before synchronization errors with servers NTP, and also give step by step instructions for diagnostics and repair for Windows 10/11 And Linux.

The peculiarity of the problem is that it can manifest itself in different ways: for some, the time is lost after each shutdown, for others - only after removing the battery, and for others - randomly every few days. We'll look at each scenario individually so you can pinpoint the source of the problem. It is important to understand that Timing glitches are often related to the laptop's non-volatile memory, and ignoring the problem can result in lost BIOS settings or even the system being unable to boot.

1. The CMOS battery is dead - the main reason for the time failure

In 90% of cases, the culprit for an erroneous date and time is battery CMOS (or RTC - Real-Time Clock). This is a small round battery on the motherboard that powers the clock chip even when the laptop is turned off. When the battery is low, the memory CMOS is reset and the system loses all settings, including the current time.

How can you tell if the problem is with the battery?

  • ⏰ Time is lost every time after shutdown laptop (even if it was connected to the network).
  • ⚙️ B BIOS/UEFI other settings are reset (boot priority, fan operating modes).
  • ⚠️ When turned on, a message appears CMOS checksum error or Time and date not set.
  • 🔋 Laptop older than 3–5 years (battery life CR2032 - about 5 years).

To check the battery status, follow these steps:

  1. Turn off your laptop and unplug the power cable.
  2. Remove the back cover (on some models Lenovo, HP or Dell The battery is accessible without complete disassembly).
  3. Find a coin cell battery CR2032 (less often - CR2026) and measure its voltage with a multimeter. Norm - 3 V. If the reading is below 2.5 V, the battery needs to be replaced.

2. BIOS/UEFI settings: why the system does not save time

Sometimes the problem lies not in the hardware, but in incorrect settings BIOS/UEFI. For example, if the module is disabled in the firmware RTC (Real-Time Clock) or the energy saving settings have been reset. Also some versions BIOS (especially on older laptops Acer or Asus) have bugs that cause the time to go wrong even with a working battery.

What to check in BIOS/UEFI:

  1. When booting the laptop, press F2, Del or Esc (depending on model) to enter settings.
  2. Find a section Main or System Time and check if the time matches the real one. If not, install the correct one.
  3. Go to Advanced → Power Management and make sure the option ACPI Auto Configuration or RTC Wakeup enabled (Enabled).
  4. Reset settings to factory defaults (Load Default Settings) and save changes (F10).

If after reset BIOS The time is wrong again, update the firmware. To do this:

  • 🔍 Download the latest version BIOS from the manufacturer's official website (indicate the exact laptop model!).
  • 💾 Create a bootable USB flash drive with firmware (instructions are usually included in the archive).
  • ⚠️ Don't interrupt the update process - this can lead to failure of the motherboard.
What to do if the laptop does not turn on after updating the BIOS?

If after the firmware BIOS the screen remains black, try:

1. Disconnect the laptop from the network, remove the battery and hold the power button for 30 seconds (static charge release).

2. If there is a backup battery CMOS - replace it.

3. On some models Lenovo or HP can be restored BIOS through combination Win + B (hold for 10 seconds with power off).

If all else fails, contact the service center for flashing. BIOS programmer.

3. Problems with time synchronization in Windows

If the date and time are wrong only on Windows, but in BIOS are displayed correctly, the problem lies in the synchronization settings. The operating system may not communicate correctly with time servers (NTP), especially if:

  • 🌐 A VPN or proxy is used that blocks access to time.windows.com.
  • 🔒Antivirus or firewall is blocking the time service Windows Time (w32tm).
  • ⚡ The laptop often goes into sleep/hibernation mode, and the time service does not have time to synchronize.

How to set up time synchronization in Windows 10/11:

  1. Open Settings → Time and language → Date and time.
  2. Enable options Set time automatically And Automatically set time zone.
  3. Click Sync now. If an error appears, run (Win + R → cmd):
w32tm /register

w32tm /config /syncfromflags:manual /manualpeerlist:"time.windows.com,0x8 pool.ntp.org,0x8"


w32tm /config /reliable:yes


w32tm /resync


net stop w32time & net start w32time

If the problem persists, try using alternative time servers (for example, pool.ntp.org or ru.pool.ntp.org). To do this:

  • Open Control Panel → Administrative Tools → Services.
  • Find a service Windows Time, stop it and set the startup type Automatic (delayed start).
  • In the service parameters, specify the new server in the field NtpServer.
📊 How often do you lose time on your laptop?
  • Every time after switching off
  • Once every few days
  • Only after removing the battery
  • Randomly, without patterns

4. Time glitches in Linux: features and solutions

In distributions Linux (Ubuntu, Mint, Fedora, etc.) the problem over time is often related to a conflict between hardware clock (RTC) and system clock. By default, Linux assumes that the hardware clock stores time in the format UTC, whereas Windows uses local time. If the laptop is used with both OSes (dual boot), this leads to constant crashes.

How to check and fix:

  1. Open a terminal and run the command to check the current time:
timedatectl status

Pay attention to the lines:

  • System clock synchronized - if no, synchronization is disabled.
  • RTC in local TZ - if yes, watch RTC are set to local time (this may cause conflicts).

Linux solutions:

  • 🔄 If you use dual boot with Windows, disable local time RTC:
sudo timedatectl set-local-rtc 0
  • 🌍 Set the correct time zone:
sudo timedatectl set-timezone Europe/Moscow
  • ⏱️Forcibly synchronize time with the server:
sudo systemctl restart systemd-timesyncd

If the problem persists, check the service systemd-timesyncd:

sudo systemctl status systemd-timesyncd

If the service is inactive, enable it:

sudo systemctl enable --now systemd-timesyncd

5. Viruses and malware: the hidden threat

Rarely, there are viruses that deliberately disrupt the system time in order to:

  • 🕵️ Bypass software license checks (for example, Adobe or Microsoft Office).
  • 🔑 Disrupt security certificates (for example, for attacks like Man-in-the-Middle).
  • 📅 Hide traces of your activity (changing file timestamps).

How to check your system for viruses:

  1. Download utilities Kaspersky Virus Removal Tool or Dr.Web CureIt! and scan the system in safe mode.
  2. Check startup (msconfig on Windows or systemctl --user list-unit-files on Linux) for suspicious processes.
  3. Remove unfamiliar tasks from Task Scheduler (taskschd.msc).

Pay special attention to:

  • 📁 Files with the extension .exe or .bat in folders Temp, AppData.
  • 🔗 Suspicious registry entries along the way HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run.
  • 🕒 Programs that forcibly change time (for example, Cheat Engine or pirated activators).
💡

If the antivirus finds threats like Trojan.Win32.Agent or Backdoor, after treatment, be sure to check the integrity of system files with the command sfc /scannow (Windows) or debsums (Linux).

6. Hardware faults: when it’s not the battery

If replacing the battery CMOS and all software methods did not help, the problem may lie in motherboard malfunction. The most common culprits are:

  • 🔌 Damaged power circuit RTC (for example, after liquid ingress or power surge).
  • 💾 Faulty chip CMOS or Super I/O (responsible for low-level functions, including the clock).
  • 🔌 Short circuit on the battery contacts (for example, due to oxidation).

How to diagnose a hardware problem:

Symptom Probable Cause Solution
Time is lost even with a new battery CMOS. The microcircuit is faulty RTC or power circuit. Diagnostics at a service center (you need a multimeter and a motherboard diagram).
The laptop does not turn on after replacing the battery. Short circuit or incorrect battery installation (reverse polarity). Check polarity, clean contacts with alcohol.
B BIOS All settings are reset, including boot priority. The chip is damaged CMOS or firmware BIOS. Flashing BIOS or replacing the microcircuit.
The time only goes wrong when running on battery power. The power circuit is faulty RTC from battery. Check the power circuit (the charging controller may be faulty).

If you suspect a hardware problem but have no experience repairing electronics:

⚠️ Attention: Do not attempt to solder or replace chips yourself without proper skills! Errors when working with the motherboard can lead to complete failure of the laptop. Contact the service center indicating the symptoms.

7. External factors: temperature changes, humidity, magnetic fields

Few people know, but work hours RTC external conditions may influence:

  • 🌡️ Extreme temperatures: when overheated or cooled below 0°C, the quartz resonator in the chip RTC may cause an error.
  • 💧 High humidity: leads to oxidation of battery contacts CMOS.
  • 🧲 Strong magnetic fields: If the laptop is placed near powerful speakers or transformers, it may affect the accuracy of the watch.

How to minimize the influence of external factors:

  • 🏠 Store your laptop in a dry place at a temperature 10–35°C.
  • 🔌 Do not leave it near sources of strong electromagnetic fields (microwaves, refrigerators, speakers with magnets).
  • ☀️ Avoid direct sunlight - overheating can speed up battery drain CMOS.

If the laptop was used in unfavorable conditions (for example, in a workshop or outdoors), it is recommended:

  1. Dry it in a warm, dry place for 24 hours.
  2. Clean battery contacts CMOS eraser or alcohol.
  3. Check the accuracy of the time after normalization of conditions.

Check the temperature and humidity in the room|Inspect the laptop for condensation|Make sure that there are no sources of magnetic fields nearby|Test the operation after normal conditions-->

FAQ: Frequently asked questions about time errors on a laptop

Can I use a laptop without a CMOS battery?

Technically yes, but the time will be lost every time you turn it off. In addition, settings may be reset BIOS, which will lead to loading problems. If the battery is completely discharged, some laptops (for example, Dell Latitude or HP EliteBook) may not even turn on.

Why does the time only go wrong when running on battery power?

This is a sign that the power supply is RTC does not receive voltage from the battery. Possible reasons:

  • The charging controller is faulty.
  • The cable connecting the battery to the motherboard is damaged.
  • B BIOS power off RTC battery (on some models Lenovo ThinkPad there is a separate setting).

Solution: Check the battery and power circuit at a service center.

How to check if the RTC chip is good?

It’s difficult to do this yourself, but you can perform an indirect check:

  1. Install a new battery CMOS.
  2. B BIOS set the correct time.
  3. Turn off your laptop and leave it without power for 24 hours.
  4. If after switching on the time is lost, the microcircuit is most likely faulty RTC or power circuit.
Can a virus affect the hardware clock (RTC)?

No, viruses cannot directly change the time in the chip RTC, since it is controlled at the hardware level. However, malware can:

  • Change the system time in the OS (which will be reset after a reboot).
  • Block the time synchronization service.
  • Substitute answers from NTP-servers (in rare cases).

If the problem persists after treating viruses, look for the cause in the hardware.

The time is lost on a laptop running MacOS. What to do?

On MacBook the problem is usually related to:

  • Low battery CMOS (in models up to 2015).
  • Failure in SMC (System Management Controller).
  • Incorrect synchronization settings with Apple servers.

Solutions:

  1. Reset SMC (instructions on the Apple website).
  2. Run in terminal:
sudo sntp -sS time.apple.com

If the problem persists, contact Apple Service.