Windows 11 Automatic Repair Loop and "Working on Updates" Stuck: How to Fix Both Without Losing Files

What the Automatic Repair loop and "Working on updates" screens really mean

The Automatic Repair loop is Windows telling you it failed to start twice in a row, launching the Windows Recovery Environment (WinRE), failing to fix itself, and restarting into the same failure. "Working on updates" and "Undoing changes made to your computer" are the same family of problem: an update that could not finish, followed by Windows trying to roll it back. In most cases your files are untouched and the fix is a matter of removing the thing that broke the startup.

Two different loops get mixed together in search results, and the right fix depends on which one you have. The first is the boot repair loop: the screen says "Preparing Automatic Repair", then "Diagnosing your PC", then "Automatic Repair couldn't repair your PC" with two buttons, Shut down and Advanced options. Choose restart and the cycle begins again. The second is the update rollback loop: the screen says "We couldn't complete the updates, Undoing changes made to your computer. Don't turn off your computer", or it sits on "Working on updates, 30% complete. Don't turn off your computer" for hours. Both can end in each other, because a rollback that fails halfway commonly leaves Windows unable to boot, which triggers Automatic Repair.

The reassuring part is that Windows keeps a separate, small recovery system on your drive that does not depend on the main Windows installation working. That recovery system is what you will use in this guide. It offers uninstalling the latest update, a command prompt for offline repairs, Safe Mode, System Restore and a reset that can keep your files. Almost every case on this page is solved with those five tools, in the right order, without reinstalling anything.

This guide is written for Windows 11, including the 24H2, 25H2 and 26H2 releases, and the steps are nearly identical on Windows 10. If you only want the shortest path, use the quick-fix box above. If that did not work, read on: the sections are ordered from the safest and fastest fix to the last resort, and each one tells you what to expect so you know whether to move on.

Why Windows ends up in a repair loop

Windows enters Automatic Repair when the startup process fails two consecutive times, and the usual causes are a damaged update, a corrupted boot configuration, a failing drive, a bad driver, or an interrupted shutdown during an update. The recovery system does not know which of those it is facing, so it runs a short list of generic checks, and when they do not find the problem it gives up and shows the error.

Here are the causes we see most often, from most to least common in remote support work.

• A cumulative or feature update that was interrupted or half installed. A power cut, a forced shutdown, a battery that ran flat, or a user holding the power button because the screen "looked frozen" are the classic triggers. Windows is left with an update marked as pending but missing files.
• A corrupted boot configuration (BCD) or damaged EFI partition. The BCD is a small database that tells the firmware which Windows to start. If it is damaged or points to the wrong partition, the PC cannot even begin to load.
• File system errors or a failing drive. Bad sectors on a hard drive or a worn-out SSD can corrupt exactly the files needed at boot. This is the cause that matters most, because repeated repair attempts on a dying drive can make data loss worse.
• A faulty driver or a recently installed program. Storage drivers (Intel RST or VMD, NVMe vendor drivers), graphics drivers and security software that hooks into startup are frequent offenders.
• Corrupted system files. Malware, a failed cleanup tool or an unexpected shutdown can leave critical files damaged.
• BIOS or firmware changes. A BIOS update, a reset to defaults that flips the disk mode from AHCI to RAID or the reverse, or a changed Secure Boot setting can make Windows look for its boot files in the wrong place.
• A BitLocker or TPM change. If device encryption is on and the firmware changes, startup can stall at a recovery prompt. See our guide on the Windows that will not boot after an update for the related patterns.

Notice what is not on the list: a virus is rarely the root cause, and a failed Windows licence almost never is. Treat the loop as a startup file and storage problem first.

Which screen do you have? A symptom table

Match the exact words on your screen to the row below, because "Automatic Repair", "Working on updates" and "Undoing changes" need different first moves. If you are unsure, start with the quick checks in the next section; they are safe for every row.

One more clue: the log file. When Startup Repair fails, it writes a report to C:\Windows\System32\Logfiles\Srt\SrtTrail.txt (the drive letter may differ inside WinRE). The "Advanced options" screen on the failed repair message usually shows the name of this file. The line starting with "Root cause found" is the most useful single line in the whole recovery environment, and it often names the exact file or driver that blocked startup. We will read it in the Startup Repair section.

Step 1: Quick checks that fix more loops than you would expect

