Flamingo Raises $4.5M Seed Round

Skip to content

How to stop Windows Update without breaking Defender

IT Operations
Troubleshooting
Aliaska VarievaAliaska Varieva
September 18, 2026
1,579 views
How to stop Windows Update without breaking Defender

A method-by-method guide for IT teams and MSPs: what pause, active hours, metered connections, service commands, Group Policy, registry values, update rings and SConfig on Windows Server each stop, how to confirm a hold took, and how to undo one when Windows won't update.


Updated: November 2026

To stop Windows Update, open Settings > Windows Update and pause it for up to 35 days, the only off switch Microsoft supports. This guide covers that pause, canceling an update already in progress, and the policies that hold across an in-house fleet or a client base. It also covers the side effect to check first: Microsoft Defender gets its signatures through Windows Update, so disabling it can leave Defender up to a week out of date.

TL;DR

  • Pause is the supported off switch. Up to 35 days, then it resumes on its own.
  • An update in progress stops when you pause. Once it's installing at restart, let it finish and uninstall it afterwards.
  • Active hours stops the restart, not the download. Metered connections still let priority updates through.
  • Disabling the service does not hold. It is re-enabled by a component Microsoft has never documented.
  • Defender rides the same pipe. Break Windows Update and signatures can go stale for seven days.

Pause updates, the only supported off switch

On Windows 11 the path is Start > Settings > Windows Update, then Pick a date on the Pause updates control. Microsoft's pause documentation sets the ceiling at 35 days from the current date, and the calendar will not offer you a date beyond it. Extending resets to 35 days from today rather than adding to what you already used.

On Windows 10 the path is Start > Settings > Update & Security > Windows Update, then either Pause updates for 7 days or Advanced options and a resume date.

Two things worth knowing before you rely on it. Updates already in progress are canceled when you pause. And when the pause expires the device checks, downloads and installs on its own, with no prompt.

Microsoft's own documentation contradicts itself here. The Windows Update FAQ, last dated March 2026, says that after the pause limit you will need to install the latest updates before you can pause again. The pause article, dated May 2026, describes extending repeatedly inside a rolling 35 days. They also describe two different interfaces. Treat the behavior as build-dependent and check the machine in front of you rather than trusting either page.

When the pause limit has been reached or pause is grayed out

"The pause limit has been reached" means the device has used its full 35 days. Microsoft's FAQ says you'll need to install the latest updates before Windows offers the pause again, so let the pending updates install, restart, and the button comes back.

A grayed-out Pause updates button is a different problem. Either the device is managed by an organization and its policy hides the option, or someone enabled the Group Policy setting Remove access to "Pause updates" feature. On a work machine, that's a conversation with whoever manages it, not a setting to fight.

How to resume Windows updates after a pause

To unpause, open Settings > Windows Update and select Resume updates. Windows 11 lets you resume manually at any time, and Windows 10 resumes on its own on the date you picked. Either way, the device then checks for, downloads and installs everything it held back, so plan for a restart soon after.

How to stop a Windows Update in progress

How you cancel an update depends on how far it got.

  • Downloading or installing in the background. Pause updates. Microsoft's pause page says updates in progress are canceled when you pause, which makes it the cleanest cancel available.
  • Showing Working on updates at a restart. There is no cancel button at this stage. Let it finish rather than cutting the power mid-install, then remove the update afterwards if it caused the problem.
  • Already installed. On Windows 11, Settings > Windows Update > Update history > Uninstall updates lists the updates you can remove.

Removal has limits. Microsoft's recovery options page notes that some updates can't be uninstalled, and that going back to the previous version of Windows is only available for 10 days after an upgrade. If the machine won't boot, the Windows Recovery Environment offers the same removal under Troubleshoot > Advanced options > Uninstall updates.

On a fleet, cancel by policy rather than machine by machine. The pause values and their 35-day cap are in the deferral section below.

Active hours stops the restart, not the update

Active hours is the setting people reach for when the real complaint is a reboot, not a patch. It does nothing to downloading or installing. Microsoft's own wording in the Update Policy CSP is that the PC will not automatically restart during the window, and that is the whole scope of it.

The range is configurable but bounded: between 8 and 18 hours, defaulting to 18, with a start default of 8 and an end default of 17. On Windows 11 it sits under Settings > Windows Update > Advanced options > Active hours, with an Adjust active hours dropdown offering Automatically or Manually. Windows 10 puts it behind Change active hours with a separate auto-adjust toggle.

One trap: the start and end values have no effect at all if either "No auto-restart with logged-on users for scheduled automatic updates installations" or "Always automatically restart at scheduled time" is enabled. If active hours appear to be ignored, check those two before anything else.

Metered connection, and what it does not block

