Windows 10 Suddenly Won’t Boot — Fixed by Replacing the CMOS Battery and Enabling Legacy Mode

by

A Windows 10 PC that had been working normally suddenly stopped booting.

When I entered the BIOS, the first thing I noticed was that the date and time had been reset, and the boot order had also returned to its default settings.

Because the BIOS settings appeared to have been reset, I suspected a CMOS battery issue. I replaced the motherboard battery and restored the date, time, and boot order, but Windows still would not start.

After further checking, I found that the existing Windows 10 installation was using an MBR disk with Legacy boot.

After the BIOS reset, the boot mode had returned to the motherboard’s default UEFI configuration. I changed the boot mode back to Legacy/CSM to match the existing Windows installation, and Windows 10 booted normally again.

Symptoms

The following symptoms were confirmed:

  • Windows 10 had previously been working normally
  • The PC suddenly stopped booting
  • BIOS was still accessible
  • The storage drive was detected in BIOS
  • BIOS date and time had been reset
  • The previous boot order had returned to its defaults
  • Restoring the boot order alone did not start Windows

Because the drive itself was still detected, I first suspected that the motherboard BIOS settings had been reset.

First Suspicion — CMOS Battery

A reset BIOS clock can be a sign that CMOS settings are no longer being retained properly.

On older PCs, a weak CMOS battery can cause symptoms such as:

  • Date and time resetting
  • Boot order resetting
  • BIOS settings returning to defaults
  • Settings being lost after AC power is disconnected

In this case, both the clock and boot settings had been reset, so I suspected the CMOS battery.

I replaced the motherboard battery and then reconfigured the BIOS.

Many desktop motherboards use a CR2032 coin-cell battery, but the actual battery type should be checked before replacement.

Windows Still Would Not Boot After Replacing the Battery

After replacing the battery, I restored:

  • Date and time
  • Storage detection settings
  • Boot order for the Windows drive

However, Windows still did not start.

Since the drive was correctly detected in BIOS, I checked whether another BIOS setting had changed and no longer matched the way Windows had originally been installed.

The Existing Windows 10 Installation Used MBR

The Windows 10 installation in this PC was using an MBR disk and Legacy boot.

Windows systems commonly use configurations such as:

GPT disk
↓
UEFI boot

or:

MBR disk
↓
Legacy BIOS / CSM boot

This PC was using the second configuration:

Windows 10
+
MBR
+
Legacy boot

After the CMOS/BIOS settings were reset, the motherboard returned to a UEFI-oriented default boot configuration.

The existing MBR/Legacy Windows installation therefore could not boot normally.

Changed UEFI Back to Legacy/CSM

I checked the BIOS boot settings and enabled a Legacy or CSM-compatible boot mode.

The exact menu name varies by motherboard manufacturer and BIOS version.

Possible names include:

  • Boot Mode
  • UEFI / Legacy
  • CSM
  • Launch CSM
  • Legacy Support
  • UEFI and Legacy

I changed the boot configuration to match the existing Windows 10 installation.

After saving the BIOS settings and restarting the PC, Windows 10 booted normally.

Why Didn’t Fixing the Boot Order Solve It?

The boot order only determines which storage device the PC attempts to boot from first.

In this case, the problem was not just the drive order.

The BIOS boot method no longer matched the way Windows had been installed.

For example, if the existing system is:

MBR + Legacy

but the BIOS reset leaves the system booting in:

UEFI

the drive may still appear normally in BIOS while Windows itself cannot be started through the same boot path.

Therefore:

SSD detected normally
+
Boot order correct

does not necessarily mean Windows will boot.

The boot mode must also be checked.

GPT/UEFI vs. MBR/Legacy

GPT and UEFI are often mentioned together, as are MBR and Legacy, but they are not the same type of technology.

GPT and MBR are disk partitioning schemes.

UEFI and Legacy BIOS are firmware boot methods.

For Windows installations, these combinations are commonly used:

GPT ↔ UEFI
MBR ↔ Legacy/CSM

This PC used the second combination.

