Fix Windows 11 Updates Stuck at 46%: 2026 Guide

Discover how to fix Windows 11 updates stuck at 46%. Learn quick fixes, SFC, DISM, and cache resets. Stop the 46% loop and update your PC successfully today.

I’ve spent the last hour staring at a progress bar that hasn’t moved since it hit 46%. If you’re here, chances are you’re feeling the exact same frustration. The screen says “Getting Updates,” the cursor is spinning, and nothing is happening. It feels like your computer is stuck in a time loop, and you’re wondering if you’ve just bricked your machine or lost your files.

Let’s get one thing straight right away: this is a known, solvable issue, not a hardware failure. While it’s annoying, the underlying problem is usually a mismatch between the update service and your network stack, not a broken hard drive. In my 15 years of troubleshooting, I’ve seen the windows 11 updates stuck at 46 error occur on everything from brand-new laptops to older desktops, often triggered by the release of Windows 11 Build 22000 and the subsequent 25H2 cycles.

This guide isn’t just a list of "wait and see" advice. I’ll walk you through a structured path to resolving this. We’ll start with quick wins, like using the Windows Update Troubleshooter and checking your network settings, and move toward advanced command-line repairs if those don’t work. By the end, you’ll have the tools to fix the issue without losing your data or performing a clean install.

Close-up of a smartphone displaying Android recovery mode with an SD card inserted.

Why Windows 11 Gets Stuck at 46%: The Technical Root Cause

To fix a problem, you first need to understand why it’s happening. Most online guides just say "restart the service," but that rarely addresses the root cause. Let’s dig into what is actually happening inside your PC at this specific percentage.

Understanding the 'Getting Updates' Phase

Think of the Windows Update process like a complex supply chain. It doesn’t just download one big file. It’s a sequence of distinct phases. The 46% mark is a critical checkpoint. This is where the system transitions from preparing the local environment to actively retrieving the cumulative update files from Microsoft’s servers.

During this phase, the Windows Update service interacts heavily with your TCP/IP stack. It needs to establish a secure handshake with Microsoft’s update servers. If your network adapter has an outdated driver, if your ISP is throttling specific ports, or if there’s a conflict with your router’s DHCP settings, this handshake fails. The progress bar freezes because the system is waiting for a response that will never come, or it times out silently without throwing a visible error.

I’ve also found that low Storage Capacity can cause I/O bottlenecks here. If your drive is almost full, the system struggles to temporarily store the update manifest files it needs to verify before the download even completes. It’s a bit like trying to unpack a moving box when you have no floor space to stand on.

Common Triggers: Network, Drivers, and Antivirus

In most cases I’ve handled, the culprit falls into one of three categories. First, third-party antivirus software is a major offender. Many AV suites hook into the file system to monitor writes. When Windows Update tries to copy new system files, the AV might flag the action as suspicious or slow down the process to "scan" it, causing the update to hang.

Second, outdated NIC (Network Interface Card) drivers or incorrect proxy settings disrupt the communication channel. If your corporate environment uses a proxy, and that proxy isn’t configured correctly in Windows 11, the update service can’t reach the internet at all, even if you can browse the web fine.

Finally, on older PCs, BIOS Update requirements can trigger compatibility checks that loop indefinitely. If your firmware is significantly behind what the latest 25H2 build expects, the update engine might get stuck verifying hardware capabilities. Before jumping to command-line fixes, it’s worth checking if your motherboard manufacturer has a pending BIOS update.

A close-up photo of a computer screen showing the settings button with a cursor hovering over it.

Quick Fixes: Resolving Windows 11 Update Problems in Minutes

Before we get into the nitty-gritty of command prompts, let’s try the safe, built-in tools. These steps address the majority of transient glitches.

Run the Windows Update Troubleshooter

Windows 11 includes a built-in diagnostic tool that is surprisingly effective at resetting corrupted update components. It’s not just a placebo; it actually resets the state of the Windows Update Troubleshooter services and clears temporary files.

