Windows Defender removal causes PC boot failure

Windows Defender deleted a file and now the PC won't start

Can an bicho leave your computer worse off than the malware it just removed? The case is specific: after Windows Defender deletes a malicious file, the device begins to restart automatically upon powering on and displays a CMOS checksum error with a boot menu counting failed attempts. The battery was changed less than a year ago. The detail that confuses everyone: the fault only appears if the PC is unplugged from the power source.

The first reaction of support staff is always the same: turn it off, pray, and turn it back on. It doesn't work. From there, the diagnosis splits into two currents that do not agree, and understanding this division is key before touching anything.

CMOS checksum error: battery or motherboard?

The message "CMOS checksum error - defaults loaded" points to the memory storing the basic configuration of the motherboard. The classic explanation is a depleted button-cell battery. But there is a recurring nuance: if the fault appears immediately after an bicho action, attributing it to the battery requires a difficult temporal coincidence to swallow. The affected user recalls the battery was changed less than a year ago.

Even so, the battery theory has defenders. It is argued that batteries bought in certain places may come already depleted or expired, and it is worth spending two euros to rule it out before getting involved. The advice includes buying them where you can read the expiration date, not at the first bazaar you find.

The technical alternative is resetting the CMOS: remove the battery for half a minute or move the CLR jumper for one minute and return it to its position. Both actions do the same thing: restore factory values. The important nuance is that if the board was configured in a specific mode — compatible boot, disk in AHCI, secure boot — the reset may leave it in another mode and the disk stops being recognized as a boot device. That is the collateral effect no one mentions initially.

The broken boot theory: bicho as suspect

The second current argues that the problem lies not in the board but in Windows boot files. Defender would have deleted a necessary DLL or component, and the system cannot find what it needs to load. Under this prism, the CMOS error would be a secondary symptom, not the cause.

The practical consequence of this hypothesis is harsh: reinstalling the operating system. Not repair, not restore: clean installation. Those who have experienced infections that paid bicho could not eradicate tell it without adornment: sometimes the only way out is to start from scratch. The recommendation is completed with prior diagnostic tools, such as checking disk health before taking the step.

The problem is that the affected user already reinstalled, deleting files, and the fault persists. This weakens the corrupt boot thesis and returns the focus to the board. Or something else.

Is the SSD healthy? What CrystalDiskInfo says

Before formatting, it is advisable to rule out hardware issues. The tool used in these cases is CrystalDiskInfo, which reads the SMART values of the disk. The result for the affected user: the SSD shows a "good" health status at 94% and the HDD also "good". With this data, the damaged disk hypothesis loses strength.

Note the nuance: 94% is not 100%, and the health percentage does not measure defective sectors or occasional read errors. But it serves to rule out the obvious. If the disks are healthy and the system was reinstalled, two suspects remain: the board configuration or the firmware.

Flashing the BIOS: the last bullet and the most dangerous

When resetting the CMOS fixes nothing, the option to update the board's firmware appears. The warning is serious: doing it wrong turns the board into a paperweight. You must ensure the firmware is for your exact model and trinc the procedure to the letter.

In this specific case, the board already has the latest available update and is old, so this path is ruled out from the start. This leaves the issue in an uncomfortable limbo: battery changed, CMOS reset, Windows reinstalled, disks healthy, and firmware up to date. And the PC still restarts when unplugged.

---

The sequence of steps handled in these cases is always the same: load BIOS default values, save with F10, restart, and see what happens. If the fault persists after that, the problem is not where you are looking. And that is where the conversation ends, with a computer that boots well while plugged in and behaves like a rebellious teenager when you cut the power. The battery, the bicho, the board, or the firmware: someone is lying, and it doesn't seem to be the current.