Windows often updates at the worst moment: you sit down to finish a deadline, and the machine decides to reboot. That is why many people search for how to pause Windows updates. Windows 10 and Windows 11 both include a built-in pause control, and it is simpler than most guides suggest. The catch is that “pause” means different things depending on the tool you use, and the limits are stricter than most people expect. The built-in option comes first, then controls for advanced users, then the common mistakes that turn a quick pause into a broken update system. (Windows Update)
The Built-In Pause Button Is Easier Than You Think
The fastest route lives right inside Settings. Microsoft added a dedicated Pause updates control to Windows 10 in the May 2019 update and carried it into Windows 11 at launch. Anyone running a supported build has it.
Here’s the basic path:
- Open Settings (press the Windows key and type “Settings,” or use the shortcut list in this guide to Windows keyboard shortcuts everyone should know).
- Go to Windows Update in Windows 11, or Update & Security → Windows Update in Windows 10.
- Click Pause updates and choose a duration from the dropdown.
- To resume early, click Resume updates in the same spot.
That’s it. No registry editing, no third-party tools, no command line. For most home users, this is the only method they’ll ever need.
How Long Can You Actually Pause?
This is where expectations and reality split. The built-in pause is capped at 35 days total across both Windows 10 and Windows 11. Depending on your build, you’ll see options in one-week increments, often up to five weeks at a time.
Here’s the part that frustrates people: once the pause expires, Windows installs any pending updates automatically, and you cannot pause again until those updates are installed. The pause button simply won’t work. It’s a temporary brake, not a parking permit.
That design is deliberate. Microsoft’s servicing model treats updates as a security baseline, and the 35-day ceiling exists so machines don’t drift indefinitely without patches. If you need a longer window, you need a different mechanism entirely, which is where the next section comes in.
Pausing Versus Deferring: Two Different Tools
A huge amount of confusion online comes from people mixing up pausing and deferring. They are not the same feature, and they live in different parts of the system.
| Feature | Who can use it | Maximum window | Where it lives |
|---|---|---|---|
| Pause updates | All editions | 35 days total | Settings → Windows Update |
| Deferral policies | Pro, Enterprise, Education | Longer, policy-dependent | Group Policy or Intune |
| Metered connection | All editions | Indefinite, unofficial | Network settings |
| Third-party blocker | All editions | Indefinite, unsupported | Separate software |
The pause button is a consumer convenience. Deferrals are an IT management tool. Metered connections and third-party blockers are workarounds, and workarounds carry risk.
If you’re on Windows Home, the pause button is genuinely your only supported option. If you’re on Pro or above, you have real alternatives.
Group Policy: The Pro and Enterprise Route
On Windows Pro, Enterprise, and Education, the Local Group Policy Editor exposes update controls that the Settings app hides. The relevant policy is Configure Automatic Updates, found under Computer Configuration → Administrative Templates → Windows Components → Windows Update.
Inside that policy, you can set the behavior to “Notify for download and notify for install” rather than automatic installation. That gives you a manual gate: Windows tells you an update is ready, and you decide when to pull the trigger. It’s not a true pause, but it achieves the practical goal of not being surprised.
The exact policy names and deferral options differ between Windows 10 and Windows 11, and Microsoft has been steadily retiring some older deferral settings in favor of newer targeting and rollback features. That means a how-to written in 2021 may point you at options that no longer exist. Always check the current policy definitions on your own build before assuming a guide is accurate.
One practical tip from experience: after changing Group Policy, run `gpupdate /force` from an elevated command prompt, then restart the Windows Update service. Policy changes often don’t apply to the update pipeline until the service cycles. People frequently conclude “the policy didn’t work” when they simply never restarted the service.
What About the Registry Method?
You’ll find plenty of articles telling you to edit values under `HKLMSOFTWAREMicrosoftWindowsUpdateUXSettings`, particularly `PauseUpdatesExpiryTime` and the feature update start-time values. These are the keys the Settings UI itself writes to.
Here’s the honest assessment: Microsoft does not document these as a supported administrative interface. They work, sometimes, on some builds. They can also be silently reset by the next servicing operation, leaving you with a false sense of control. If you go this route, back up the registry first, and understand that you’re in unsupported territory.
A safer habit for anyone poking around system settings: learn the undo shortcut key for windows and mac so you can reverse accidental edits in text fields quickly, and keep a system restore point before touching the registry at all.
The Metered Connection Trick and Why It’s Fragile
Marking a Wi-Fi network as metered tells Windows to hold back some automatic downloads, because it assumes data is expensive. On some builds, this genuinely reduces update traffic.
But it’s not a pause. Microsoft doesn’t present metered connections as an update control, and behavior varies by build and by connection type. Ethernet connections can’t be marked metered through the normal UI at all. It’s a side effect, not a feature, and building a workflow around it is asking for confusion later.
Third-Party Blockers: Strong Control and Risk
Tools like Windows Update Blocker and the older `wushowhide.diagcab` utility circulate widely in forums. The hide tool was once distributed by Microsoft to suppress specific updates; its availability and support status today is uncertain, so verify before relying on it.
Dedicated blocker utilities typically work by disabling the Windows Update service outright. That does stop updates. It also stops security updates, and it can leave your machine exposed for months. If you use one, treat it as a short-term measure with a firm end date, not a permanent configuration.
There’s a related hygiene point worth making. Machines that go long stretches without patching are exactly the machines that pick up malware, and cleaning up afterward is far more work than pausing for two weeks. If you ever suspect something slipped in during an unpatched window, this walkthrough on how to check for viruses on a windows pc covers the basics, and these best free virus removal tools for windows are a reasonable starting kit. (Windows 11)
A Realistic Pause Strategy That Actually Works
Rather than chasing an indefinite block, most people are better served by a simple rhythm. Here’s what tends to work in practice.
Pause before high-stakes periods. Big presentation, exam week, a video call you can’t reschedule? Pause for one or two weeks. That’s the exact use case the feature was designed for.
Never pause past 35 days by stacking tricks. Pausing, then editing the registry, then disabling the service is how people end up with a machine that hasn’t been patched in a year and a half.
Let the pause expire on a quiet day. If you know your pause ends on a Friday, plan to leave the laptop on and plugged in that evening so updates install while you’re not working.
Check what’s pending before you resume. A quick look at the update history tells you whether you’re about to receive a routine quality update or a full feature upgrade. The two have very different time costs.
Keep an eye on lifecycle dates. Windows 10 reached the end of mainstream support on October 14, 2025, with consumer Extended Security Updates offered for a fee. Pausing updates on an out-of-support system doesn’t extend its servicing window; it just delays the patches you’re already entitled to. On Windows 11, each feature update has its own end-of-servicing date, and pausing never moves that date.
That last point matters more than most articles admit. Pausing is a scheduling tool. It is not a substitute for staying current, and it can’t rescue an operating system that’s past its support life.
Common Mistakes People Make
A few patterns show up again and again in support threads.
Assuming pause is permanent. It isn’t. The 35-day cap is hard, and the button locks after expiry.
Confusing pause with deferral. These are separate systems with separate limits, and guides that blend them produce settings that don’t behave as described.
Editing the registry without a backup. Unsupported keys can be reset mid-servicing, and without a restore point you may not notice until something breaks.
Disabling the update service and forgetting. Months later, the machine is unpatched and the owner has no idea why a security scan is flagging dozens of missing patches.
Ignoring restart prompts during a pause. A pause stops new updates from downloading, but an update that already installed and is waiting for a reboot still needs that reboot. Skipping it can leave components in a half-configured state.
Not checking for driver and firmware updates separately. Pausing Windows Update doesn’t pause manufacturer tools, and it doesn’t stop every driver from arriving through other channels.
When Pausing Is the Wrong Tool
Sometimes the real problem isn’t update timing at all. If updates are failing repeatedly, pausing just delays the failure. If a specific update is breaking a driver, the fix is rolling back that update, not freezing the whole pipeline. And if the machine is shared or handles sensitive data, indefinite pauses are a compliance problem, not a convenience.
The honest framing is this: pausing is a scheduling feature for a few weeks. Anything longer should go through proper deferral policy if you have the edition for it, or through a managed update strategy if you don’t.
Conclusion
Pausing Windows updates takes about fifteen seconds: Settings, Windows Update, Pause updates, pick a duration. That’s the whole procedure for most people, and it works well for exactly what it was built for, which is getting Windows out of your way during a busy stretch. The 35-day ceiling is real and non-negotiable, and the pause button genuinely stops working until pending updates install. Users on Pro and above can go further with Group Policy deferrals, but those controls have shifted over time and need verification against current documentation. Registry edits and service blockers technically work, yet they trade a small scheduling convenience for real security exposure and unpredictable behavior. The balanced approach is straightforward: pause when you need breathing room, let it expire on a quiet day, and never let a temporary brake become a permanent one. For anyone tracking how update policies and platform changes ripple through the wider tech world, resources like Dealer Daily: Major Auto News and Industry Updates show how quickly industry shifts move, and Windows servicing follows the same pattern of constant adjustment.
Frequently Asked Questions
How long can I pause Windows updates?
The built-in pause in Windows 10 and Windows 11 is capped at 35 days total. Depending on your build, you’ll choose from increments of roughly one to five weeks. Once the pause expires, Windows installs pending updates automatically, and the pause option stays unavailable until those updates are installed.
Does pausing updates stop security patches too?
Yes. The pause control is not selective. It holds back quality updates, which include security fixes, along with everything else in the pipeline. That’s why short pauses are low-risk and long ones aren’t. If you pause, plan to resume within a couple of weeks.
Can I pause updates forever?
Not with any supported method. Group Policy deferrals on Pro, Enterprise, and Education editions extend the window but still expire. Third-party tools that disable the Windows Update service can block updates indefinitely, but they also block security patches and leave the system exposed, so they’re a poor long-term choice.
Why is my pause button greyed out?
The most common cause is that a previous pause has expired with updates still pending. Windows requires you to install those updates before you can pause again. Other causes include managed-device policies applied by an employer or school, and certain metered connection states.
Is it safe to edit the registry to extend a pause?
Microsoft doesn’t document the pause-related registry values as a supported administrative interface. They can work on some builds, but they may be reset during servicing, and there’s no guarantee of consistent behavior. Back up the registry and create a restore point before trying, and don’t rely on the result as a permanent fix.
What’s the difference between pausing and deferring updates?
Pausing is a consumer feature in Settings with a 35-day cap. Deferring is a management feature available through Group Policy or mobile device management on business editions, with longer windows that vary by policy and Windows version. They’re separate mechanisms, and guides that treat them as the same thing tend to produce confusing results.