Here is how to access it:

  1. Open Settings (Win + I).
  2. Go to System > Troubleshoot > Other troubleshooters.
  3. Find Windows Update and click Run.

Let it finish. It might say "No fix found," but often it has already reset the service counters in the background. After it finishes, try the update again. I recommend waiting a few minutes after the troubleshooter runs before checking your progress, as the system needs time to re-index its update catalog.

The 'Wait or Restart' Decision Tree

When the bar freezes at 46%, the hardest part is deciding when to intervene. Restarting too early can leave you with a half-installed update, but waiting too long wastes hours. I use this simple decision tree in my support calls:

  • 0-5 Minutes: Wait. The system might be performing background defragmentation or file verification.
  • 5-30 Minutes: Check your network. Ensure you’re not on a metered connection that has been disabled for updates. If you’re on Wi-Fi, try moving closer to the router.
  • 30+ Minutes: It’s safe to restart. Being stuck at 46% during "Getting Updates" means the core system files are still intact. Unlike the "Configuring updates" phase (which is where the OS is actually being modified), this stage is mostly read-only and verification. A forced restart is unlikely to corrupt your OS.

Is it safe to leave it overnight? If you have the time, yes. Sometimes, the background service just needs a longer timeout window to complete a slow download. However, if you’ve been waiting for two hours or more, the network lock is likely permanent for that session, and a restart is the faster path forward.

Advanced Repair: Fixing Windows 11 Update Error via Command Line

If the quick fixes haven’t moved the needle, it’s time to get our hands dirty. This section covers how to fix windows 11 update error states by resetting the underlying services and repairing system integrity.

Resetting Update Services and Cache

The Windows Update cache is stored in two specific folders. If these folders get corrupted with bad data from a previous failed update, every new attempt will fail at the same spot (usually 46% or 74%). We need to clear this cache manually.

Open Command Prompt as Administrator (right-click Start > Terminal (Admin)). Copy and run these commands one by one:

net stop wuauserv
net stop bits
net stop cryptsvc

Now, let’s rename the cache folders. This forces Windows to create new, empty ones on the next restart.

ren C:\Windows\SoftwareDistribution SoftwareDistribution.bak
ren C:\Windows\System32\catroot2 catroot2.bak

Restart the services:

net start wuauserv
net start bits
net start cryptsvc

Reboot your PC. This single step resolves a significant portion of persistent windows 11 update stuck issues because it clears the "pending" update state that is locking the progress bar.

Using SFC and DISM to Repair System Corruption

If the cache reset didn’t work, the problem might be deeper. The System File Checker (SFC) and the DISM command are your best friends here. SFC scans for corrupted system files and replaces them with a cached copy. DISM repairs the component store, which is the library SFC uses.

Run these in an Admin Command Prompt:

sfc /scannow

Wait for this to finish (it can take 10-15 minutes). Once it’s done, run:

DISM /Online /Cleanup-Image /RestoreHealth

I explain this to clients like this: Imagine your house (the OS) has a missing shingle (a corrupted file). SFC tries to find a replacement in your attic (the component store). But if the attic is broken, you need DISM to fix the attic first. That’s what /RestoreHealth does. It downloads fresh copies of system components from Windows Update servers to repair the local store.

After both commands complete successfully, restart your PC and try the update again.

Disabling Dynamic Update and Third-Party Interferences

Some conflicts come from services that run in the background. Dynamic Update is a service that allows Windows to download minor updates without a reboot, but it can sometimes conflict with the main update loop. Temporarily disabling it can help.

More commonly, it’s third-party antivirus and firewalls. I always advise clients to disable their non-Microsoft AV (like Norton, Avast, or MacAfee) and third-party firewalls for the duration of the update. Do not uninstall them; just disable real-time protection. Once the update completes, re-enable them immediately. Leaving your system unprotected is a risk I don’t recommend, but for a 30-minute window, it’s a necessary trade-off to clear the conflict.

Network Diagnostics: Ensuring Stable Connectivity for Updates

