Power cuts are brutal on Windows PCs. One second everything's fine, the next the power's gone mid-write and your file system is in a state. If your PC is acting weird after a power outage, whether that's sluggish performance, random crashes, a boot loop, or a black screen that goes nowhere, this guide covers every fix in order from the quick stuff to the nuclear option.

TL;DR

PC acting weird after power outage? Start by power cycling the machine and running chkdsk C: /f /r from an elevated Command Prompt. Follow that with sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth. If the PC won't boot at all, use Windows Recovery Environment to run Startup Repair or rebuild the boot config with bootrec commands. Hardware damage is possible if nothing software-side fixes it.

⏱️ 13 min read ✅ High success rate for software issues 📅 Updated July 2026

Key Takeaways

PC acting weird after power outage is almost always caused by file system or system file corruption, both of which are fixable with built-in Windows tools.
Run CHKDSK first, then SFC, then DISM. That order matters.
Boot failures need bootrec commands from Windows Recovery Environment.
If software fixes don't work after a clean install, the PSU or storage drive may be physically damaged.
A UPS (battery backup) is the single best way to prevent this happening again.

At a Glance

Difficulty: Medium
Time Required: 15 to 45 mins
Success Rate: High for software-based issues

What Causes a PC to Act Weird After a Power Outage?

The core problem is timing. Your PC is constantly reading and writing data to the disk. When the power cuts out mid-operation, those writes don't complete cleanly. The file system ends up in what's called a 'dirty' state, meaning it thinks files are still open or partially written. Windows marks the volume as needing a check, and on next boot, things can go sideways fast.

The most common cause is file system corruption. NTFS (the file system Windows uses) is journaled, which means it keeps a log of changes to help recover from exactly this kind of thing. But if the outage is bad enough, or the disk was under heavy write load, the journal itself can get corrupted. That's when you start seeing sluggish performance, missing files, or apps that crash on launch.

Beyond the disk, Windows system files can get corrupted too. DLLs, drivers, registry hives, these all live on disk and if a write to any of them was interrupted, you'll get weird behaviour that ranges from a single app refusing to open all the way to Windows itself failing to start. This is what SFC and DISM are designed to catch and fix.

Then there's the boot configuration. The Master Boot Record (MBR) and Boot Configuration Database (BCD) tell your PC how to find and load Windows. If those get hit during the outage, you'll see a boot loop, a 'No bootable device' error, or Windows will just dump you into Automatic Repair every time. That's a different fix to file system corruption and needs the bootrec commands from Recovery Environment.

And finally, hardware damage. Power surges often accompany outages, especially when the power comes back on. That surge can damage the power supply unit, the motherboard, RAM, or the storage drive itself. If you've run every software fix going and the PC is still misbehaving, that's when you start looking at the hardware. According to HowToGeek's guide on CHKDSK, disk-level corruption after power loss is one of the most common scenarios CHKDSK was built to handle.

PC Acting Weird After Power Outage: Quick Fix First

Before running any tools, do the basics. You'd be surprised how often a proper power cycle sorts minor weirdness that a normal restart doesn't.

Power Cycle and Check Your Power Source Easy

Full power cycle
Turn off the PC. If it's a desktop, flip the switch on the back of the PSU to off. Unplug the power cable from the wall entirely. Hold the power button for 10 seconds to drain any residual charge from the capacitors. Wait a couple of minutes.
Bypass the power strip
Plug the PC directly into a known-good wall outlet. Not a power strip, not a UPS that may have taken a hit. Confirm the outlet works by plugging in a phone charger or lamp first.
Boot and observe
Turn the PSU switch back on, then power up the PC. Watch what happens. Does it boot normally? Does Windows offer Automatic Repair? Does it just sit at a black screen? Note exactly what you see, it tells you which fix to go to next.
Let Automatic Repair run if offered
If Windows launches Automatic Repair, let it finish. Don't interrupt it. It can fix a surprising number of boot issues on its own. If it completes and Windows boots, check Device Manager (right-click Start > Device Manager) for any yellow warning icons on devices.

If Windows boots and runs normally after this, you may have got lucky. Still run CHKDSK as a precaution (see below) to make sure there's no underlying disk corruption waiting to cause problems later.

If Automatic Repair loops (runs, fails, tries again, fails again), don't let it keep going. Power off after the second failure and move to the intermediate fixes below.

PC Acting Weird After Power Outage: Intermediate Fixes

