Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

License Error 0x800106BA

Microsoft Defender real-time protection will not turn on: what 0x800106BA really is

12 min read Updated October 5, 2026 Antivirus & Endpoint Security

Fix it now

0x800106BA and 0x800106B5 are legacy Windows Defender initialisation errors from the Vista, 7 and 8 era, filed by Microsoft under previous Windows versions. On Windows 10 and 11 the same symptom shows up as Defender being in disabled mode because another antivirus is registered, or as event 3002 in Defender’s own log.

Run in an elevated PowerShell window. AMRunningMode is the field that answers the question

Get-MpComputerStatus | Select-Object AMRunningMode,AMServiceEnabled,RealTimeProtectionEnabled,IsTamperProtected,AntivirusSignatureLastUpdated
  1. Open Windows Security, then Settings, then Manage providers, and read which product Windows currently treats as your antivirus.
  2. If a product you already uninstalled still appears there, run its vendor’s removal tool and restart. A leftover registration alone keeps Defender out of the way.
  3. Read AMRunningMode from the command above. Normal means Defender is doing the work; anything else means it has stood down.
  4. Open the Defender operational log – Applications and Services Logs, Microsoft, Windows, Windows Defender, Operational – and look for event 3002, which records real-time protection failing with an error code and a reason.
  5. Open services.msc and confirm Microsoft Defender Antivirus Service is running, along with the Security Center service that tracks registered products.
  6. If the machine is managed, produce a policy report with gpresult /h %userprofile%\Desktop\gp.html and check whether a policy is turning Defender off.

Do not search for 0x800106BA and follow what you find. Most of that advice tells you to re-register DLLs and start a service that has not existed since Windows 8.

If Defender reports real-time protection on and it survives a restart, you are done. If not, the next section explains why Windows turns it off deliberately.

Why it happens

Start with the code, because it is the reason this problem is so badly served. 0x800106BA and 0x800106B5 are Windows Defender anti-spyware initialisation errors from Windows Vista, 7 and 8, and Microsoft’s material on them sits under previous Windows versions. They are not documented Microsoft Defender Antivirus codes on Windows 10 or 11. Keep them as a search term if that is how you found this page, but do not treat them as a current diagnostic – the remedies attached to them, re-registering DLLs and starting the old Windows Defender service, describe a product that no longer exists in that form.

On current Windows the same symptom has a documented explanation, and it is usually not a fault. Microsoft states that on Windows 10 and Windows 11, when a non-Microsoft antivirus solution is installed and registers itself, Microsoft Defender Antivirus goes into disabled mode automatically. That is the designed behaviour, and no amount of clicking the real-time protection toggle overrides it while another product holds the registration.

Passive mode is a different state and it is worth not confusing the two. Microsoft documents passive mode as what happens where a device is onboarded to Microsoft Defender for Endpoint alongside a non-Microsoft antivirus. There is one further case: on Windows 11 with Smart App Control enabled, Defender may go into passive mode rather than remaining disabled, and Microsoft is explicit that this is not the same passive mode as on an onboarded device.

Windows Server behaves differently again, and getting this wrong costs people real coverage. On Windows Server, Microsoft Defender Antivirus is not disabled automatically when a non-Microsoft antivirus is installed – it has to be disabled or uninstalled deliberately. A server running two engines because nobody did that is a genuine problem, and it is the opposite of the client case.

The remaining codes are ordinary. 0x80070005 is access denied: the change was refused rather than failing technically, which is what to expect when something other than Windows Security alters a tamper-protected setting. Event 5007 records a configuration value changing. Event 3002 is the one that reports an actual failure, naming the feature, the error code and the reason.

Another antivirus holds the registration

You have this one if Manage providers names a non-Microsoft product, and Defender describes itself as turned off.

  1. Decide which product you want doing real-time work; running both is not the goal on a client.
  2. If you are keeping the third-party product, leave Defender alone. Disabled mode is documented behaviour here, not a fault.
  3. If you want Defender back, uninstall the other product from Settings, Apps, then run its vendor’s removal tool to clear the registration.
  4. Restart and check Manage providers again before touching any Defender setting.

A removed product left its registration behind