However, it is better not to generalize that:

MBR always means Legacy
GPT always means UEFI

in every possible environment.

The important point is to identify how the existing Windows installation was actually configured and booted.

Result

The troubleshooting process was:

Windows 10 suddenly would not boot
↓
Entered BIOS
↓
Date/time and boot order were reset
↓
Replaced CMOS battery
↓
Restored date/time and boot order
↓
Windows still would not boot
↓
Confirmed existing Windows used MBR
↓
Checked BIOS boot mode
↓
Enabled Legacy/CSM boot
↓
Windows 10 booted normally

The important part of this case was separating the CMOS reset problem from the Windows boot-mode problem.

Replacing the battery alone did not restore Windows booting.

The BIOS boot configuration also had to be restored to match the existing Windows installation.

Important Notes

1. BIOS Menu Names Vary by Motherboard

Legacy, CSM, and UEFI options may have different names and locations depending on the motherboard manufacturer and BIOS version.

Instead of looking for one exact menu name, check the sections related to Boot, CSM, or boot compatibility.

Laptop and OEM PC BIOS menus may also differ significantly.

2. Newer PCs May Not Support Legacy/CSM

Some newer motherboards and OEM PCs support UEFI boot only and do not provide Legacy or CSM options.

If no Legacy/CSM setting exists, that does not necessarily indicate a BIOS problem.

3. Do Not Apply This Directly to Windows 11 Systems

For a normally supported Windows 11 configuration, UEFI boot with a GPT disk is the preferred direction.

If a Windows 11 PC has a boot problem, it is not a good idea to automatically search for Legacy mode or convert the disk to MBR.

This article describes a case where an existing Windows 10 installation was already using MBR + Legacy.

4. Do Not Convert the Disk Immediately

If an MBR Windows installation suddenly stops booting, do not immediately convert the disk to GPT or delete partitions.

If the actual problem is only a changed BIOS boot mode, modifying the disk layout may create additional problems or affect data.

Check first:

  • Whether the drive is detected in BIOS
  • Whether Windows was installed as GPT or MBR
  • Whether the BIOS boot mode changed
  • Whether the boot order is correct

5. A Reset BIOS Does Not Prove the Battery Was the Only Cause

If the date and time are reset on an older PC, the CMOS battery is a reasonable component to suspect.

The motherboard battery was replaced in this case.

However, a single BIOS reset does not prove with certainty that the battery alone caused the reset.

If the BIOS clock or settings continue to reset after battery replacement, additional motherboard or power-related issues should be investigated.

Additional Checks for Similar Cases

If Windows suddenly stops booting and BIOS settings appear to have reset, check:

  1. Is the SSD/HDD detected in BIOS?
  2. Has the BIOS date/time reset?
  3. Has the boot order changed?
  4. What is the CMOS battery condition?
  5. Is the Windows disk GPT or MBR?
  6. Was Windows booting through UEFI or Legacy?
  7. Did Secure Boot or CSM settings change?
  8. Is the BIOS configured for the existing Windows installation?

If the storage device is not detected at all in BIOS, the cause is likely different from the case described here.

Field Notes

Symptom: Windows 10 suddenly stopped booting

Initial finding: BIOS date/time and boot order had been reset

Initial suspicion: Weak CMOS battery and reset BIOS settings

Work 1: Replaced the motherboard CMOS battery and restored date/time and boot order

Additional symptom: Storage drive was detected normally, but Windows still would not boot

Additional finding: Existing Windows 10 installation used MBR with Legacy boot

Work 2: Changed the reset BIOS boot configuration from UEFI back to Legacy/CSM to match the existing Windows installation

Result: Windows 10 booted normally

Possible cause: The BIOS reset likely changed the boot mode so that it no longer matched the existing MBR/Legacy Windows installation

Caution: Newer PCs may not support Legacy/CSM, and the same procedure should not be applied blindly to Windows 11 or GPT/UEFI systems

Not fully confirmed: The original BIOS reset could not be confirmed as being caused only by the CMOS battery