Before opening any recovery menu, unplug every USB device, drain the power, and make sure the PC is not simply still installing an update. These three checks resolve a surprising share of loops in minutes and cost nothing.

1. Give a "Working on updates" screen real time. Large cumulative updates and feature updates can legitimately spend one to two hours on the percentage screens, especially on older PCs with a mechanical hard drive. Look at the drive activity light if your computer has one, or listen for the drive. If there is activity, wait. A common rule of thumb in support work is to wait at least two hours with no disk activity at all before concluding the process is hung. This is a rule of thumb, not an official Microsoft figure.
2. Disconnect everything non-essential. Unplug USB drives, SD cards, printers, docks, external monitors and phones. A faulty USB device or a dock with its own storage can confuse the boot order or hang a driver at startup. Keep only power, and the keyboard and mouse if they are wired.
3. Do a full power drain. Shut down completely (hold the power button for 10 seconds). On a laptop with a removable battery, take it out; on modern sealed laptops, unplug the charger and hold the power button for 30 seconds. Wait a minute, plug in only the charger, and start. This clears a stuck firmware state and resets the embedded controller. It sounds like folklore, but it works for a real reason: many laptops keep a partial state in the controller across normal restarts.
4. Check the BIOS or UEFI settings. Press the setup key at power on (often F2, F10, Del or Esc depending on the maker). Verify the internal drive is detected in the boot list. If the drive is missing here, Windows cannot be the problem: it is a cable, a drive or a firmware issue, and you should go to the hardware section. Also confirm that the SATA mode and boot mode (UEFI) match what they were before; if a BIOS update reset them, set them back.
5. Try one more normal restart. If the PC has just been through a rollback, the next normal boot sometimes completes the cleanup on its own.

Step 2: Get into the Windows Recovery Environment (WinRE)

The Windows Recovery Environment is the blue menu with "Troubleshoot", "Advanced options" and "Startup Settings", and every serious fix lives inside it. If your PC shows "Automatic Repair couldn't repair your PC", choose "Advanced options" and you are already in. If it does not appear, you can force it.

There are three reliable ways in, from easiest to most manual.

1. From the Automatic Repair screen. Click Advanced options. This opens the "Choose an option" menu. Click Troubleshoot, then Advanced options again. You will see Startup Repair, Uninstall Updates, Startup Settings, Command Prompt, System Restore and, on some builds, UEFI Firmware Settings.
2. Force it by interrupting boot. Turn the PC on. As soon as the manufacturer logo or the Windows spinning dots appear, hold the power button until it shuts off. Repeat two to three times. On the third startup, Windows should launch Preparing Automatic Repair. This works on almost every Windows 10 and 11 PC, but it should be a last resort, because interrupted starts are not harmless.
3. Boot from a Windows 11 USB drive. If the recovery partition itself is damaged, create a Windows 11 installation USB on another PC from Microsoft's official download page (8 GB or more). Boot from it using the one-time boot menu key (often F12, F9 or Esc), choose your language, and click Repair your computer in the bottom left corner (not Install now). That leads to the same menu.

If your drive is encrypted with BitLocker or Device Encryption, WinRE may ask for the recovery key before it lets you open the Command Prompt or other tools. That key is a 48-digit number. You can find it by signing in at your Microsoft account's recovery key page from another device, or in the printout or file you saved, or in your work or school account. Our guide on the Windows boot problems after an update explains where the key usually hides. Do not skip this: without it, the encrypted drive stays locked.

Step 3: Read the one clue Windows leaves for you

The file SrtTrail.txt, the Startup Repair log, tells you why the automatic repair failed, and its "Root cause found" line points you to the correct fix in this guide. You can open it right from the failure screen. Click Advanced options on the "Couldn't repair your PC" message, and the screen shows the log location, normally D:\Windows\System32\Logfiles\Srt\SrtTrail.txt. Inside WinRE the Windows partition is very often called D: rather than C:, which confuses almost everyone.

To read it, go to Troubleshoot, Advanced options, Command Prompt, then type:

notepad D:\Windows\System32\Logfiles\Srt\SrtTrail.txt

If the file is not found, try C: instead, or find your Windows drive by typing dir C:\Windows and then dir D:\Windows until one of them lists a folder. In the notepad window, scroll to the last block and read the lines "Root cause found" and "Repair action". The table below translates the most common root causes.

