Blog Post

Windows IT Pro Blog
2 MIN READ

Expanding memory integrity protection across Windows devices

Peter_Waxman's avatar
Peter_Waxman
Icon for Microsoft rankMicrosoft
Sep 01, 2026

Security works best when protection is built in, not bolted on.

Beginning in October 2026, Microsoft will expand memory integrity protection across eligible devices, helping you and your organization benefit from stronger kernel-level protection from sophisticated attacks by default with little or no additional configuration. This change reduces security complexity while helping you establish a stronger security baseline across your environment.

Built on Virtualization-based Security (VBS), memory integrity helps protect critical parts of Windows from tampering. It forms a foundation for modern security innovations such as hotpatch updates that improve user experience and productivity, as well as protection.

Making advanced security the easier choice

More devices will soon receive stronger protection by default, with no additional setup required. Windows quality updates will begin enabling memory integrity protection on eligible devices. If not already enabled, these updates will also enable VBS, helping make additional security capabilities available and reflecting our commitment to making Windows secure by design and secure by default.

To help ensure a reliable device experience, Windows automatically evaluates readiness before enabling memory integrity. Readiness signals include hardware capabilities, compatibility, and performance considerations. For more detail on requirements, see our Memory integrity and VBS enablement documentation.

Recommended by Microsoft, controlled by you

Windows provides a recommended security baseline, while respecting organizational choice. While most eligible devices will benefit automatically from memory integrity protection, you retain full control over your security configuration. Existing administrator and user decisions and policies remain in effect. This means that devices where memory integrity has already been disabled won't be automatically changed by this rollout.

If memory integrity is not enabled by default, users and organizations can still review, configure, and enable it using existing Windows security and management tools. For step-by-step guidance, see Enable memory integrity.

Stronger protection today, a foundation for tomorrow

By expanding memory integrity protection across eligible Windows devices, Microsoft is helping you establish a stronger security foundation, reduce configuration burden, and prepare for the next generation of Windows security innovations. Soon, more devices will be protected against attacks that attempt to compromise the Windows kernel and gain control of critical operating system functions. Memory integrity helps make this possible by allowing only trusted kernel-mode code and drivers to run. More protection. Less complexity. A stronger foundation for what's next.

For more information on memory integrity, see:

 


Securing today. Preparing for what's next.
Learn more in the Windows Security book and Windows Server Security book. To stay up to date on the latest in security features and enhancements, visit the Microsoft Security site, follow the Microsoft Security Blog, or connect with Microsoft Security on LinkedIn and @MSFTSecurity.

Updated Aug 31, 2026
Version 1.0

5 Comments

  • lalanc01's avatar
    lalanc01
    Iron Contributor

    Hi, great addition, but I'm not so sure about the controls that we have.
    If a device doesn't have memory integrity enabled and no enterprise policies are applied for that setting, will it be auto enabled after the October update?

    And if that's the case, if we want to control the rollout, we must set an enterprise policy to disable it and create rings that enable it?

    Also if a device is imaged with OSD and we don't have any enterprise policy for this setting, when will it get enabled? Asking because for device encryption it's when a corporate user logs onto the device.

    Thks in advance.

    • Peter_Waxman's avatar
      Peter_Waxman
      Icon for Microsoft rankMicrosoft

      If Memory Integrity is not already configured and no enterprise policy applies, an eligible device may be enabled after it receives the applicable Windows update and is staged rollout assignment, passes the required eligibility and compatibility checks, and restarts. If your organization wants to control the rollout you can apply an explicit disable policy to managed devices and then use deployment rings to change that policy to enabled for each approved group. Enterprise policy takes precedence over the automatic enablement.

       

      For newly imaged devices without a policy, Memory Integrity may be enabled during the out-of-box experience (OOBE) if the device is eligible. This process is not tied to user sign-in.

  • wroot's avatar
    wroot
    Silver Contributor

    How does it compare/stack up with Credential Guard.

    • Peter_Waxman's avatar
      Peter_Waxman
      Icon for Microsoft rankMicrosoft

      Both memory integrity and Credential Guard depend on Virtualization-based Security that provides the underlying isolated environment needed by both.  However they are independent security capabilities that provide different protections. Memory integrity uses VBS to ensure that only code which satisfies Windows kernel code-integrity policy is permitted to be executed in the kernel and prevents the validated kernel code from being modifiable. Credential Guard meanwhile is a feature that uses VBS to isolate enterprise credentials such as NTLM password hashes or Kerberos Ticket Granting Tickets (TGTs) so that any possible malicious code running in the user or kernel mode in Windows cannot access or leak these credentials. They are both important security capabilities that work independently of each other. 

  • coakl's avatar
    coakl
    Copper Contributor

    When I turned this on, Task Manager showed an item named 'System' eating up 4,096 MB of memory.  That's on an i7-11700 with 32 GB memory, Win 11 Home 25H2.  Given what's going with A.I. jacking up memory prices, you shouldn't roll out memory-eaters like this one, as a default setting.  Especially in a bad economy with high inflation and increasing layoffs.  People have to live in tough times like today, and make do with older devices.