You have this one if Manage providers lists something that no longer exists in Installed apps, or a product whose subscription lapsed months ago.

  1. Get the removal tool from that vendor’s own support pages; an ordinary uninstall frequently leaves the registration in place.
  2. Run it, restart, and check Manage providers again.
  3. Confirm Defender now reports itself as the active provider in Windows Security.
  4. Run Get-MpComputerStatus and confirm AMRunningMode reads Normal and real-time protection is enabled.

This is the single most common way a machine ends up with no working real-time protection at all: one product gone, the other standing aside for a registration that outlived it.

Real-time protection is failing at runtime

You have this one if Event 3002 in the Defender operational log, naming a feature and an error code.

  1. Read the Feature field in the event. It names which part failed – on-access, behaviour monitoring, or the network inspection system.
  2. Read the Error Code and Reason fields, which carry the actual HRESULT and why the feature was restarted.
  3. Run sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth in an elevated Command Prompt, and restart.
  4. Collect the Defender logs with "%ProgramFiles%\Windows Defender\MpCmdRun.exe" -GetFiles before opening a support case.

A policy is switching Defender off

You have this one if Defender is the only registered product, real-time protection refuses to stay on, and the interface shows settings as managed.

  1. Produce a policy report with gpresult /h %userprofile%\Desktop\gp.html and look at the Defender antivirus policies.
  2. On a managed machine, change it in the management console rather than locally; local edits are overwritten at the next refresh.
  3. On an unmanaged machine, check HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender for values left by tuning scripts or a previous suite.
  4. Restart and confirm the setting holds.

Where tamper protection is on, changes to tamper-protected settings made through Group Policy are ignored, so a policy that looks like it should be winning may not be.

The change is being refused rather than failing

You have this one if 0x80070005 when you try to alter a setting, and Windows Security itself works normally.

  1. Confirm you are working from an administrator account.
  2. Make the change in Windows Security rather than by script or registry edit.
  3. Check whether tamper protection is on with Get-MpComputerStatus; if it is, that is the refusal.
  4. If the machine is managed, the change belongs in the management console.

Full reference

What state Defender is actually in

Situation Documented Microsoft Defender Antivirus state
Windows 10 or 11, no other antivirus Active
Windows 10 or 11, a non-Microsoft antivirus installed, not onboarded to Defender for Endpoint Disabled, automatically
Windows 11 with Smart App Control enabled and a non-Microsoft antivirus May be passive rather than disabled, and this is not the same as passive mode on an onboarded device
Onboarded to Defender for Endpoint with a non-Microsoft antivirus Passive, automatically
Windows Server with a non-Microsoft antivirus Not disabled automatically; it must be disabled or uninstalled deliberately

Reading your row off that table before doing anything is the single highest-value step in this article. Three of the five are working as designed, and in two of them the correct action is to change nothing.

The fields worth reading in Get-MpComputerStatus

Field What it answers
AMRunningMode Which state Defender is in. Normal means it is doing the work
AMServiceEnabled Whether the antimalware service is enabled at all
RealTimeProtectionEnabled Whether the real-time layer is on
IsTamperProtected Whether tamper protection is refusing changes
AntivirusSignatureLastUpdated Whether anything is keeping the definitions current

Reading event 3002 properly

Event 3002 is the current equivalent of what people go looking for when they search the legacy codes. Microsoft publishes it as MALWAREPROTECTION_RTP_FEATURE_FAILURE – real-time protection encountered an error and failed – and it carries four useful fields: the Feature that failed, the Error Code as a standard HRESULT, the Error Description, and the Reason Defender restarted the feature. That gives you a specific HRESULT to work on rather than a fifteen-year-old code with no current meaning.

The legacy codes, and what to do with them

  • Treat 0x800106BA and 0x800106B5 as search terms, not diagnostics.
  • Ignore advice to start a service called Windows Defender; on current Windows the service is Microsoft Defender Antivirus Service.
  • Ignore advice to re-register DLLs such as wuapi.dll. That was a remedy for a different product on a different operating system.
  • If you are genuinely on Windows 7 or 8, that operating system is out of support and the antivirus question is the smaller of your problems.
  • On Windows 10 or 11, replace the code with the state: read Manage providers and AMRunningMode, and work from there.