You do not have to memorize any of this. The point is that the log removes guesswork: if it names a boot file, you will not waste an hour on a Safe Mode attempt that cannot work. If you want to talk it through with a technician who reads the log with you, the number is at the end of this guide.

Step 4: Uninstall the latest update from WinRE

If the loop started right after a Windows update, removing the latest quality update or feature update from the recovery menu is the fastest and safest fix, and it does not touch your personal files. This is the first thing to try when the trouble began after a Patch Tuesday restart.

1. In WinRE, click Troubleshoot, then Advanced options, then Uninstall Updates.
2. Choose Uninstall latest quality update first. A quality update is the monthly cumulative update, the kind that usually has a KB number and arrives on the second Tuesday of the month.
3. Select your account, enter your password if asked (a PIN does not work here, you need the account password), and confirm. The removal takes several minutes.
4. When it finishes, restart. If Windows starts, you are done for now: pause updates for a week or two (see the prevention section), then reinstall later when Microsoft has corrected the problem.
5. If the loop continues and the failure began after a bigger release such as 25H2 or 26H2, return and choose Uninstall latest feature update. Be aware that the feature update rollback is only available for a limited period after installing, commonly cited as 10 days, and it disappears after a Disk Cleanup of previous Windows installation files.

Two practical notes. First, if Windows asks for your account password and you only ever used a PIN or a Microsoft account fingerprint, use the Microsoft account password (the one you use on outlook.com). If you forgot it, reset it from another device before you continue. Second, the screen sometimes says "Couldn't uninstall the update" or that the update is not installed. That tells you something useful: the damage is probably not an installed update, so move on rather than repeating the step.

Step 5: Startup Repair, then bootrec and bcdboot for the boot configuration

Run Startup Repair once from the menu, and if it fails, rebuild the boot files by hand in the Command Prompt with bootrec and bcdboot. These commands repair the boot loader, not your files, and they take less than ten minutes. Do them in this order, because the later commands depend on the earlier ones.

Start with the simplest. In WinRE, choose Troubleshoot, Advanced options, Startup Repair, select your account, and let it run. It will either restart into Windows or say it could not repair the PC. If it fails, open Command Prompt from the same menu and continue.

5a. Find the right drive letters

Inside WinRE, letters are shuffled. Your Windows folder might be on D: instead of C:. Run:

diskpart
list volume
exit

Look for the large NTFS volume that holds your Windows installation and the small FAT32 volume of about 100 to 500 MB labelled System or EFI. Note the letters. Alternatively, test with dir C:\Windows and dir D:\Windows. The rest of this guide uses C: for Windows; replace it with your real letter.

5b. The classic bootrec sequence

bootrec /scanos
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

/scanos lists Windows installations the system can find. /fixmbr writes a standard master boot record (it is harmless on UEFI systems, which do not rely on it). /fixboot writes a new boot sector. /rebuildbcd scans for installations and offers to add them to the boot configuration. When asked "Add installation to boot list?", press Y then Enter. If /scanos reports zero installations, that is itself a clue: the Windows partition may be unreadable, so go to the chkdsk step and the hardware section.

On UEFI PCs, bootrec /fixboot often fails with "Access is denied". That is common and expected on current builds. The cure is to rebuild the EFI boot files with bcdboot instead.

5c. The bcdboot fix for "Access is denied" and a damaged EFI partition

diskpart
list disk
select disk 0
list partition
select partition 1
assign letter=S
exit
bcdboot C:\Windows /s S: /f UEFI

Pick the partition that is FAT32 and about 100 to 500 MB (it is often partition 1 or 2; use list volume to confirm the type shows "System"). The command bcdboot copies fresh boot files from your Windows folder to that partition and recreates the boot entries. If you see "Boot files successfully created", close the Command Prompt, click Continue, and see whether Windows starts. If the system disk is not disk 0, adjust the numbers. Only use these commands on the disk that holds Windows, and read each line before pressing Enter.

5d. When the 0xc000000f, 0xc0000225 or "No boot device" errors appear

These codes describe the same family of problem: the firmware cannot find a valid boot entry. After the bcdboot fix above, enter the BIOS and verify that the boot list contains "Windows Boot Manager" and that it is first. If it is missing, the bcdboot step did not finish, or the firmware has lost its boot entries. Re-run bcdboot with the correct partition letter. Our page on Windows 11 boot failure 0xc0430001 covers a related boot-failure code and its causes.

