What happened
The author's home server, an ASUS-based machine more than a decade old, ran Proxmox and had no UPS. That detail comes from his account of his own machine. After a power outage it didn't restart by itself. Powered on by hand, it stopped at a firmware screen waiting for a keypress before Proxmox could load. A headless box in a corner is never going to get that keypress.
Once the machine was running, the BIOS settings were back at defaults. He lost his boot order, XMP memory profile, "Restore on AC Power Loss" setting, VT-d and fan curves. The same thing happened on a second power loss, and that told him the battery was at fault. Replacing it fixed everything.
Why the fault looked random
The key clue was the pattern. His Proxmox host had also been crashing, and he recovered from those crashes with hard resets. None of them wiped a setting. He attributes this to the PSU, which feeds a 5V standby rail to the board as long as it's plugged in and switched on. That keeps the CMOS alive without the coin cell.
General reference material agrees with that mechanism. Wikipedia's page on nonvolatile BIOS memory says on ATX motherboards the PSU supplies 5V standby power to keep CMOS memory energized while the system is off. It adds that swapping the cell with the PSU switched on and plugged in can avoid an unwanted BIOS reset. That's a handy trick, though it depends on the board.
So a crash and a lost setting looked like two unrelated faults. The battery only matters when standby power is also lost, such as in an outage, when the PSU is switched off, or when the cord is pulled.
Symptoms to look for
Other repair guides list similar signs. Home PC Repair, for example, lists a system clock that resets to a default date and BIOS settings such as boot order, XMP/EXPO profiles or fan curves that keep disappearing. It also notes occasional failure to boot after the PC has been unplugged for an extended time, such as after a long power cut. The "CMOS checksum error" at POST is another common one. Treat these third-party guides as general repair advice, not a diagnosis of the XDA server.
Desktop knock-on effects:
- Wrong clock: The author notes that a wrong date can cause HTTPS certificate errors, because browsers check certificates against system time. He says this as a possible consequence. It wasn't something he saw on the server.
- Virtualization off: If a reset turns CPU virtualization off, WSL 2, Docker Desktop, Android emulators and some anti-cheat tools can stop working. Microsoft's WSL documentation says WSL 2 needs the "Virtual Machine Platform" and "Windows Subsystem for Linux" features enabled. Microsoft's troubleshooting guidance also points to BIOS virtualization settings. A CMOS reset won't disable virtualization on every machine, but check it after any reset.
- Unattended boot hangs: Some boards stop and wait for F1 after a reset. That's fatal for a server nobody is watching.
It might not be the battery
The author is upfront that other causes exist. Many modern UEFI boards keep their settings in flash. On those, a dead coin cell may only reset the clock. Settings can also revert after failed memory training, an accidental clear-CMOS jumper bridge, or a failed automatic overclock. He calls these rare but plausible.
His practical test is simply to replace the battery. It's cheap, but it isn't proof. If the settings still vanish afterward, look at the other causes.
How to replace it
These steps come from ASUS's support pages. They cover ASUS boards, so check your own board's manual.
- Power off and unplug. ASUS's clear-CMOS procedure starts by powering off the PC and removing the power cord.
- Find the battery. ASUS says to locate it on the board. Some boards use a coin-cell holder. Others use a wired two-pin battery.
- Remove it. On ASUS's replacement page, a latch secures the cell. You press the latch and the cell pops up. ASUS adds that boards with a rubber plug need it pulled straight up, then refitted afterward.
- Fit the new cell. ASUS lists a CR2032 3V battery for its guidance, and other repair guides say to seat it with the positive (+) side facing up. Confirm the cell type on your own board.
- Reconfigure the BIOS. ASUS's reset flow is to enter setup (often by pressing F1 at the prompt), set the date and time, press F5 for Load Optimized Defaults, then press F10 to save and exit. After that, reapply the settings you need. Check boot order and mode, fan curves, XMP/EXPO, virtualization, and AC-power-restore behavior.
- Test before leaving it alone. Cut the power briefly, then confirm the clock and settings survive. Do this before you trust a headless server again.
A UPS is a mitigation, not a repair
The author says he still needs to buy a UPS. A UPS cuts down the outages that expose a weak battery. It doesn't revive a dead cell or show that a battery is healthy.
Takeaways
- A clock or BIOS reset after a full power loss, with settings intact after ordinary restarts, is a strong clue.
- Wiped settings and a hang at POST can look like a bigger hardware or OS problem, as the author found after flashing BIOS versions and digging through the manual.
- Batteries on boards over a decade old are worth checking. The author's claim that failures are rare on PCs under 5 years old comes with no supporting data, so take it as one builder's experience.
- Always-on machines such as home labs, NAS boxes and Proxmox hosts have the most to lose, because nobody is there to press F1.
A CR2032 costs a few dollars. Most other fixes for these symptoms cost far more time.
References
- A dead CMOS battery made my PC act haunted for a week before I worked out what was wrong XDA · 2026-10-23T11:00:21+00:00
- (Motherboard) How to replace CMOS battery on motherboard when it runs out power ? | Official Support | ASUS USA asus.com
- CMOS Battery Problems: Symptoms and How to Replace It (2026) homepcrepair.co.uk