A metered connection is a network Windows treats as having a data cap or a per-megabyte cost, so it holds back background downloads to save data. You set it per network: in Windows 11, go to Settings > Network & internet, open the Wi-Fi or Ethernet connection, and switch on Metered connection.

Marking a connection metered is the softest block available and the most misunderstood. Microsoft's metered connections page says Windows Update will only download priority updates, Store downloads might pause, and offline files might not sync.

Read that phrasing carefully. It is not "no updates" and it is not "security updates only" either, because Microsoft never defines what counts as a priority update on that page. Quote it as written when you explain it to a user or a client rather than translating it into a promise you cannot keep.

Cellular connections are metered by default and Wi-Fi is not. There is also an explicit override at Settings > Windows Update > Advanced options > Download updates over metered connections, and a matching policy called "Allow updates to be downloaded automatically over metered connections", so a metered block can be quietly undone from either side.

Disabling the service does not hold

The advice that circulates most is to set the Windows Update service, wuauserv, to Disabled. It works until it does not.

Microsoft documents wuauserv, the Update Orchestrator Service UsoSvc, the Background Intelligent Transfer Service BITS and the Delivery Optimization service DoSvc. What it does not document, anywhere, is WaaSMedicSvc, the Windows Update Medic Service, which is the component that reverses the change. Searching Microsoft Learn for it returns community question threads and nothing else. There is no page describing what it does, when it runs, or how to stop it.

That absence is the argument. A method whose failure mode is undocumented cannot be tested, cannot be supported, and should not be standardized across a fleet. Microsoft's own position in the Windows Update FAQ is blunt: you cannot stop updates entirely, and they will eventually need to be installed regardless of your settings. If you need updates held, hold them with policy, where the behavior is written down.

One r/sysadmin thread runs that experiment all the way to the end. The OP stops wuauserv, UsoSvc, WaaSMedicSvc and DoSvc, kills each process, disables four UpdateOrchestrator and WaaSMedic scheduled tasks and sets NoAutoUpdate to 1, and Windows still installs updates during shutdown. The workaround the replies converge on is not to fight the service at all: point Windows Update at a WSUS server that does not exist.

How to permanently disable Windows Update, and why it won't stick

Not in a way Microsoft supports, as its FAQ above makes clear. What holds longest is policy, not the service. Setting Configure Automatic Updates to Disabled writes NoAutoUpdate = 1, covered in the registry section below, and the thread above lands on pointing devices at a WSUS address that doesn't exist.

Both stop security updates along with everything else, and both can cut off Defender's main signature route. Microsoft reserves the off option for systems under regulatory compliance. If the real need is a quiet month, a pause or a deferral gets you there without either cost.

Stopping Windows Update from the command line

The commands people search for stop the services for the current session only. From an elevated Command Prompt:

code
net stop wuauserv
net stop bits
net stop usosvc

That halts a download that's running right now. It doesn't survive a restart, and the same undocumented repair component brings the services back. Use it to get through a meeting, then pause properly.

Set-Service -Name DoSvc -StartupType Disabled targets something else. DoSvc is Delivery Optimization, the service that shares update files between PCs on your network and over the internet. Turning it off changes where updates download from, not whether they download. If peer sharing is the actual worry, Microsoft's Delivery Optimization reference gives the supported route: set Download Mode to 0 (HTTP only). Microsoft also warns against Bypass mode (100), which is deprecated in Windows 11 and can make some content fail to download.

Group Policy, and the tree that moved

The path still quoted widely is Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Automatic Updates. On current Windows 11 ADMX that is the old layout. There are now four subfolders under Windows Update:

SubfolderWhat lives there
Manage end user experienceConfigure Automatic Updates, active hours policies, metered download, removing access to Pause updates, notification and deadline settings
Manage updates offered from Windows UpdateSelect when Quality Updates are received, Select when Preview Builds and Feature Updates are received, Select the target Feature Update version, driver inclusion
Manage updates offered from Windows Server Update ServiceWSUS and intranet service settings
Legacy PoliciesAuto-restart timing, restart notifications, deferral scan behavior

Microsoft's own pages disagree about this, which is why the confusion persists. The Policy CSP reference, dated June 2026, gives the subfolder layout. "Manage additional Windows Update settings", dated February 2026, still prints the flat path. Both paths appear in the wild depending on the ADMX version in your central store, so look for the policy rather than the path. Windows 11 Home and Windows 10 Home don't include the Group Policy editor at all, so on those editions the Settings pause, active hours and a metered connection are what you have.

Configure Automatic Updates itself offers options 2, 3 and 4 on Windows 11 client: notify for download and auto install, auto download and notify for install, and auto download and schedule the install. Option 5 exists in the documentation but Microsoft states it is unavailable on Windows 10 and later, and option 7 is Windows Server 2016 and later only.

The numbers that mean two different things