A machine with no real-time protection at all

  1. Open Windows Security, Settings, Manage providers and list what Windows believes is installed.
  2. For each entry, establish whether the product is actually present and licensed.
  3. Remove any that is not, using that vendor’s removal tool rather than Settings.
  4. Restart and re-check. Defender should take the position back once nothing else claims it.
  5. Confirm with Get-MpComputerStatus that AMRunningMode reads Normal, real-time protection is enabled, and the signature date is current.

Servers are the exception worth writing down

Because Windows Server does not disable Defender automatically, a server with a third-party agent installed can end up running two real-time engines against the same file operations, with the performance cost and the occasional mutual-detection comedy that implies. Microsoft’s position is that it must be disabled or uninstalled deliberately. If you manage servers, that is a checklist item rather than something to discover during an incident.

When a licence is the actual fix

There are two coherent positions here and one that is not. Run Microsoft Defender alone, which is included with Windows and costs nothing. Or run a licensed non-Microsoft suite and let Defender go into disabled mode, which is what these symptoms usually describe. What you must not do is leave an expired or half-removed product holding the registration while nothing protects the machine, which is the state a surprising number of these end up in. If you want the third-party suite, Arco supplies Bitdefender Total Security and can check how many devices your licence needs to cover. If you would rather not pay for one, remove the old product cleanly with its vendor’s tool and let Defender take the position back – that costs nothing and we will say so.

Every code this article covers

Code What it points at Source
0x800106BA A legacy Windows Defender initialisation error from the Windows Vista, 7 and 8 era, filed under previous Windows versions. It is not a documented Microsoft Defender Antivirus code on Windows 10 or 11 Microsoft (legacy documentation)
0x800106B5 The same legacy family and era as 0x800106BA. On current Windows the equivalent condition surfaces as disabled mode or as event 3002 Microsoft (legacy documentation)
0x80070005 Win32 error 5, ERROR_ACCESS_DENIED: access is denied. The change was refused rather than failing technically Microsoft Learn
Event ID 5007 MALWAREPROTECTION_CONFIG_CHANGED: the antimalware platform configuration changed, carrying the old and new values. It is an audit record, not an error Microsoft Learn
Event ID 3002 MALWAREPROTECTION_RTP_FEATURE_FAILURE: real-time protection encountered an error and failed. The event names the feature, the error code, the description and the reason Microsoft Learn

Confirm the fix worked

  1. Windows Security, Manage providers shows one active antivirus provider, and it is the one you intend.
  2. Get-MpComputerStatus reports AMRunningMode as Normal and real-time protection as enabled, if Defender is the product you chose.
  3. The setting survives a full restart rather than reverting at logon.
  4. No new event 3002 entries appear in the Defender operational log.
  5. The signature date is current, which is the proof that whichever product is in charge is actually working.

Questions people ask about this

Is 0x800106BA still a real Defender error?

Not on Windows 10 or 11. It is a legacy Windows Defender initialisation error from the Vista, 7 and 8 era, and Microsoft files it under previous Windows versions. Use it to find this page, then diagnose from Manage providers, AMRunningMode and event 3002 instead.

Is Defender being off actually a problem?

Only if nothing else is on. If a current non-Microsoft antivirus holds the registration and is updating, the machine is protected and Defender being in disabled mode is documented behaviour. If the registered product has expired or been removed, nothing is protecting the machine.

What is the difference between passive and disabled mode?

Microsoft documents disabled mode as what happens automatically on Windows client when a non-Microsoft antivirus is installed. Passive mode applies where the device is onboarded to Defender for Endpoint. On Windows 11 with Smart App Control enabled Defender may go passive instead, and Microsoft states that is not the same as passive mode on an onboarded device.

Does this work the same way on Windows Server?

No, and this is the one to remember. On Windows Server, Microsoft Defender Antivirus is not disabled automatically when a non-Microsoft antivirus is installed; it has to be disabled or uninstalled deliberately.

Do I need to buy anything to turn Defender back on?

No. Defender is part of Windows. The work here is removing whatever is holding it back, and that costs nothing. A licence only enters the picture if you decide you want a third-party suite instead.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error ESET error ACT.11: this licence is already used on the maximum devices License Error Norton says your subscription has expired: error 3035 1 and 1002 3 explained License Error Avast subscription expired: fixing activation errors 0xE001D025 and 0xE001D024 License Error Bitdefender update error -1002 and -1022: the client cannot reach the update servers
โ† Back to Knowledge Base