Skip to content
TroubleGrid

Windows says Microsoft Defender Antivirus is turned off when it isn't

Last verified November 2026Tested against Windows 11 26H1, Windows 11 25H2, Windows 11 24H2, Windows 11 23H2, Windows 10 22H2, Windows 10 21H2, Windows Server 2012 through 2025, Microsoft Defender Antivirus platform 4.18.26070.9 (5 August 2026) through 4.18.26080.3 (affected), Microsoft Defender Antivirus platform 4.18.26080.4, released 17 September 2026 (carries the fix), Microsoft Defender Antivirus platform 4.18.26090.9, released 12 October 2026, Microsoft Defender Antivirus platform 4.18.26100.4, released 27 October 2026 (current)Well documented

Microsoft resolved this on 17 September 2026, in Microsoft Defender Antivirus platform version 4.18.26080.4. Let Defender update itself, then check that Get-MpComputerStatus reports AMProductVersion as 4.18.26080.4 or later - as of 17 November 2026 the newest platform is still 4.18.26100.4, so a PC that updates normally is well past the fix. Until it reaches your PC the warning is cosmetic, but prove that before ignoring it: if AntivirusEnabled, RealTimeProtectionEnabled and AMServiceEnabled all read True, Defender is running and you are looking at the bug.

The reason this one is worth two minutes rather than zero is that a disabled Defender is also what malware leaves behind, so "just ignore it" was bad advice even while the bug was unfixed. The check is quick and it distinguishes the two cases cleanly. Note the shape of the bug: the alert appeared at startup and at random afterwards, it kept appearing even after you turned Windows Security notifications off, and every settings page continued to show protection as on. It rode in on a Defender platform update rather than a Windows cumulative update, which is why it landed on Windows 10, Windows 11 and Windows Server at the same time — and why the fix arrives the same way.

Symptoms

  • A notification saying "Microsoft Defender Antivirus is turned off" or prompting you to turn on virus protection
  • It appears when Windows starts and then intermittently
  • It keeps appearing after you disable Windows Security notifications
  • Windows Security itself shows real-time protection as on with no threats
  • Manual scans and definition updates work normally
  • It started on a machine with no third-party antivirus installed

Why this happens

The notification came from Defender's reporting, not from Defender stopping

Microsoft's release-health entry lists the originating Windows update as N/A and describes the alert appearing after installing Microsoft Defender Antivirus platform update 4.18.26070.9, released 5 August 2026, while the antivirus is functioning correctly and all settings show it as active. Because it rode on Defender's own updates rather than a Windows cumulative update, it turned up across Windows 10, Windows 11 and Windows Server at the same time, and uninstalling a Windows update would not clear it. Microsoft named platform 4.18.26080.4, released 17 September 2026, as the version that fixes it, and marked the known-issue entry Resolved on 30 September 2026.

Update Defender to platform 4.18.26080.4 or later · Prove Defender is actually running, and read your platform version

It was in the wild for two months before it was acknowledged

Reports go back to June 2026 in the Release Preview channel and to 25 July 2026 on Microsoft Q&A, where three people described the same behaviour on both preview and normal builds and the page records 30+ others as having the same question. Microsoft opened the known issue on 28 August and a moderator restated on 13 September that it was cosmetic. If you have been seeing this for weeks and could not find anything about it, that gap is why.

Prove Defender is actually running, and read your platform version · Update Defender to platform 4.18.26080.4 or later

Fixes

Prove Defender is actually running, and read your platform version

about 3 min

This separates the known bug from a genuinely disabled antivirus, which is the only distinction that matters here — and the same command tells you whether you already have the fixed version.

Applies to: Windows 10, Windows 11, Windows Server 2012 and later

  1. Right-click Start and open Terminal (Admin) or Windows PowerShell (Admin).
  2. Run this and read the values.
    Get-MpComputerStatus | Select-Object AntivirusEnabled, RealTimeProtectionEnabled, AMServiceEnabled, AMRunningMode, AMProductVersion, AntivirusSignatureLastUpdated
  3. If AntivirusEnabled, RealTimeProtectionEnabled and AMServiceEnabled are all True, Defender is running and the notification is the known bug. AntivirusSignatureLastUpdated should be recent, which confirms it is still getting definitions.
  4. AMProductVersion is your Defender platform version. 4.18.26080.4 or later is the build Microsoft says fixes the false alert; 4.18.26070.9 through 4.18.26080.3 are the builds Microsoft ties to the bug.
  5. If any of the three values is False, this article does not apply and you have a real problem. Open Windows Security and read what Virus & threat protection actually says, and check whether another antivirus product has taken over.
  6. As a second opinion, press Windows key + R, run services.msc, and confirm Microsoft Defender Antivirus Service (WinDefend) is Running.
    services.msc