This is the trap worth reading twice, because it produces the opposite of what you intended and it does so silently.

The same policy is expressed on two different integer scales. In the registry, under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU, the value AUOptions uses one scale. In the MDM and CSP world, AllowAutoUpdate uses another.

ValueRegistry AUOptionsCSP AllowAutoUpdate
0not listedNotify the user before downloading
1Keep my computer up to date is disabledAuto install, notify to schedule restart
2Notify of download and installationAuto install and restart (default)
3Automatically download and notify of installationAuto install and restart at a specified time
4Automatically download and scheduled installationAuto install and restart without end-user control
5Allow local admin to select the mode, unavailable on Windows 10 and laterTurn off automatic updates
7Notify for install and notify for restart, Windows Server 2016 and laternot listed

Read row five. Someone who finds AllowAutoUpdate = 5 in the CSP reference and writes AUOptions = 5 into the registry has not turned updates off. They have set a mode Microsoft says does not work on this operating system. Microsoft does not publish a cross-walk between these scales, so do not convert between them; take each from its own reference.

The straightforward registry switch in that same key is NoAutoUpdate, a REG_DWORD where 0 is enabled and 1 is disabled. Microsoft's warning on the CSP equivalent is worth passing on to whoever asked for updates off: that option is for systems under regulatory compliance, because you will not get security updates either.

Deferral across a fleet

Deferral is what the request usually means when someone says stop. It holds an update back for a defined window without breaking the mechanism, and the limits are firm.

Quality updates defer for a maximum of 30 days, via DeferQualityUpdatesPeriodInDays. Feature updates defer for up to 365 days on the General Availability Channel and 14 days on prerelease channels, via DeferFeatureUpdatesPeriodInDays. Both sit under HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate, and in Group Policy they are "Select when Quality Updates are received" and "Select when Preview Builds and Feature Updates are received".

Microsoft publishes a number here that is useful to quote in a patch SLA: to help ensure devices stay secure, configure quality update deferral to be less than three days.

Pausing by policy is also capped at 35 days, using PauseQualityUpdatesStartTime and PauseFeatureUpdatesStartTime, which take a string in yyyy-mm-dd form. Pausing feature updates does not pause quality updates; those keep being offered. In Intune the same controls appear as update rings, with a quality deferral range of 0 to 30 days, a feature deferral range of 0 to 365, and the same 35-day pause.

Two operational details from Microsoft's Intune documentation save trouble. A device that is switched off when you issue a pause may download and install a scheduled update when it powers on, before it checks in. And deleting an update ring does not revert anything: the device keeps the settings it already has, with no record of what it held before.

What a working ring config looks like is worth reading from someone running one. In this thread an admin describes a 14-day deferral on Windows servers with a separate 3-day ring for test and low-risk production boxes, weekly cadence, and one escaped issue in about seven years. Another admin in the same thread describes a validation ring with no test instance of the critical servers and no functional checks, shipping to production a week later regardless, which is the useful half: a ring is only worth the testing that happens inside it.

How to stop Windows Update on Windows Server 2016, 2019 and 2022

Windows Server doesn't give you the 35-day pause button that client Windows has. The control is SConfig, the Server Configuration tool, and Microsoft's SConfig documentation lays out three modes.

Open SConfig (it launches at sign-in on Server 2022 Core, and runs from SConfig.cmd on 2016 and 2019), choose option 5, then pick a letter. A installs updates automatically every day at 3:00 AM server time. D downloads updates and waits for you, and it's the default. M stops automatic checks completely, so nothing happens until an admin runs option 6.

For a fleet of servers, set the same thing by Group Policy with Configure Automatic Updates. Option 7, notify for install and notify for restart, exists for Windows Server 2016 and later and is the usual choice for servers you patch in a maintenance window.

Manual mode on a server is a decision to own patching yourself, so put the window in a calendar. Windows Server 2016 reaches the end of extended support on January 12, 2027, which means the monthly security updates you're holding are among the last it will get.

Turning off updates turns down Defender

This side effect changes the recommendation.

Microsoft Defender Antivirus does not have its own independent update channel by default. Microsoft states it plainly in an Important callout on the Defender update sources page: security intelligence updates and platform updates are delivered through Windows Update.

There is a fallback, and the timing is the problem. If the Microsoft Update source is the working one and you break it, the security intelligence page fallback only kicks in when the current update is considered out of date, which Microsoft defines as seven consecutive days of not being able to apply updates. Security intelligence normally refreshes several times a day. So the realistic outcome of disabling the service on an endpoint is up to a week of stale detection content on a machine whose owner believes only patching stopped.

Defender is independent only if you have explicitly configured the fallback order to include the security intelligence source, a file share or an internal definition server, and then verified it. That is a two-minute check with Set-MpPreference -SignatureFallbackOrder, and it is worth doing before you disable anything.