These are the fixes that sort the vast majority of post-outage problems. CHKDSK, SFC, and DISM are Microsoft's own tools for exactly this situation. Run them in order. Skipping CHKDSK and going straight to SFC is a mistake a lot of people make, and then they wonder why SFC keeps reporting errors it can't fix.

Run CHKDSK to Fix Disk and File System Errors Medium

Open Command Prompt as administrator
Click Start, type cmd, right-click Command Prompt in the results, and choose Run as administrator. Click Yes on the UAC prompt.
Run the CHKDSK command
Type chkdsk C: /f /r and press Enter. The /f flag fixes file system errors. The /r flag locates bad sectors and attempts to recover readable data. You'll see a message saying the volume is in use and asking to schedule on next restart.
Schedule and restart
Type Y and press Enter, then restart the PC. CHKDSK runs before Windows loads. On a large drive it can take a while (20 to 40 minutes is normal). Don't interrupt it.
Check the result
After Windows boots, open Event Viewer (type eventvwr in Start), go to Windows Logs > Application, and look for a Wininit source entry. It shows the full CHKDSK log including how many bad sectors were found and fixed.

CHKDSK completed with no errors or fixed errors means the file system is clean. Move on to SFC next.

Repair System Files with SFC and DISM Medium

Run SFC
Open Command Prompt as administrator again. Run sfc /scannow. SFC scans every protected Windows system file and replaces corrupted ones from a cached copy. As Microsoft's own documentation explains, this is the recommended first step for corrupted system files. It takes 5 to 15 minutes.
Read the SFC result carefully
You'll get one of three messages: 'Windows Resource Protection did not find any integrity violations' (all good), 'Windows Resource Protection found corrupt files and repaired them' (fixed), or 'Windows Resource Protection found corrupt files but was unable to fix some of them' (run DISM next).
Run DISM if SFC couldn't fix everything
In the same elevated Command Prompt, run DISM /Online /Cleanup-Image /RestoreHealth. DISM repairs the Windows component store that SFC draws from. It downloads replacement files from Windows Update if needed, so make sure you're connected to the internet. This can take 10 to 20 minutes.
Run SFC again after DISM
Once DISM finishes, run sfc /scannow one more time. With the component store repaired, SFC should now be able to fix anything it couldn't before. Restart the PC when done.

If SFC reports all files repaired and the PC is running normally, you're sorted. Give it a day of normal use to confirm stability.

Use System Restore to Roll Back to Before the Outage Easy

Open System Restore
Type restore in the Start menu and select Create a restore point. In System Properties, click the System Restore button.
Choose a pre-outage restore point
Select a restore point dated before the power cut happened. If you're not sure of the exact date, pick the oldest available one that predates your problems. Click Next, confirm, and let Windows restore. The PC will restart automatically.

System Restore doesn't affect personal files, but it will uninstall apps and drivers installed after the restore point date. Worth it if the above tools haven't fully sorted the weirdness.

Advanced Fixes: PC Still Acting Weird After Power Outage

If the PC won't boot at all, or if the intermediate fixes didn't stick, you're dealing with either boot configuration corruption or something more serious. These steps require Windows Recovery Environment or installation media. Don't skip straight here if you haven't tried CHKDSK and SFC first, those fix the majority of cases.

Boot Repair from Windows Recovery Environment Hard

Get into Windows Recovery Environment
If Windows won't boot, interrupt the startup process 2 to 3 times by pressing the power button during the spinning dots. Windows will automatically drop into Recovery Environment after repeated failed boots. Alternatively, boot from a Windows 10 or 11 USB created with the official Media Creation Tool and choose Repair your computer.
Run Startup Repair first
Go to Troubleshoot > Advanced options > Startup Repair. Let it run. It handles a lot of common boot file issues automatically and is worth trying before going manual with bootrec.
Rebuild boot config manually if Startup Repair fails
Go to Troubleshoot > Advanced options > Command Prompt. Run these commands one at a time, pressing Enter after each:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
If bootrec /fixboot returns 'Access is denied', you may need to reassign the boot partition drive letter first using diskpart. That's an edge case but it does come up on some systems.
Restart and test
Exit the command prompt, remove any USB media, and restart. Windows should now boot normally. If it does, run CHKDSK and SFC from within Windows as described above to clean up any remaining file system issues.