Confirmed by the vendor.

Source: Microsoft, Microsoft Q&A, Microsoft

Update Defender to platform 4.18.26080.4 or later

about 10 min

This is the actual fix. It ships as a Defender platform update rather than through Windows Update's monthly cumulative cycle, so it arrives on its own schedule.

Applies to: Windows 10, Windows 11, Windows Server 2012 and later

  1. Open Windows Security, go to Virus & threat protection, and under Virus & threat protection updates click Check for updates.
  2. Alternatively force an update from an administrator Terminal.
    & "$env:ProgramFiles\Windows Defender\MpCmdRun.exe" -SignatureUpdate
  3. Restart the PC, then re-run the Get-MpComputerStatus check above and read AMProductVersion.
  4. Once AMProductVersion is 4.18.26080.4 or later, the false notification should stop. Microsoft published that version on 17 September 2026 as the resolution, and its Defender platform release notes now list it and name this fix explicitly.
  5. If AMProductVersion is still 4.18.26080.3, the update has not reached your machine yet. Platform updates roll out gradually; leave the PC on and connected and check again in a day or two. The alert remains cosmetic in the meantime.
  6. Any platform newer than 4.18.26080.4 also carries the fix, so you do not need that exact version. As of 17 November 2026 the newest release is still 4.18.26100.4, dated 27 October 2026; anything at or above 4.18.26080.4 is past the fix.

Confirmed by the vendor.

Source: Microsoft, Microsoft, Microsoft, BleepingComputer

Reset the Windows Security app

Check before applyingabout 10 min

Suggested by Microsoft staff on their own Q&A thread, for the case where the alert outlives the fixed platform version. It clears the app's local state, which is where the incorrect status is displayed.

Applies to: Windows 10, Windows 11

Before you do this

Resetting an app clears its stored settings. Any notification preferences, exclusions set through the app, or controlled folder access choices you made there may need to be set again. Do not turn off Tamper Protection while you do this.

  1. Only do this if AMProductVersion already reads 4.18.26080.4 or later and the alert has not stopped. Otherwise wait for the update instead.
  2. Open Settings, go to Apps, then Installed apps.
  3. Find Windows Security, open the three-dot menu, and choose Advanced options.
  4. Click Repair first. If the alert persists, come back and click Reset.
  5. Restart the PC, then re-run the Get-MpComputerStatus check from the first fix to confirm protection is still on.

Reported to work by one user; not confirmed by the vendor.

Source: Microsoft Q&A

Known issues

  • Incorrect notifications that Microsoft Defender Antivirus is turned off. Opened 28 August 2026; marked Resolved on 30 September 2026, though the fix itself shipped earlier, in Defender platform 4.18.26080.4 of 17 September 2026. The entry now sits on Microsoft's resolved-issues page, which names Defender platform 4.18.26070.9 of 5 August 2026 as the update after which the notifications appear. Microsoft states the antivirus remained active throughout.

    Affects Windows 11 26H1, Windows 11 25H2, Windows 11 24H2, Windows 11 23H2, Windows 10 22H2, Windows 10 21H2, Windows Server 2012 through 2025, Defender platform 4.18.26070.9 through 4.18.26080.3 · Status: fixed

  • The two Microsoft pages now agree, re-checked 11 October 2026. Through late September the Defender platform release notes still showed 4.18.26080.3 as the newest release and did not list 4.18.26080.4 at all, while the release-health dashboard named it as the fix. That gap has closed: the notes now list Platform 4.18.26080.4 (17 September 2026) as the most recent release, and its changelog names this bug directly.

    Affects Defender platform 4.18.26080.3, Defender platform 4.18.26080.4 · Status: fixed

  • Still no independent confirmation that 4.18.26080.4 stops the alert, re-checked 17 November 2026 - two months on. The evidence remains vendor-only: the Microsoft Q&A thread has not moved since 14 September 2026 and names no Defender platform version, and the BleepingComputer report of the fix relays Microsoft's dashboard rather than testing it; none of its four reader comments mentions 4.18.26080.4 or says whether the alerts stopped.

    Affects Defender platform 4.18.26080.4 · Status: unknown

  • Two newer Defender platforms have shipped since the fix, and neither mentions this issue (re-checked 17 November 2026, no newer release since): 4.18.26090.9 on 12 October 2026 and 4.18.26100.4 on 27 October 2026. That is the expected pattern once a bug is resolved, and it means the fix attribution stays with 4.18.26080.4 rather than moving to a later release.

    Affects Microsoft Defender Antivirus platform 4.18.26100.4 · Status: fixed