If the goal is Defender itself rather than updates, our guide to turning Defender off temporarily covers that separately, including how to get it back on.

How to confirm it took

Do not trust the Group Policy editor for pause state. Microsoft documents that GPEdit will not reflect an expired pause period: the device resumes after 35 days, and the checkbox stays ticked anyway.

Check the status keys instead, under HKLM\SOFTWARE\Microsoft\WindowsUpdate\UpdatePolicy\Settings. The values PausedQualityStatus and PausedFeatureStatus read 0 for not paused, 1 for paused, and 2 for automatically resumed after a pause. PausedQualityDate and PausedFeatureDate give the start date. That 2 is the one to look for when someone insists updates were held and the machine patched anyway.

Why won't Windows Update?

Sometimes the problem runs the other way: updates were held once, and now nothing installs. Before treating it as a fault, look for a hold left behind by one of the methods above.

Leftover holdWhere to look
A pause still runningPausedQualityStatus and PausedFeatureStatus under HKLM\SOFTWARE\Microsoft\WindowsUpdate\UpdatePolicy\Settings
A metered connectionSettings > Network & internet, then the connection's Metered connection switch
A disabled serviceThe wuauserv startup type in services.msc
Automatic updates off by policyNoAutoUpdate under HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
A long deferralDeferQualityUpdatesPeriodInDays and DeferFeatureUpdatesPeriodInDays under HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
A WSUS address that goes nowhereWUServer in that same key, and UseWUServer under its AU subkey

If none of those is set, it's a fault rather than a hold. Microsoft's update troubleshooting page starts with the Windows Update troubleshooter in the Get Help app, then clears the update cache: stop the Windows Update service, delete the contents of C:\Windows\SoftwareDistribution, and start the service again. It also asks for at least 20 GB free on a 64-bit system before an upgrade.

When the failure comes with an error code, look it up before resetting anything. Our error 0x80248007 guide walks through that cache reset step by step.

Should you stop Windows Update at all?

Usually the ticket is about the reboot rather than the patching, and active hours plus a deadline settles it without disabling anything.

Where it matters most right now is version support rather than monthly patching. Windows 11 24H2 Home and Pro reach end of servicing on October 14, 2026, which means a fleet sitting behind a long feature-update deferral is heading for unsupported machines rather than merely delayed ones. Deferral is a delay, not a block, and it does not extend a lifecycle.

The risk side comes with numbers. CISA's Known Exploited Vulnerabilities catalog, as of its September 16, 2026 release, carries 177 entries for Microsoft Windows products, and 49 of those are flagged as used in known ransomware campaigns. One entry added on September 8, 2026 is a privilege escalation in the Windows Update stack itself. Our guide to patch management software covers the tooling side of keeping that window short.

If ring-based deferral is where you land, this walkthrough builds the pilot, early adopter and production rings in Intune, with separate deferral periods for feature and quality updates and deadline policies for install and restart.

Which method fits which goal

If you wantUseHow long it holds
A quiet week or month on one PCPause updates in SettingsUp to 35 days
No restarts during working hoursActive hours plus a deadline policyAs long as the policy stays
Less data on a capped linkA metered connectionPartly: priority updates still download
A tested window across many machinesDeferral policy or update rings30 days for quality, 365 for feature updates
Automatic updates off on a compliance systemNoAutoUpdate = 1 by policyUntil you remove it, with no security updates

For an in-house team the request usually comes from one department with one deadline. For an MSP it changes client by client, so record each hold and its end date where the next technician will see it.

What to do next

Pause if you need a short, supported hold and you accept the 35-day ceiling. Use deferral policy if you need a repeatable window across machines, and keep quality deferral tight. Use active hours and deadlines if the complaint is about restarts.

If you are managing more than a handful of endpoints, do it from update rings rather than per-device settings, and confirm the result in the status keys rather than in the policy editor. Our endpoint management comparison covers the platforms that push this centrally. OpenFrame, Flamingo's open, AI-native infrastructure for IT and security, is one of them. It runs patch policies, remote access and a help desk for one company or many clients, at 1 dollar per device per month with a 14-day free trial.

And before you disable anything on any machine, your own or a client's, check where Defender is getting its signatures. That is the failure nobody reports as an update problem, because it does not look like one.

Aliaska Varieva

Aliaska Varieva

VP of Engineering

Hi! I’m Aliaska, and I’ve been working as a software engineer (mostly Java + a bit Kotlin) for over 8 years now. I mostly spend my time building backend services, integrating systems, fixing bugs (the fun part 🙃), and making sure things don’t fall apart behind the scenes.

Related Content

Frequently Asked Questions

/blog/how-to-stop-windows-update

Still deciding?

Ask Mingo answers from our docs and customer stories.

Loading related content and questions