● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
A Windows laptop on a dark desk showing a failed update screen with a spinning loading icon and blue error overlay
Fix It Yourself · Troubleshooting

Computer shuts off during a Windows update? Here's what to do

Updated 6 November 202614 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

In more than twenty years of remote support, the pattern tends to be the same. A computer shuts off during a Windows update, the owner panics, forces a restart, and then either gets stuck in a loop or lands on a black screen. The fix is usually not dramatic, but getting the sequence right matters. Do the wrong thing first and you can turn a minor glitch into a proper data recovery job.

What Actually Causes a Computer to Shut Off During a Windows Update?

First, check whether it really shut off. A black screen alone doesn't prove it has. If the screen says "Your PC screen will turn off for a brief period during the update", or that a firmware or system update is in progress, don't turn the PC off: a firmware update can reset the display before Windows starts. If its fans or power light are still on, leave it alone rather than force it off.

When it genuinely switched off, the cause is usually one of these.

Power. A laptop battery that ran flat, a charger that came loose, a power cut, or a desktop power supply unit that can't cope when the processor works hard during the install.

Heat. Updates keep the processor busy for a long time. A PC with clogged vents or a failing fan can overheat and switch itself off to protect the hardware.

A crash. A driver or firmware problem can crash Windows partway through the update, which looks like a shutdown or a sudden restart.

A damaged update or system files. A bad download in the update cache, or system files that were already damaged, can make the same update fail again and again at the same point.

Event Viewer can give you useful clues, though it can't prove the cause on its own. Press Windows key + X, open Event Viewer and go to Windows Logs > System. Look around the time it went off.

  • Kernel-Power, Event ID 41 means Windows restarted without shutting down cleanly. Click it and look at BugcheckCode under Details. A non-zero number means Windows recorded a stop error (a blue screen), so look for a bugcheck event or a dump file. A value of 0 can mean lost power, a hang, a forced shutdown or a crash whose code wasn't written to disk.
  • Event 6008 records that the previous shutdown was unexpected, with its time.
  • Event 1074 means something asked for the restart, and names the program, such as Windows Update. If you see that and no 41, the PC restarted on purpose.
  • WHEA-Logger errors point to a hardware problem, such as the processor, memory or drive.
Quick routeStart here

Computer Shuts Off During Windows Update: Quick Fix

If it switched off once, give Windows a clean start and the chance to roll the update back.

1

Force Clean Shutdown and Let Windows Roll Back Easy

  1. Make sure it's really off
    If the screen is black but fans or lights are on, wait. If it's completely unresponsive and has shown no signs of progress, a hard shutdown is a last resort. It can corrupt files or Windows, so hold the power button only if you need to get to the recovery options.
  2. Plug in and disconnect extras
    Connect a laptop's charger. Unplug USB drives, docks, card readers and printers.
  3. Start it and leave it
    Press the power button once. If you see "Undoing changes made to your computer" or "Working on updates", leave it alone until it's finished, even if it takes a long time.
  4. Try the update again, plugged in
    Once you're at the desktop, open Settings > Windows Update (Settings > Update & Security on Windows 10) and check for updates with the laptop on its charger. Windows 10 Home, Pro, Enterprise and Education reached end of support on 14 October 2025. Eligible PCs can still receive security updates through Extended Security Updates if they're enrolled. LTSC editions have their own support dates.
If Windows starts and the update installs on the second try, keep an eye out for another unexpected shutdown. If there's another one, stop updating and work through the checks below.
Intermediate routeKeep going if needed

More Computer Shuts Off During Windows Update Solutions

If it happens again, deal with whatever made it switch off before you try the update a third time.

2

Check Power Settings and the Battery Easy

  1. Open Power Options
    Press Windows key + R, type powercfg.cpl and press Enter.
  2. Reset the plan
    Click Change plan settings next to your plan, then Restore default settings for this plan. This resets custom power settings. It can help if the PC is going to sleep, but it won't diagnose a sudden power loss or crash.
  3. Restart instead
    On Windows 10, Fast Startup can delay some updates after you choose Shut down. It doesn't come into it when you choose Restart, so restart the PC before trying the update again. Fast Startup won't be why a PC genuinely switched itself off, though.
  4. Check the battery (laptops)
    Open Command Prompt as administrator and run powercfg /batteryreport. Open the battery-report.html file it names. If Full Charge Capacity is far below Design Capacity, the battery may be worn, but the report doesn't prove why the laptop switched off. Compare it with the shutdown events and test the charger too.
If the next update goes through, keep the laptop plugged in for updates, and replace a worn battery.
3