Sometimes the issue isn’t your PC, it’s the pipe connecting it to the internet. The windows 11 update stuck error is frequently a DNS or TCP/IP issue.

TCP/IP Reset and DNS Configuration

If your DNS settings are pointing to a slow or blocked server, the update handshake will fail. Let’s reset your network stack.

Open Command Prompt as Admin and run:

netsh winsock reset

You will be prompted to restart your computer. Do so.

After rebooting, you can test by manually setting your DNS to a public resolver. Go to Settings > Network & Internet > Wi-Fi (or Ethernet) > Properties > IP settings > Edit. Set your DNS to:

  • Preferred: 8.8.8.8
  • Alternate: 1.1.1.1

This bypasses any ISP-level DNS blocking that might be interfering with Microsoft’s update domains. Also, double-check Settings > Proxy. Ensure "Automatic" is selected, or that your manual proxy settings are correct. A wrong proxy entry is a classic cause of the 46% freeze.

Offline Installation Strategy

If online updates just won’t budge, you can force an offline installation. This is particularly useful if you’re trying to move to the latest 25H2 build and the online checker is buggy.

  1. Download the Windows 11 Installation Assistant from the Microsoft Support page on a working PC.
  2. Or, use a USB drive with the Windows 11 ISO image.
  3. Run setup.exe from the ISO or USB.
  4. Crucial Step: When asked to "Download and install updates," select "Not right now."

This bypasses the online verification phase that is currently hanging at 46%. Windows will install the base OS from the local media. Once the installation is complete and you have a fresh desktop, you can reconnect to the internet and run a normal Windows Update check. The cumulative patches will then download individually, which often works better than the bundled "feature update" mechanism.

MethodProsCons
Online UpdateFast, seamlessProne to 46% hangs
ISO "Not Right Now"Bypasses online checkRequires internet later for patches
USB MediaReliable, offline capableRequires physical media

FAQ

Why is my Windows 11 update stuck at 46% instead of 100%?

The 46% mark is a specific checkpoint in the "Getting Updates" phase where the system verifies cumulative patches and compatibility before final installation. If the network handshake fails or a service times out at this verification stage, the progress bar freezes because the system is waiting for a response that doesn't arrive.

Is it safe to restart my PC if Windows 11 update is stuck at 46%?

Yes. Unlike the "Configuring updates" phase, being stuck at 46% during "Getting Updates" usually means the core system files are intact and no active changes are being written to the disk. A restart is safe and often resolves transient network locks or service hangs.

What should I do if SFC and DISM commands don't fix the update issue?

Proceed to manually clearing the Windows Update cache (renaming SoftwareDistribution and CatRoot2) or temporarily disable third-party antivirus. If all else fails, use the Media Creation Tool or ISO to run an in-place upgrade from a USB drive, selecting "Not right now" for updates during the installation process to bypass the online check.

Does Windows 11 update stuck at 46 indicate a disk error?

Not necessarily. While a failing hard drive can cause stalls, the 46% freeze is primarily a network/service handshake point. However, check Event Viewer (specifically the "System" log) for disk I/O errors (like NTFS errors). If you see those, your priority shifts from network settings to checking your drive health via chkdsk or manufacturer tools.

Conclusion

Navigating through a frozen update can feel like walking through mud, but as we’ve seen, the windows 11 updates stuck at 46 issue is rarely catastrophic. It’s usually a communication breakdown between your update service and your network stack. By moving from quick fixes like the Windows Update Troubleshooter to advanced command-line resets of the cache and system files, you can regain control without resorting to a clean install.

Remember to re-enable any antivirus or services you disabled, and run a final check in Windows Update to ensure all pending patches are installed. If the issue persists after trying all these steps, check the Microsoft Support page for specific error codes (like 0x800f0818) which may point to a specific driver issue.

I hope this guide helps you get back to a fully updated, stable system. If you’re struggling with a specific error code, share it in the comments or check the Microsoft Community forums where others may have identified a recent 25H2 bug. Happy troubleshooting.

← Back to Home