If none of this worked

If Get-MpComputerStatus reports False for any of the three values, Defender really is off and this article is not your answer. The common innocent reason is a third-party antivirus, which Windows lets take over while Defender steps back. The one that matters is malware, which disables real-time protection and Tamper Protection to stay hidden. Check Windows Security > Virus & threat protection > Manage settings and confirm Tamper Protection is on. If it is off and you did not turn it off, treat the machine as compromised and scan it with the Microsoft Defender Offline scan before doing anything else. A Group Policy or registry setting such as DisableAntiSpyware will also genuinely turn Defender off on managed machines, which is a question for whoever manages the PC rather than a fault to fix yourself.

Common questions

Is my PC unprotected while this alert is showing?
Not if Get-MpComputerStatus reports AntivirusEnabled, RealTimeProtectionEnabled and AMServiceEnabled as True. Microsoft's own advisory stated the antivirus remains active and functioning correctly despite the notification, and a Microsoft Q&A moderator called it purely cosmetic on 13 September 2026.
How do I know whether I have the fixed version?
Run Get-MpComputerStatus and read AMProductVersion. That is the Defender Antivirus platform version. Microsoft says 4.18.26080.4, released 17 September 2026, carries the fix, and its Defender platform release notes now list that version and name this fix in its changelog; 4.18.26070.9 through 4.18.26080.3 are the builds Microsoft ties to the bug. Do not confuse it with the security intelligence version, which changes several times a day and is not what Microsoft credited with the fix - one reader who thought a signature update had cured it reported the warning returning afterwards.
Why can't I turn the notification off?
Microsoft documents that these notifications persist even when notification settings are turned off. That is part of the bug, not something you have configured wrong. The fix is the updated Defender platform, not a notification setting.
Should I install a different antivirus because of this?
No. Installing a second antivirus to silence a false alert leaves you with a real change to your security setup for a problem that is cosmetic and now fixed.
Will uninstalling a Windows update fix it?
No. Microsoft lists the originating update as N/A, which means it came with a Defender Antivirus update rather than a Windows cumulative update. Removing a Windows update will not touch it, and removing a security update to chase a cosmetic alert is a bad trade.
Defender says my platform is 4.18.26090.9, not 4.18.26080.4. Am I still affected?
No - a higher version is what you want. 4.18.26080.4 of 17 September 2026 is the release that carries the fix, and Microsoft has since shipped platform 4.18.26090.9, dated 12 October 2026, which is newer and therefore includes it. Any version at or above 4.18.26080.4 is past the bug, which is why the check is "4.18.26080.4 or later" rather than that exact number.

Did this fix work?

If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.

Report a problem with this page

Related problems