Step 6: Repair system files and the disk offline (chkdsk, sfc, DISM)

From the WinRE Command Prompt you can check the disk with chkdsk, repair protected system files with sfc using the offline switches, and revert half-installed updates with DISM. Run them in that order, and always against the correct Windows drive letter. Offline repair works because Windows is not running, so no file is locked.

6a. Check the file system with chkdsk

chkdsk C: /f

This checks the file system structure and fixes logical errors. It is fast on an SSD and can take 20 minutes or more on a large hard drive. Use chkdsk C: /r only if you suspect bad sectors and you are confident the drive is not physically failing, because /r reads every sector and can take hours, and heavy reading stresses a dying drive. If chkdsk reports "Windows has made corrections to the file system", restart and test. If it reports a large number of bad sectors, or it hangs repeatedly at the same percentage, stop: that is a hardware sign, covered below.

6b. System File Checker, offline

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Both switches are required in recovery mode: /offbootdir is the root of the drive that contains Windows and /offwindir is the Windows folder on it. If you see "Windows Resource Protection could not perform the requested operation", the most common reason is a wrong drive letter or a pending operation. Try again with the other letter, or use the DISM revert below first. If sfc finds and repairs corrupt files, restart and test. Microsoft's guidance on the System File Checker is linked in the sources.

6c. Revert pending actions with DISM

The most useful DISM command for a loop that follows a failed update is:

dism /image:C:\ /cleanup-image /revertpendingactions

It tells Windows to cancel the update operations that were queued but not completed, which is exactly the state "Working on updates" and "Undoing changes" get stuck in. The command reports "The operation completed successfully" when it works. Restart, and allow a long first startup. If the command says it cannot find the image or returns an error, check the drive letter. If it says there is nothing to revert, move to the next fix. A related and more manual trick, used by experienced technicians, is to rename the file C:\Windows\WinSxS\pending.xml to pending.old, because that file lists the operations Windows retries at each boot. This is an advanced step with a small risk of leaving the component store inconsistent, so only try it after the revert command, and make a note of the original name.

cd /d C:\Windows\WinSxS
ren pending.xml pending.old

If the log pointed at a damaged component store, offline RestoreHealth needs a healthy source, such as the install.wim file from a matching Windows 11 USB. That is more involved, and it is a good moment to call a technician rather than guess the parameters.

For deeper explanations of the related error codes that show up in Windows Update logs, see our pages on error 0x80073712 and error 0x800f0922, which are both frequent partners of rollback loops.

Step 7: Startup Settings and Safe Mode

If Windows can still load its basic drivers, Safe Mode lets you uninstall a bad driver or update, run a malware scan and remove the program that causes the loop. Reach it from WinRE through Troubleshoot, Advanced options, Startup Settings, Restart, then press 4 or F4. Press 5 or F5 for Safe Mode with Networking, which you need if you want to download a driver.

1. In WinRE choose Troubleshoot, Advanced options, Startup Settings, Restart.
2. When the numbered list appears, press 4 for Safe Mode, 5 for Safe Mode with Networking, or 6 for Safe Mode with Command Prompt.
3. If Safe Mode loads, open Settings, Windows Update, Update history, Uninstall updates and remove the most recent one. Then open Device Manager and roll back or uninstall recently changed drivers, starting with the graphics and storage controllers.
4. If you use a third-party security suite, uninstall it temporarily; such tools are a known source of boot failures after major updates.
5. Restart normally. If Windows loads, you have your answer: the problem was an update, a driver or a startup program.

Two other options on the same list are worth knowing. Option 7, Disable driver signature enforcement, lets an unsigned or incorrectly signed driver load once, which helps diagnose a driver problem but is not a permanent fix. Option 8, Disable early launch anti-malware protection, bypasses the anti-malware driver that sometimes blocks startup after a security product update. Microsoft documents these options in its recovery guidance.

As a diagnostic only, some guides suggest turning the automatic repair behaviour off with bcdedit /set {default} recoveryenabled No in the WinRE command prompt, so the PC shows the underlying error instead of re-entering the loop. It can help you see the real stop code. Turn it back on afterwards with bcdedit /set {default} recoveryenabled Yes. This is a widely published technique, we flag it as one to use deliberately.