Do not run bootrec /rebuildbcd on a dual-boot system without understanding which OS entries you have. It can remove boot entries for Linux or a second Windows installation. Check bootrec /scanos output first to see what's detected.

Repair Install or Clean Install of Windows Hard

Try a repair install first
Create a Windows 10 or 11 USB using the Media Creation Tool. Boot into Windows (if you can), plug in the USB, and run setup.exe from the USB drive. Choose Upgrade this PC now. On the 'What to keep' screen, select Keep personal files and apps. This reinstalls Windows over itself, replacing all system files, while leaving your documents and programmes intact. It took three reboots before this one stuck on a machine I worked on last month, so be patient with it.
Clean install as last resort
If corruption is severe or the repair install won't complete, you need a clean install. Back up everything important to an external drive first. Boot from the Windows USB, choose Install now, and at the drive selection screen delete all existing partitions until you have Unallocated Space. Select the unallocated space and click Next. Windows creates fresh partitions and installs cleanly. This is the most reliable fix for software corruption, full stop.

A clean install wipes everything on the drive. Make sure your data is backed up before you start. There's no undo.

Check for Hardware Damage if Nothing Else Works Hard

Test the PSU
Power surges are hard on PSUs. If you have access to a known-good PSU of the same or higher wattage, swap it in and see if the instability goes away. A dodgy PSU can cause crashes, random reboots, and all sorts of weird behaviour that looks like software corruption but isn't.
Run storage diagnostics
Download your drive manufacturer's diagnostic tool. For Samsung SSDs, that's Samsung Magician. For Seagate, it's SeaTools. For WD, it's Western Digital Dashboard. CrystalDiskInfo is a good free option if you're not sure of the brand. Run the extended test. Any reallocated sectors or uncorrectable errors on an SSD mean the drive is failing and needs replacing.
Check RAM
Run Windows Memory Diagnostic (type mdsched in Start) or boot from a Memtest86 USB for a more thorough test. Faulty RAM after a surge can cause random crashes and blue screens that mimic software corruption perfectly.

If you're seeing hardware failures after a power surge, check whether your home or business insurance covers electrical damage to electronics. Some policies do.

Preventing Your PC from Acting Weird After a Power Outage

The single most effective thing you can do is get a UPS (Uninterruptible Power Supply). Not a surge protector, an actual battery backup. A UPS gives you 5 to 20 minutes of power after the mains cuts out, enough time for Windows to shut down cleanly and for all pending disk writes to complete. Brands like APC and CyberPower make decent ones for home and office use starting around £60 to £80. For a desktop PC, a 600VA to 900VA unit is usually plenty.

Surge protectors are better than nothing but they don't help with the actual power cut itself, only the voltage spike. And honestly, a lot of cheap surge protectors provide minimal real-world protection. If you're going to spend money on protection, spend it on a UPS.

Beyond that, keep your backups sorted. Windows File History (Settings > Update and Security > Backup) backs up your personal files automatically to an external drive. OneDrive handles documents and photos in the cloud. Neither helps if the system files get corrupted, but at least your data survives. For a full system image backup, Macrium Reflect Free is solid and well-regarded in the repair community.

Keep Windows updated. Microsoft regularly pushes fixes that improve NTFS resilience and recovery behaviour. An up-to-date system handles unexpected shutdowns better than one that's been ignored for two years. Same goes for your storage drivers and firmware, check your SSD manufacturer's site for firmware updates if you haven't in a while.

And if a storm's rolling in and the power's already been flickering, just shut the PC down properly before it cuts out. Takes 30 seconds. Saves hours of repair work.

PC Acting Weird After Power Outage: Summary

Most cases of a PC acting weird after a power outage come down to file system corruption or damaged system files, both of which CHKDSK, SFC, and DISM handle well. Run them in that order, don't skip steps, and give each tool time to finish. If the PC won't boot, Windows Recovery Environment and the bootrec commands sort the majority of boot configuration problems. A repair install covers the cases where system file damage is too widespread for the scan tools to fix. And if you've done all of that and the machine is still misbehaving, you're looking at hardware, most likely the PSU or the storage drive. At that point it's worth getting hands-on help rather than chasing software fixes that won't stick.

If you're dealing with related issues like Windows refusing to boot entirely or you're seeing repeated blue screens after the outage, those guides cover the specific error codes and fixes in more detail. And if your machine took a surge and you're worried about the drive health specifically, our guide on failing hard drive symptoms walks through exactly what to look for.