Sources

  • Microsoft · Support page · checked Nov 17, 2026

    • Microsoft opened the known issue "Incorrect notifications that 'Microsoft Defender Antivirus is turned off'" on 28 August 2026 at 15:34 PT and marked it Resolved on 30 September 2026 at 16:42 PT
    • As of 17 November 2026 the entry is listed on the resolved-issues page; it no longer appears on the Windows 11 25H2 status page
    • The notifications might appear after installing Microsoft Defender Antivirus update version 4.18.26070.9, released 5 August 2026, even though the antivirus is functioning correctly and all settings show it as active
    • Microsoft states the issue was resolved in the Microsoft Defender Antivirus update version 4.18.26080.4, released on 17 September 2026
    • The notifications can appear when Windows starts and intermittently afterward, and persist even if notification settings are turned off
    • The issue could be observed in any version of Windows or Windows Server with Microsoft Defender Antivirus running the latest Defender updates
    • Affected platforms include Windows 11 26H1, 25H2, 24H2 and 23H2, Windows 10 22H2 and 21H2, Windows 10 Enterprise LTSC 2019 and 2016, and Windows Server 2012 through 2025
    • The originating update field is N/A, so the notification was not tied to a specific Windows cumulative update
  • Microsoft · Documentation · checked Nov 17, 2026

    • Platform 4.18.26080.4 with Engine 1.1.26080.3 is listed under the heading "Windows Antivirus | August 2026-2"
    • Re-checked 20 October 2026: 4.18.26080.4 is no longer the newest release. The page now lists Windows Antivirus Platform 4.18.26090.9 with Engine 1.1.26090.9, dated 12 October 2026, above it under the heading "Windows Antivirus | September 2026".
    • The enhancements list for Platform 4.18.26090.9 does not mention the false "turned off" notification, so the fix remains attributed to 4.18.26080.4.
    • Its release-details table dates Platform 4.18.26080.4 to September 17, 2026, and Platform 4.18.26080.3 to September 1, 2026
    • Its Enhancements and features list for that release states: "Fixed an issue where Windows could incorrectly display a notification stating that 'Microsoft Defender Antivirus is turned off' when Windows started or intermittently afterward, even though Defender Antivirus remained active and functioning correctly."
    • That entry links to the Windows release-health known issue for the false notification
    • Defender Antivirus platform and engine versions are released separately from Windows cumulative updates
    • Re-checked 4 November 2026: a newer release has shipped. The page now lists Platform 4.18.26100.4 with Engine 1.1.26100.4, dated 27 October 2026, as the newest Windows Antivirus release. Its Enhancements list does not mention the false "turned off" notification, so the fix stays attributed to Platform 4.18.26080.4 of 17 September 2026.
    • Re-checked 17 November 2026: no newer Windows Antivirus release; Platform 4.18.26100.4 (27 October 2026) is still the newest, and the 4.18.26080.4 changelog still names the false "turned off" notification fix. The release-details table dates Platform 4.18.26070.9 to August 5, 2026.
  • Microsoft · Documentation · checked Nov 17, 2026

    • Get-MpComputerStatus gets the status of antimalware software installed on the computer
    • Its output includes AntivirusEnabled, RealTimeProtectionEnabled, AMServiceEnabled, AMRunningMode, AMProductVersion, AMEngineVersion, AMServiceVersion, AntispywareEnabled, BehaviorMonitorEnabled and AntivirusSignatureLastUpdated
    • AMProductVersion, alongside AMEngineVersion and AMServiceVersion, is among the version fields the cmdlet reports
  • BleepingComputer · News · checked Nov 17, 2026

    • Published 31 August 2026
    • The false notifications affected users in the Windows Insider Release Preview Channel since June 2026, months before Microsoft acknowledged them in late August
    • Microsoft advised users to disregard the alerts because the antivirus is functioning correctly
    • The erroneous alerts appear in the Windows Security app and prompt users to "Tap or click to turn on Microsoft Defender Antivirus"
    • The top reader comment reports the warnings stopped after installing Defender version 1.457.423.0, and a follow-up comment from the same user reports the warning returned
    • Comments on the page now carry relative timestamps rather than dates
    • Re-checked 17 November 2026: unchanged. The reader comment reporting the warning gone after Defender 1.457.423.0 is still followed by the same user reporting it returned the next day, so it remains evidence of nothing either way. No editor's update has been added.
  • BleepingComputer · News · checked Nov 17, 2026

    • Published 18 September 2026 by Sergiu Gatlan
    • Microsoft Defender Antivirus update version 4.18.26080.4 was released on 17 September 2026 and resolves the false "turned off" notifications
    • The issue affected all supported Windows client and server versions, including Windows 11 26H1 and Windows Server 2025
    • The report relays Microsoft's release-health dashboard statement rather than independently verifying that the notifications stop
    • Re-checked 17 November 2026: still explicitly second-hand, relaying Microsoft's release-health dashboard statement. Its four reader comments do not mention 4.18.26080.4 or report whether the notifications stopped after the fix.
  • Microsoft Q&A · Forum · checked Nov 17, 2026

    • Three distinct users describe the notification in the thread: the question of 25 July 2026 and answers of 14 and 16 August 2026, before Microsoft acknowledged it
    • The page records 30+ other people as having the same question
    • Reporters describe all protection toggles enabled, antivirus updates working and manual scans running normally while the warning keeps appearing
    • It is reported on both Release Preview builds (25H2 26200.8968) and on the normal August 2026 build 26200.9168
    • Alex-L, a Microsoft external staff moderator, recommended on 26 July 2026 running Get-MpComputerStatus and checking AntivirusEnabled, RealTimeProtectionEnabled and AMServiceEnabled
    • The same post recommended confirming Microsoft Defender Antivirus Service (WinDefend) is running in services.msc, and resetting the Windows Security app from Settings > Apps > Installed apps > Windows Security > Advanced options > Reset
    • A volunteer moderator stated on 13 September 2026 that this is a known issue and is purely cosmetic
    • As of 11 October 2026 the latest post is dated 14 September 2026 and no post names a Defender platform version that stopped the alerts
    • Re-checked 17 November 2026: the thread has not moved. The latest post is still Johnny55's of 14 September 2026, and no post in it names a Defender platform version that stopped the alerts. Johnny55 says only that Microsoft is working on a fix for an upcoming Defender update, naming no version.