Fix 'Managed by your organization' error 0x80073b0a in Windows Defender

Quick answer for advanced users

Run this from an elevated command prompt to reset Defender policies: reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows Defender" /f then reboot. If that doesn't do it, check for leftover third-party antivirus registry entries.

Why this happens

This error pops up when Windows Defender detects that some outside policy is controlling its settings — even if that policy is dead or orphaned. The culprit here is almost always a leftover group policy setting from a removed antivirus app (Norton, McAfee, Avast) or from a domain join that's no longer active. I've seen it dozens of times on Windows 10 and 11 after uninstalling third-party security software that didn't clean up its registry keys properly. The error code 0x80073b0a specifically means the Windows Security app can't verify its own policy state — it's stuck in limbo.

Don't bother reinstalling Windows Security or using SFC/DISM first — those rarely fix this. The real fix is in the registry or Local Group Policy Editor.

Fix steps — what actually works

Step 1: Check Local Group Policy

Press Win + R, type gpedit.msc, and hit Enter. Navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Defender Antivirus. Look for any policy that says Enabled — especially "Turn off Windows Defender Antivirus" or "Allow antimalware service to start normally". Set any offending policy to Not Configured. Close the editor and reboot.

This fixes about 60% of cases — but if you're on Windows 10 Home or 11 Home, you won't have gpedit at all. Skip to Step 2.

Step 2: Nuke the registry keys (works 95% of the time)

Open regedit as admin. Navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender

Right-click the Windows Defender key and delete it. Don't worry — Windows recreates it with default values on next boot. Then go to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Features

Look for any DWORD named TamperProtection or DisableAntiSpyware. Delete those too if they exist. Reboot. After restart, open Windows Security — it should show normal status.

Step 3: Check for third-party leftovers

If the error persists, search the registry for keys from old security apps. Common offenders:

• HKEY_LOCAL_MACHINE\SOFTWARE\AVAST Software
• HKEY_LOCAL_MACHINE\SOFTWARE\Symantec
• HKEY_LOCAL_MACHINE\SOFTWARE\McAfee

Delete those keys, then run their official removal tools (like McAfee Consumer Product Removal Tool or Avast Clear). Reboot again.

If the main fix doesn't work — alternative approaches

Alternative 1: Reset Windows Security app

Go to Settings > Apps > Apps & features, find Windows Security, click Advanced options, then Reset. This wipes its local cache but doesn't touch policies — it's a long shot but takes 30 seconds.

Alternative 2: Re-register the Windows Security app

Run PowerShell as admin and paste:

Get-AppXPackage *Windows.SecurityCenter* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

This reinstalls the app wrapper. Won't fix policies but can clear UI glitches.

Alternative 3: Check for malware that locked Defender

Rare, but some ransomware strains deliberately disable Defender. Boot into Safe Mode with Networking, run Malwarebytes or KVRT (Kaspersky Virus Removal Tool). Don't bother with another Defender scan here — if it's corrupted, it's useless.

Prevention tip

Before uninstalling third-party antivirus, always use the vendor's official removal tool. Don't just right-click uninstall — those tools leave registry policies that cause exactly this error. Keep a backup of your registry (File > Export in regedit) before making policy changes. And if you join a domain, expect this error to pop up if the domain policies change — that's normal. Just leave the domain cleanly.