Run the Windows Update Troubleshooter Easy

  1. Windows 11
    Go to Settings > System > Troubleshoot > Other troubleshooters and run Windows Update. On current Windows 11 it opens in the Get Help app.
  2. Windows 10
    Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update.
  3. Apply its fixes and restart
    Let it finish, apply what it suggests, restart and try the update again.
Advanced routeChange one thing at a time

Advanced Computer Shuts Off During Windows Update Fixes

Go to fix 6 if Windows won't start at all. If it starts, copy your files somewhere safe and begin with the update cache in fix 4. You only need any of this if the PC keeps switching off at the same point, or won't start properly afterwards.

4

Clear the Windows Update Cache Medium

  1. Open an admin Command Prompt
    Click Start, type cmd, right-click Command Prompt and choose Run as administrator.
  2. Stop the update services
    Run net stop wuauserv, net stop bits and net stop cryptsvc, one at a time.
  3. Rename the cache folders
    Run ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak and ren %systemroot%\System32\catroot2 catroot2.bak. The folders are renamed rather than deleted. Windows recreates them when the services start, then downloads a fresh copy of the update.
  4. Start the services again
    Run net start cryptsvc, net start bits and net start wuauserv, restart the PC and check for updates.
If the update installs this time, clearing the cache has ruled out one possible cause.
5

Repair System Files with SFC and DISM Medium

  1. Repair the component store
    In an admin Command Prompt, run DISM /Online /Cleanup-Image /RestoreHealth. It checks the store Windows uses to repair itself and fixes it from Windows Update, so stay online.
  2. Then run SFC
    Run sfc /scannow. "Did not find any integrity violations" means the files are fine. "Successfully repaired them" means it fixed something. "Unable to fix some of them" means the damage goes deeper, so try fix 8. Microsoft's SFC documentation explains each message.
  3. If DISM fails to download
    Error 0x800f081f means Windows couldn't find a repair source. Check the PC is online on a working ethernet cable or Wi-Fi connection and try again, or use fix 8, which reinstalls Windows from fresh files.
6

Boot into WinRE to Uninstall or Roll Back the Update Advanced

  1. Open the recovery menu
    Only do this if Windows can't start and you have no recovery media. Turn it on, then hold the power button to switch it off when the Windows logo appears. Repeat once, then turn it on a third time. This is an unclean shutdown and can lose unsaved data. Windows should show the Automatic Repair screen, where you can choose Advanced options.
  2. Have your BitLocker key ready
    If the drive is encrypted, some options ask for the recovery key. If you backed it up to your Microsoft account, find it at aka.ms/myrecoverykey on another device. A work or school PC may keep it with that organisation instead.
  3. Uninstall the update
    Choose Troubleshoot > Advanced options > Uninstall Updates. Try Uninstall latest quality update first, then the latest feature update. Microsoft's WinRE technical reference explains how the recovery environment works.
  4. Or use System Restore
    In Advanced options, choose System Restore and a point from before the update. Keep a laptop on AC power and don't switch it off while it runs. Your files stay, but apps and drivers installed after that date go.
7

Battery Driver Reset (Laptops Only) Easy

  1. Remove the battery driver
    Don't do this on a Surface Pro X. Microsoft says its battery driver can only be restored with a full system reset if you remove it. On another laptop, create a restore point first. In Device Manager, expand Batteries. If Microsoft ACPI-Compliant Control Method Battery is listed, right-click it and choose Uninstall device. If Windows offers to delete the driver package, leave that box unticked.
  2. Restart
    Restart with the charger connected. Windows reinstalls the driver on its own.
  3. Watch the charge reading
    If the battery percentage jumps around or the laptop switches off at a reading well above zero, the battery's reporting is wrong or the battery is worn. Compare with the battery report from fix 2.
8

Check Heat, Then Reinstall Windows in Place Advanced

  1. Watch temperatures under load
    Install HWiNFO, open its sensors window and use the PC as you normally would, then run something demanding. Check your processor's maximum temperature on its maker's site. If it sits at that limit and the PC switches off, stop the test and get the cooling cleaned or checked before another update.
  2. Reinstall Windows over itself
    On Windows 11, if Fix problems using Windows Update is available, go to Settings > System > Recovery and select Reinstall now. Keep the PC connected to power and the internet until it finishes. On Windows 10, create Microsoft installation media, open setup.exe from it while signed in, choose Change what to keep, then Keep personal files and apps. Back up first either way.
9

Read the Crash Dump Advanced

  1. Find the dump
    If event 41 showed a BugcheckCode other than 0, look for a .dmp file from that time in C:\Windows\Minidump or C:\Windows\MEMORY.DMP. The location depends on the dump type Windows is set to create.
  2. Open it in WinDbg
    Install WinDbg from the Microsoft Store, open the file with File > Open Crash Dump, then type !analyze -v in the command window.
  3. Read the culprit
    MODULE_NAME and IMAGE_NAME are clues, not proof. Check the stop code and stack too, and only change a driver when the dump repeatedly points to a non-Microsoft driver.