If Safe Mode itself also loops or crashes, the problem is deeper than a driver. For a longer walk-through, see our guide for the blue screen of death on Windows 11, because a crash during Safe Mode often produces a stop code that narrows things down. Our driver update guide shows how to replace a problem driver once you are back in Windows.

Step 8: System Restore, the underused fix

System Restore rolls system files, drivers and the registry back to an earlier restore point without touching your personal documents, and it succeeds often when the failure is a bad driver or a bad registry write. It only works if a restore point exists. In WinRE choose Troubleshoot, Advanced options, System Restore, select your account, and pick the newest restore point from before the trouble began.

The wizard lists the date and a description (for example "Windows Update" or "Installed driver"). Click Scan for affected programs to see which programs and drivers will be removed; anything installed after that date disappears, and anything uninstalled after it comes back. Files in Documents, Pictures and Desktop are not removed. The restore can take 15 to 40 minutes and the PC will restart.

If the wizard says there are no restore points, that usually means System Protection was turned off, which is the default on some newer installations, or the points were removed during an earlier cleanup. It is not a sign that anything is wrong with your PC, and the other methods still apply. Once you are back in Windows, open Create a restore point from the Start menu and switch protection on for the C: drive so that next time you have this safety net.

A related old trick, restoring the registry from the C:\Windows\System32\config\RegBack folder, is mostly dead on modern Windows: since a 2018 change, Windows no longer creates those backups by default, so the folder is usually empty. Do not rely on it, and do not delete live registry files by hand unless a technician walks you through it.

"Working on updates" and "Undoing changes made to your computer": what to do, hour by hour

A stuck "Working on updates" or "Undoing changes" screen is usually Windows finishing, or reversing, a large update on a slow disk. Wait while the drive is active, force a restart only after about two hours of complete inactivity, and if the screen persists, use the DISM revert and the uninstall steps above. The wrong reaction is the very common one: switching the power off in the first twenty minutes.

Those time brackets are practical experience, not official limits. Microsoft does not publish a maximum duration for update installation, and hardware varies widely. A 2018 laptop with a 5400 rpm drive installing a feature update is a different animal from a new NVMe machine. If your PC is old and slow, give it the longer bracket.

If Windows starts again after "Undoing changes"

You are in a good position, because the system is intact. Do not click "Check for updates" at once. First, restart once more so the cleanup completes. Then free space: a failed update often needs at least 15 to 20 GB free on the C: drive. Run the Windows Update troubleshooter, disconnect any VPN, update the storage and graphics drivers, and install the failed update again, or wait for the next month's cumulative update, which often replaces the one that failed. Our guide Windows Update stuck or failing: how to fix it covers the update-side fixes in detail, and the page on the 25H2 update helps if the failing item is the feature update.

If the same update fails again and again

Write down the KB number and the error code from Settings, Windows Update, Update history. Look at the code in the relevant error page, for example 0x80070005 (access denied). Repeated failures at the same percentage usually mean a corrupt component store, low disk space, a faulty driver or third-party security software. Rather than retrying a fourth time, run DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow from an administrator terminal, then retry. Alternatively, install the update manually from the Microsoft Update Catalog, which bypasses the Windows Update download path.

When the real problem is the drive, the memory or the firmware

If every software repair fails, or the loop returns after each fix, suspect the storage drive first, then the memory, because a failing drive corrupts exactly the files Windows needs to start. Check the drive's health before spending hours on software. This is the section that decides whether you are fixing Windows or rescuing data.

Signs that point to hardware rather than software:

• The BIOS does not list the drive, or lists it with the wrong size.
• chkdsk hangs, or reports many bad sectors, or the drive disconnects during the scan.
• The PC clicks, grinds or beeps (hard drive), or the SSD disappears intermittently.
• The loop began after a drop, a spill or a heat event, or the PC is more than six or seven years old.
• Random blue screens, application crashes and corrupted downloads happened before the loop (a memory or drive warning sign).
• Different repair methods fail at different, random points, or the BCD gets corrupted again after you rebuild it.

Checks you can run without Windows:

