Windows Update is supposed to run on its own. Except when it doesn’t. And when it doesn’t, your PC stays wide open to malware, ransomware, and anyone scanning for known flaws. Microsoft itself admits that most successful attacks exploit holes that already had a patch available. So if your machine is stuck on «You’re up to date» while your build is months old, you have a problem worth fixing today.
Below is how to force Windows 10 and Windows 11 updates using methods that actually work in 2026, not the recycled advice from 2018 that no longer applies.
Why Windows Update Sometimes Gets Stuck
The most common culprits are corrupted update components, a half-installed patch, or a Group Policy setting that quietly disabled automatic updates. On Windows 11, the notorious «Update paused» toggle can also be silently flipped after a failed install attempt.
There’s another factor people ignore: Microsoft now rolls out updates in phases. Your device might simply be in a later rollout bucket. That’s not a bug, but it’s cold comfort when you’re missing a critical security patch that everyone else already has.
According to Microsoft’s Security Response Center, the company patches 100+ vulnerabilities every month. Skipping even one Patch Tuesday leaves you exposed to exploits that are already public.
Method 1: Force an Update from Windows Update Settings
This is the obvious one, but most people do it wrong. Checking for updates once isn’t enough if the service itself is broken.
- Press Win + I and go to Windows Update (Windows 11) or Update & Security (Windows 10).
- Hit Check for updates. If it stalls for more than 60 seconds, close it and reopen.
- Click Download & install if updates appear. If nothing appears, open Advanced options → Optional updates and install those too.
- Reboot. Not shutdown. Reboot. Windows often finalizes patches on restart, not on shutdown.
If you see error codes like 0x80070002 or 0x800f081f, jumping straight to the next method usually saves you an hour of pointless troubleshooting.
Method 2: PowerShell and PSWindowsUpdate (the Real Fix)
When the GUI refuses to cooperate, PowerShell doesn’t care. This is the method I recommend for anyone dealing with blocked updates on Windows 10 or 11.
Open PowerShell as administrator (right-click → Run as administrator), then run:
Install-Module PSWindowsUpdate -Force
Get-WindowsUpdate -Install -AcceptAll -AutoReboot
This bypasses the Windows Update UI entirely and pulls patches directly from Microsoft’s servers. If Install-Module fails because of execution policy, run Set-ExecutionPolicy RemoteSigned -Scope CurrentUser first.
You can also list pending updates without installing them by running Get-WindowsUpdate alone. Useful when you want to know what’s coming before it triggers a surprise reboot mid-meeting.
Method 3: Use the Microsoft Update Catalog to Force Manual Installs
Some patches never show up through Windows Update because they’re pulled from distribution or superseded by another build. In that case, the Microsoft Update Catalog is your best friend. Search for the KB number (for example, KB5034441), download the .msu file matching your architecture, and double-click to install.
This is the only reliable way to force a Windows 10 or Windows 11 update when your device is on a metered connection, a corporate network, or an outdated build that Microsoft has quietly stopped pushing to.
What to Do When Updates Are Paused or Blocked by Policy
If your update history shows a long pause or your organization pushed a «Defer feature updates» policy, you need to override it manually:
- Open gpedit.msc (Pro editions) and go to Computer Configuration → Administrative Templates → Windows Components → Windows Update.
- Set Configure Automatic Updates to «Not Configured» or «Enabled».
- On Home editions, delete the registry key HKLMSOFTWAREPoliciesMicrosoftWindowsWindowsUpdate after backing it up.
Restart the machine and retry the PowerShell method. Nine times out of ten, this unsticks a frozen update pipeline.
Run the Windows Update Troubleshooter (Yes, It Still Helps)
Microsoft’s built-in troubleshooter gets mocked, but it does one useful thing: it resets the SoftwareDistribution folder, which is where Windows caches update files. If those cached files are corrupted, every manual attempt will fail silently.
Go to Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. Then check again. If it still fails, delete the SoftwareDistribution folder manually after stopping the wuauserv service.
Should You Force Feature Updates Too?
Here’s where I’ll take a position: no, not blindly. Security updates? Force them without thinking twice. Feature updates (like moving from Windows 11 23H2 to 24H2) can break drivers, VPN clients, and older software. If your PC works and only the build number is old, wait until Microsoft offers it to your device naturally.
The exception is if your current build has reached end of servicing. At that point, you’re not getting security patches at all, and forcing the feature update becomes mandatory, not optional.
Quick Recap of the Fastest Route
If you only remember one thing: when Windows Update refuses to move, PowerShell with PSWindowsUpdate will push through almost anything. The GUI is a suggestion; PowerShell is a command. For stubborn cases, the Microsoft Update Catalog gives you the patch directly, no middleman.
And once you’re updated, don’t disable updates again just because a reboot annoyed you once. That single decision is behind a shocking number of ransomware stories you’ll never read about, because the victims don’t advertise it.