When to stop. Stop updating and get the hardware checked if the PC also switches off when you're not updating, or Event Viewer shows WHEA-Logger errors. The same goes if the temperature hits its limit just before it shuts off, or a desktop goes off as soon as anything demanding runs. Those all point to the power supply, the cooling or another part, and each update you try in the meantime risks leaving Windows half-installed. A desktop that only passes once a known-good power supply is fitted needs a new one, and our guide to the best power supplies covers replacements.

For IT Pros: Computer Shuts Off During Windows Update

On managed PCs, check whether the "shutdown" was a restart your policy asked for.

  1. Read who restarted it.
    Event 1074 in the System log names the process and reason for a planned restart. A 1074 from Update Orchestrator shows Windows Update initiated a planned restart. Check the reason and update policy before deciding it was a deadline.
  2. Check the deadline settings.
    In Intune, use the update ring's deadline and grace period settings. In Group Policy, Windows 11 22H2 and later use Specify deadline for automatic updates and restarts for quality update and Specify deadline for automatic updates and restarts for feature update. Windows 10 22H2 uses Specify deadlines for automatic updates and restarts. Set sensible deadlines, grace periods and active hours. Once the effective deadline has passed, including any grace period that applies, Windows can restart during active hours.
  3. Confirm what applied.
    Run gpresult /h gp.html on the affected PC to see which update policies reached it and from which GPO. On ARM64 Windows, use %windir%\SysWOW64\gpresult.exe /h gp.html instead.

Preventing Computer Shuts Off During Windows Update

Most of these are quick one-time changes that make a real difference. Priority order matters here, so start from the top.

  1. Keep laptops on AC power during updates. A worn battery can die mid-update while the machine is working hard, whatever the percentage says. Plug in before you start.
  2. Don't defer updates for months. Monthly updates are cumulative, so Windows installs the latest suitable update rather than every missed monthly patch. Install them reasonably promptly.
  3. Run SFC and DISM when something's wrong. They're repair tools, so use them when Windows reports damaged files or an update keeps failing.
  4. Create a restore point before major feature updates. Windows sometimes does this automatically, but only if System Protection is on, so check it's on and that the restore point appears.
  5. Keep drivers current, and be careful with BIOS updates. Check your laptop or motherboard maker's website for your model. Only update the BIOS when the maker says your model needs it. Before you do, back up your files and have your BitLocker recovery key ready. Then follow the maker's exact instructions, suspend BitLocker if they tell you to, keep a laptop on its charger and don't interrupt the update.
  6. Check Event Viewer if you notice any unexpected shutdowns. Kernel-Power Event ID 41 confirms Windows didn't shut down cleanly. Check BugcheckCode and the nearby events before deciding whether it was power, a crash or a forced shutdown.

Computer Shuts Off During Windows Update: Summary

When a computer shuts off during a Windows update, give it a clean start and let Windows roll the update back. Then find out why it went off. Kernel-Power 41 confirms the shutdown wasn't clean, and a non-zero BugcheckCode means Windows recorded a stop error. On a laptop, a battery report can show reduced capacity, though it won't tell you on its own what caused the shutdown. If the same update keeps failing, clear the update cache and repair system files with DISM and SFC.

A PC that won't start can still have the update removed, or be taken back to an earlier restore point, from WinRE. If it also switches off outside updates, stop retrying and have the hardware checked before the next one. And if it only behaves with a known-good power supply fitted, the original power supply needs replacing.

Frequently Asked Questions

There's no fixed time. It depends on the update, your connection and the PC itself. Watch for disk activity or on-screen progress, and if it sits at the same point long enough that you think it's stopped, use the recovery steps above rather than forcing it off again and again.

Windows usually rolls back incomplete updates automatically, but there is a real risk of file corruption. Keep regular backups and only force a shutdown if the system is completely unresponsive and you need to reach the recovery options.

Fast Startup uses hibernation rather than a full shutdown. Microsoft documents it as a Windows 10 issue that can delay some updates after you choose Shut down, not Restart. It doesn't explain a PC that has genuinely switched itself off.

It means Windows restarted without shutting down cleanly. You'll find it under Windows Logs > System in Event Viewer. Check BugcheckCode in its details: a non-zero number means Windows recorded a stop error. A value of 0 can mean lost power, a hang, a forced shutdown or a crash whose code was not written to disk.

Yes, both are official Microsoft tools built into Windows. Run them from an elevated Command Prompt (right-click, Run as administrator). SFC repairs individual system files while DISM repairs the underlying Windows component store. Let them finish completely before rebooting.