1. Manufacturer diagnostics. Many laptops from Dell, HP and Lenovo include a built-in hardware test, started by a key at power on (for example F12 on Dell, F2 on HP, F10 on some Lenovo). It tests the drive and memory without needing Windows. A failure code gives you a clear message to take to a technician or to warranty.
2. SMART status. In the WinRE command prompt, wmic diskdrive get status may return "OK" or "Pred Fail". It is a rough indicator only, because many failing drives still report OK. On Windows 11 builds where wmic is missing, rely on the manufacturer diagnostics or a bootable tool.
3. Memory test. Windows Memory Diagnostic can be run from a booted system, and MemTest86 from a USB stick works without Windows. Run at least a few passes. Any error means a faulty module or slot.
4. Reseat and test. On desktops, reseat the RAM and drive cables. On laptops, only do this if you are comfortable opening the case, as many are glued or have warranty seals.

If the drive is the issue, the order of priorities changes: get the data off first, repair later, and replace the drive. Replacing a drive is a standard job that costs less than most people fear, and our SSD versus HDD upgrade and repair cost guide explains the options and prices. If the PC does not detect the drive at all, see hard drive not detected: how to fix it.

Protect your files before the last resorts

Before you run Reset this PC or reinstall Windows, copy your important files to another drive, because a reset that keeps files is reliable but not infallible, and a failing drive can lose data mid-process. You can do this without a working Windows.

The simplest method uses the WinRE Command Prompt. Plug in an external drive, then run diskpart, list volume, and find the letters of your Windows drive and the external drive (for example, C: and E:). Exit diskpart and copy the user profile:

robocopy C:\Users\YourName E:\Backup /E /R:1 /W:1 /XJ

Replace YourName with your actual user folder (check with dir C:\Users). The switches copy subfolders, retry once on errors and skip junction points that cause endless loops. Let it run until it finishes; the summary at the end lists any files it failed to copy. Another route is booting a Linux live USB, which reads NTFS drives easily and lets you drag files to an external disk. If the volume is BitLocker-encrypted, you must unlock it first with manage-bde -unlock C: -RecoveryPassword followed by your 48-digit key.

Once you have a verified copy, open a few files from the backup to confirm they actually open. Only then continue to the reset. For the wider picture on data loss after a failed update or reinstall, read data recovery after a Windows update or reinstall.

Last resort: Reset this PC (keep my files) or a clean reinstall

If every repair fails but the drive is healthy, Reset this PC with the "Keep my files" option reinstalls Windows and preserves your documents, but it removes your installed programs and many settings. It is the last software option before a full clean install. You can start it from WinRE: Troubleshoot, then Reset this PC.

1. Choose Keep my files. The other option, Remove everything, deletes personal files and should be used only when you have a verified backup and want a fresh start.
2. Choose Cloud download or Local reinstall. Local reinstall uses files already on the PC, which is faster but fails if those files are damaged. Cloud download fetches a fresh copy of Windows, needs a working internet connection and several gigabytes of data, and is more reliable when the local files are the problem.
3. Review the summary, then click Reset. The process takes from 30 minutes to a couple of hours, and the PC restarts several times. Keep it plugged in and do not interrupt it.
4. After it finishes, expect a list of removed apps on your desktop (Windows normally creates a file listing them). Reinstall your programs, then run Windows Update fully and update drivers.

Be realistic about what is lost: programs, license-bound software that needs reactivation, browser settings not synced to an account, saved Wi-Fi networks and local-only email. Before the reset, write down your software list. If the reset itself fails with "There was a problem resetting your PC" or an error about missing files, the component store or the recovery image is damaged, and the cleanest path is a clean install from a Windows 11 USB, after backing up. Our factory reset guide for laptops explains the differences between the reset types in more detail.

A clean install from USB wipes the target partition and gives you a brand new Windows, which also removes malware and old driver clutter. It is more work, but it is final. Windows 11 will normally reactivate itself if the PC had a digital licence tied to the hardware or to your Microsoft account.

Three realistic scenarios (illustrative)

These realistic scenarios show how the same loop can have three very different causes and fixes. The names and figures are illustrative examples, not real client cases.

Scenario 1: Laptop loops after Patch Tuesday (fixed in 25 minutes)

Realistic scenario. A bookkeeper's 3 year old laptop installs the monthly update overnight and in the morning shows "Automatic Repair couldn't repair your PC". She chooses Advanced options, Troubleshoot, Uninstall Updates, then Uninstall latest quality update. After about 8 minutes of removal and one restart, Windows starts. She pauses updates for 7 days. Total time: 25 minutes. Cost: nothing. A week later the next cumulative update installs without trouble.

Scenario 2: Desktop "undoing changes" for two hours, then loops (fixed in 90 minutes)

