You can turn off Windows Defender's real-time protection in about four clicks: open Windows Security, go to Virus & threat protection, click Manage settings, and flip Real-time protection to Off. That switch is temporary by design — Windows 11 automatically flips it back on after a restart or after a short idle period. For a longer pause you need the Local Group Policy Editor or a registry change under Windows Defender policies. This guide walks through each method, the exact on-screen names, and the failure cases that trip people up, including tamper protection blocking the switch.
What "Temporarily" Actually Means in Windows Security
The Real-time protection toggle is the only genuinely temporary off switch Microsoft exposes in the consumer interface, and its behavior is defined by Windows Security's own state management. Microsoft's documentation for Windows Security describes the toggle as turning off scanning of files and programs as they run, and it restores itself when the system restarts or when the setting is re-applied by policy. That self-restoring behavior is why the toggle rarely survives a reboot.
Windows 11 and Windows 10 differ in how aggressively that reset happens. On Windows 11, the Settings app and Windows Security app share state through the Security Center service, and toggling real-time protection off from Windows Security triggers a warning banner that stays visible until you re-enable. On Windows 10, the same toggle exists, but the Settings app's "Windows Security" page sometimes shows a stale On/Off status until you refresh — a known cosmetic mismatch, not a failure.
The word "temporarily" also carries a legal boundary. Microsoft's licensing terms for Windows and its Defender antivirus component don't permit disabling protection as a permanent configuration on systems you don't own or administer, and enterprise environments often enforce it through Intune or Group Policy so the toggle is greyed out entirely. If you see "This setting is managed by your administrator," the switch is locked and no consumer method in this article will override it.
Keep the distinction clear: this article covers the consumer protection component in Windows Security, not the separate firewall, SmartScreen, or Microsoft Defender for Endpoint cloud service. Each has its own controls, and disabling real-time protection leaves the firewall running.
The 4-Click Toggle: Fastest Way to Pause Real-Time Scanning
This is the method most readers want, and it works identically on Windows 10 version 1903 and later and every Windows 11 release through 24H2. Use it when you need to install or run something Defender is flagging, and plan to turn it back on within the same session.
1: Press the Windows key, type Windows Security, and press Enter. The shield icon appears in the taskbar tray; clicking that icon opens the same app. 2: Select Virus & threat protection in the left navigation pane. 3: Under Virus & threat protection settings, click Manage settings. 4: Find the Real-time protection row and move the toggle to Off. Accept the User Account Control prompt if one appears.
The toggle shows "Off" immediately, and the Virus & threat protection page displays a red warning stating real-time protection is off. Microsoft's Windows Security help pages confirm the setting resets after a restart; in practice on Windows 11 23H2 and 24H2, the toggle often turns itself back on after a period of inactivity too, so don't leave a machine unattended expecting protection to stay paused.
Failure handling matters here. If the toggle is greyed out with "This setting is managed by your administrator," check whether your device is joined to a work or school account — a common cause on managed laptops. If tamper protection is On, the toggle may appear active but snap back to On when clicked; that's documented behavior, covered below. If the toggle moves to Off but Windows Security closes and reopens with it On, a third-party antivirus is likely registered and Defender has already stepped back.
When the Toggle Won't Stay Off: Tamper Protection and the Real Failure Case
Tamper protection is the single most common reason the Real-time protection toggle refuses to stick, and Microsoft enabled it by default on consumer Windows 10 and Windows 11 starting in 2021 through a Defender update. The feature prevents malware and unauthorized tools from changing Defender settings, and Microsoft's own documentation states that tamper protection blocks changes made through registry edits and PowerShell commands, even when you're signed in as an administrator.
To check the current state, open Windows Security > Virus & threat protection > Manage settings and look for the Tamper Protection row. If it reads On, the Real-time protection toggle still works through the standard UI — Microsoft allows that path — but registry and PowerShell methods will fight you. Turning tamper protection off is itself a separate switch on the same page, and it can take up to a few minutes to register before policy edits apply.
Here's the edge case most guides skip: on some Windows 11 builds, disabling real-time protection while a scheduled scan is running causes the scan to terminate with error 0x800705B4 (timeout), and the toggle reverts to On without explanation. Cancel any running scan from Protection history or wait for the scheduled scan to finish before toggling. Similarly, if Windows Update is mid-install, the toggle can flip back as the Defender platform updates and re-registers the security provider.
If tamper protection is On and you genuinely need a policy-level pause, disable tamper protection first, make the change, then re-enable it. Microsoft's support article on tamper protection notes that turning it off requires administrator approval and leaves the device less protected in the interim, so do the work in one sitting.
Using Local Group Policy Editor for a Controlled Pause
The Local Group Policy Editor gives you a longer, restart-defying pause and is the method administrators use. It's available on Windows 11 Pro, Enterprise, and Education, and on Windows 10 Pro, Enterprise, and Education — Windows Home lacks gpedit.msc entirely, so Home users should skip to the registry method. The policy in question is Turn off Microsoft Defender Antivirus, located under Computer Configuration.
1: Press Windows + R, type gpedit.msc, and press Enter. Accept the UAC prompt. 2: Navigate to Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus. 3: Double-click Turn off Microsoft Defender Antivirus. 4: Select Enabled, click Apply, then OK. 5: Restart the PC. The policy takes effect after a reboot, not immediately.
When this policy is Enabled, Windows Security's real-time protection toggle disappears or greys out and Defender stops scanning. Turning it back on means returning to the same policy, selecting Not Configured (not Disabled — Not Configured restores default behavior cleanly), and rebooting again. According to Microsoft's Defender documentation, this policy also stops the Antimalware Service Executable from performing real-time protection, though scheduled scans and definition updates may continue depending on the "Allow antimalware service to start up with the computer" policy state.
One failure case: if you enable the policy and then try to open Windows Security, the app may display "Your virus and threat protection is managed by your organization" and provide no toggle. That's expected. To reverse it, run gpupdate /force in an elevated Command Prompt instead of rebooting, which applies the Not Configured state within roughly a minute on most systems.
Windows Home users who want the same effect can't install gpedit.msc without editing system files, which is a separate workaround outside this scope. Use the registry method below instead.
The Registry Method and Its Windows 11 24H2 Hangup
The registry approach sets the same policy flag directly at HKLM\SOFTWARE\Policies\Microsoft\Windows Defender, where the DWORD value DisableAntiSpyware set to 1 disables Defender. Microsoft's Defender documentation warns this key is honored only when tamper protection is off and Group Policy isn't otherwise locking the setting, and starting with Windows 10 version 2004 and Windows 11, Microsoft stopped honoring DisableAntiSpyware on consumer editions in many configurations — a version-specific difference that breaks older tutorials still circulating online.
1: Press Windows + R, type regedit, and press Enter. Approve the UAC prompt. 2: Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender. If the Windows Defender key doesn't exist, create it via right-click New > Key. 3: Right-click in the right pane, choose New > DWORD (32-bit) Value, name it DisableAntiSpyware. 4: Double-click the value, set the data to 1, and click OK. 5: Restart the PC, then confirm in Windows Security that real-time protection shows Off.
On Windows 11 24H2, you may find the key exists with value 1 and Defender still runs — Microsoft's documentation confirms the setting is ignored on some builds where the Defender platform detects tamper protection or where the antimalware service has already registered. In that case the policy path via gpedit.msc is the only reliable consumer route, which is why 24H2 users on Home edition have no clean temporary-off method beyond the toggle.
To reverse it, set DisableAntiSpyware to 0, or delete the value entirely, then reboot. Deleting the whole Windows Defender policy key is safe and restores defaults, though any other policies you set under it will be lost.
Removing a Third-Party Antivirus Conflict Before You Start
A third-party antivirus like Norton, McAfee, or Bitdefender changes the picture entirely, because Windows automatically disables Defender's real-time protection when it detects another registered antivirus. The Windows Security interface then shows "Microsoft Defender Antivirus is turned off" with a note that another antivirus is handling protection. According to Microsoft's documentation on antivirus coexistence, Defender enters passive mode rather than being switched off, and the toggle isn't available.
If you're trying to disable Defender because a third-party tool asked you to, check Windows Security > Virus & threat protection for the provider name under "Who's protecting me?" first. Uninstalling the third-party antivirus through Settings > Apps > Installed apps re-enables Defender automatically within a few minutes; there's no need to touch the toggle.
The conflict failure case: installing two real-time antivirus engines simultaneously is what Microsoft calls "not recommended" in its coexistence documentation, and doing so on Windows 11 can cause both engines to quarantine the same file, producing repeated notifications and, in rare cases, a boot-time scan loop. Remove one before testing the other.
Registry-level force-disabling Defender while a third-party engine is registered can produce a state where Windows Security shows no active provider at all — a red "no protection" condition. Restore it by re-enabling Defender via the policy Not Configured state and rebooting, or reinstalling the third-party tool.
How Long a Pause Lasts and What Resets It
The reset behavior differs by method, and knowing the trigger saves you from re-doing steps. The Real-time protection toggle resets on restart, on sign-out and sign-in in some builds, and after Windows Security detects a policy refresh. The gpedit.msc policy survives restarts until you change it back to Not Configured. The registry value persists until tamper protection or a Defender platform update overrides it on builds where it's ignored.
Microsoft's Windows Security documentation doesn't publish a fixed timer for the toggle, but observed behavior on Windows 11 22H2 and later shows it flipping back within roughly 15 to 60 minutes of idle time on some systems, and immediately on a restart on all systems. That variability is why enterprise admins rely on policy rather than the toggle.
| Method | Survives restart? | Needs admin? | Works on Windows Home? | Tamper protection blocks it? |
|---|---|---|---|---|
| Real-time protection toggle | No | Yes (UAC) | Yes | No, UI path allowed |
| Local Group Policy Editor | Yes | Yes | No, gpedit.msc absent | Indirectly, via locked settings |
| Registry DisableAntiSpyware | Sometimes | Yes | Yes | Yes on supported builds |
| Third-party AV coexistence | Until AV removed | Yes | Yes | Not applicable |
The table's key column is the third one: Home edition users have exactly two viable routes, the toggle and the registry, and the registry route is unreliable on 24H2. That's not a limitation Microsoft documents prominently, but it follows from the gpedit.msc absence and the DisableAntiSpyware deprecation.
Set a reminder before you pause protection. A 10-minute window is enough for a driver install or a flagged installer; a multi-hour window with no antivirus is a risk most home users shouldn't take.
What Stays On When Real-Time Protection Goes Off
Turning off real-time protection doesn't turn off everything, and knowing what remains active changes how much risk you're actually taking. Cloud-delivered protection, automatic sample submission, the firewall, SmartScreen in Edge, and controlled folder access each have separate toggles under the same Manage settings page. Microsoft's Windows Security documentation lists these as independent controls, and the firewall in particular stays fully active.
Scheduled scans also remain active under the toggle-off state on most builds, though they may run with reduced capability. Definition updates continue downloading through Windows Update, which means Defender's signatures stay current even while real-time scanning is paused — a detail many guides miss.
The practical consequence: if you disable real-time protection specifically to run a file Defender flagged, the file can execute, but SmartScreen may still block it if it's downloaded from the internet, and controlled folder access may still prevent it from writing to Documents. Disable those too only if you understand the tradeoff, and re-enable them first.
Windows Firewall is the one component you should never disable alongside real-time protection. It's a separate page in Windows Security, and Microsoft's firewall documentation notes that disabling it exposes listening services to inbound traffic regardless of antivirus state.
Re-Enabling Protection and Verifying It Took Effect
Re-enabling is faster than disabling if you follow the reverse path exactly. For the toggle, return to Windows Security > Virus & threat protection > Manage settings and switch Real-time protection to On; the red warning clears within a few seconds. For the policy, set Turn off Microsoft Defender Antivirus to Not Configured and run gpupdate /force, then reboot. For the registry, set DisableAntiSpyware to 0 or delete the value and restart.
Verify with three checks. First, the Virus & threat protection page should show a green check and "No actions needed." Second, open Task Manager > Details and confirm MsMpEng.exe (Antimalware Service Executable) is running with meaningful CPU usage when you open a folder of files. Third, run a Quick scan from the same page — if it completes without an error code, the engine is active.
If the toggle won't return to On, tamper protection may be off and a policy still forcing the disabled state. Re-enable tamper protection from Manage settings after restoring Defender, and check gpresult /h report.html in an elevated Command Prompt to see which policy is applying.
A common verification failure: the Windows Security app caches state, so a green check can lag reality by a minute or two. Closing and reopening the app forces a refresh through the Security Center service.
FAQ
Does disabling real-time protection turn off Windows Defender completely?
No — the toggle stops on-access scanning only. Cloud-delivered protection, the firewall, SmartScreen, and scheduled scans each have separate switches, and definition updates keep downloading through Windows Update even while real-time protection is off.
Why does my Real-time protection switch flip back to On by itself?
Tamper protection or a policy refresh is the usual cause. On managed devices, an Intune or Group Policy setting reapplies the On state within minutes; on personal devices, Windows 11's Security Center service re-enables the toggle after a restart or idle period of roughly 15 to 60 minutes.
Is DisableAntiSpyware still working in Windows 11 24H2?
Microsoft stopped honoring the DisableAntiSpyware registry value on many consumer configurations starting with Windows 10 version 2004, and the limitation carries into Windows 11 24H2. On those builds the value can read 1 while Defender keeps scanning, so use the Local Group Policy Editor route or the UI toggle instead.
Can I disable Windows Defender on Windows Home without gpedit.msc?
Yes, but only two routes exist: the Real-time protection toggle in Windows Security and the registry DisableAntiSpyware value. The registry route is unreliable on Windows 11 24H2 Home, which leaves the toggle as the dependable option — and it resets on every restart.
Does turning off real-time protection leave my firewall running?
The firewall stays fully active. Windows Firewall is a separate component under Privacy & security > Windows Security > Firewall & network protection, and Microsoft's documentation treats it independently of antivirus state, so disabling Defender's scanning doesn't open inbound ports.
How long is it safe to run with real-time protection off?
There's no Microsoft-published safe duration, but the practical window for a driver install or flagged installer is minutes, not hours. Leaving a machine with real-time protection off overnight removes on-access scanning entirely, and any file that executes in that window is unchecked by Defender.
Will disabling Defender break Windows Update?
No — Windows Update and Defender definition updates run through separate services. Disabling real-time protection can, however, cause Windows Update to re-enable Defender as part of a platform update, which is one reason the toggle reverts on some systems after updates install.
What happens if I uninstall my third-party antivirus while Defender is disabled?
Windows detects the missing registered antivirus and re-enables Defender's real-time protection within a few minutes, but if Defender was force-disabled by policy or registry, the system can enter a "no active provider" state. Set the policy back to Not Configured and reboot to restore protection.