Realistic scenario. A home desktop with a 1 TB hard drive and 4 GB free space starts a feature update, spends 2 hours on "Working on updates 40%" and loses power in a storm. After the power returns, it displays "Undoing changes" and then Automatic Repair. The owner opens WinRE, runs dism /image:C:\ /cleanup-image /revertpendingactions and restarts. The boot takes 15 minutes, then Windows loads. He frees 40 GB by moving videos to an external disk, runs the update again and it completes. Total time: about 90 minutes. The root cause was low disk space combined with a power cut.

Scenario 3: Loop returns after every fix, drive failing (data saved, drive replaced)

Realistic scenario. A small office PC with a 6 year old hard drive loops. Startup Repair fails, bootrec seems to work, but the loop returns two restarts later. chkdsk hangs at 31% and the BIOS briefly drops the drive. The office manager stops, uses robocopy to copy 180 GB of accounting files to an external drive in 3 hours, and the manufacturer diagnostic reports a drive failure. A new 500 GB SSD is installed, Windows is reinstalled, the files are copied back, and the programs reinstalled. Total time: a day. The lesson: when repair attempts keep failing, protect the data first.

What this costs: DIY versus paying a technician (CAD)

Most Automatic Repair loops cost nothing to fix yourself, a clean reinstall or drive replacement costs roughly the price of a part and an hour or two of labour, and data recovery from a failing drive is the only truly expensive outcome. The figures below are typical ranges in Canada and will vary by shop and region.

Our remote service price is a single 119.99$ CAD for a 60 minute expert consultation. Because the work is done remotely when the PC can still reach the internet, in many cases there is no shipping, no drop-off and no days without your computer. When the PC cannot start at all, the options change: we guide you through the recovery menu by phone, or you take it to a shop, and our computer repair cost in Canada guide shows realistic shop prices. For a comparison of the two models, read remote IT support versus on-site computer repair.

How to avoid the loop next time

The most effective prevention is a current backup, enough free disk space, a charged or plugged-in device during updates, and the discipline to let an update finish instead of forcing a power-off. The checklist below takes ten minutes to set up.

You can also create a recovery drive on a healthy PC by searching for "Create a recovery drive" in the Start menu. It takes a USB stick of 16 GB or more and gives you the recovery tools even if the recovery partition on your PC is damaged. Keep the stick labelled and in a known place.

When to stop and call a professional

Call a technician when the drive shows signs of failing, when files are irreplaceable and not backed up, when BitLocker blocks you and you have no key, or when two or three of the steps above have failed. Past that point, more attempts rarely help and sometimes cost you data.

• The BIOS does not detect the drive, or the drive clicks or beeps.
• The loop returns after each successful repair.
• You see an unknown BitLocker prompt and cannot find the recovery key.
• The PC belongs to a business and each hour of downtime is expensive.
• You are not comfortable typing diskpart and bcdboot commands.

IT Cares has provided remote and on-site IT support in Quebec and across Canada since 2014. Our rating on Google is 4.9 stars from 78 reviews. We can walk you through WinRE by phone, read the SrtTrail log with you, and decide with you whether to repair, reset or rescue the data first. Call 1 (888) 711-9428 or book a remote session. If you only get the Automatic Repair screen and cannot connect remotely, say so on the call and we will adapt the plan.

Official resources

These Microsoft pages explain the recovery environment and the tools used in this guide. We list them as references for further reading.

• Recovery options in Windows (Microsoft Support)
• Use the System File Checker tool (Microsoft Support)
• Windows Recovery Environment technical reference (Microsoft Learn)
• Windows release health (known issues after updates)

Frequently asked questions

Related guides

• Windows won't boot after an update: fix
• Windows Update stuck or failing: how to fix it
• Windows 11 boot failure 0xc0430001
• Fix the blue screen on Windows 11
• Data recovery after a Windows update or reinstall
• Hard drive not detected: how to fix it
• SSD vs HDD upgrade and repair costs
• How to factory reset a laptop
• Windows 11 25H2 update guide
• Fix error 0x80073712

Sources and official references

Last verified: October 1, 2026

• Recovery options in Windows (Microsoft Support)
• Use the System File Checker tool (Microsoft Support)
• Windows Recovery Environment technical reference (Microsoft Learn)
• Windows release health (Microsoft Learn)