Enabling Windows 11 22H2 Core Isolation Memory Integrity feature using Intune

-

In Windows 10 and 11, the operating system can provide protection from malicious code by isolating certain processes in the PC’s memory using virtualization on supported hardware. This protection runs under Memory Integrity under Core Isolation feature. With Windows 11 22H2, Microsoft made this feature default. However, as of writing this post, Memory Integrity will only turn on new devices by default. For existing devices upgrading to Windows 11 22H2, the feature will need to be managed separately.

Memory integrity is also known as Hypervisor-protected Code Integrity (HVCI). Being a device guard feature, it hasn't made to the dedicated security profiles under Endpoint Security Attack Surface Rules in Intune as a standalone policy. Official documentation by Microsoft suggests that it can be enabled as part of Applocker Code Integrity CSP. 


Alternatively, one can also enable it through the Applocker policy in Application control ASR, if you want to enable Applocker policy as a whole.


If you do use the CSP or the built-in App locker application control policy, then be prepared for the additional forced reboot needed for enabling the feature.


If you don't want to enable Applocker, just like me, and only want to enable HVCI feature, then luckily there is another option. Follow the steps below to enable it -

2. Browse to Devices – Windows – Configuration Profiles
3. Click Create Profile
4. Select Platform as Windows 10 and later
5. Select Profile as Settings catalog
6. Provide a Name and hit next.
7. Click on Add settings.
8. Search and select for 'Hypervisor Enforced Code Integrity' as shown below.


Following values are available -

Disabled (0) - Turns off Hypervisor-Protected Code Integrity remotely if configured previously without UEFI Lock
Enabled with UEFI lock (1) - Turns on Hypervisor-Protected Code Integrity with UEFI lock
Enabled without UEFI lock (2) - Turns on Hypervisor-Protected Code Integrity without UEFI lock.

9. Set it to the desired value. (I am setting it to Enabled with UEFI lock)
10. Assign to your device or user based group.

End Result

For the setting to apply, the device must be rebooted once. After the reboot, Memory Integrity feature will turn on.




Compliance in Intune should get updated and report successful.

Comments

  1. AnonymousJanuary 3, 2023 at 3:00 PM

    Wonderful article, thank you so much, love the rigidity approach instead of turning ON some massive constellation of settings and watching everything go nuts... Thank you

    ReplyDelete
  2. All type of Crack Software are available here.January 12, 2023 at 9:49 AM

    Nice post! This is a very nice blog that I will definitively come beck to moretimes this year! thanks for the informative post Download.
    Windows 10 Manager
    Apeaksoft Video Converter Ultimate Crack
    PDF Shaper Professional
    FonePaw Android Data Recovery
    ZD Soft Screen Recorder

    ReplyDelete
  3. DaveJanuary 24, 2023 at 12:38 PM

    Hey following this guide my test machine is getting error 65000 in intune , its latest Windows 11 build ? Any ideas ?

    ReplyDelete
  4. AnonymousJanuary 24, 2023 at 12:41 PM

    followed this but getting error code 65000 in intune ? any ideas?

    ReplyDelete
  5. AnonymousMarch 23, 2023 at 4:26 PM

    Thanks so much for the information! Tried searching everywhere for this since the students at our school need memory integrity disabled in order for their test taking software to work and even ChatGPT was no help haha

    ReplyDelete
  6. GwayERP softwareApril 13, 2023 at 6:34 AM

    Thank you for sharing this fantastic article with us, and please continue to offer high-quality content like this one.
    outsourcing software development company

    ReplyDelete
  7. AnonymousApril 18, 2023 at 9:48 AM

    note: intune setting is only applicable for Windows 11 and does not affect windows 10

    ReplyDelete
  8. Adam in DCJuly 20, 2023 at 8:03 PM

    I'm getting the 65000 as well for my workstation running 21H2. I'm switching from a user based group to a device based group and we'll see if that makes an improvement.

    ReplyDelete
  9. Albert EinsteinOctober 17, 2023 at 8:52 AM

    Good Work.Keep it Up.

    PDF Shaper Professional Crack

    Goodhertz All Plugins Bundle Crack

    LastPass Password Manager Crack

    Zemana AntiLogger Crack

    ReplyDelete
  10. Waseem MalikNovember 5, 2023 at 1:19 AM

    I like your all post. You have done really good work. Thank you for the information you provide, it helped me a lot.I hope to have many more entries or so from you.
    Very interesting blog.
    Software house03
    ZD Screen Recorder Crack
    MiniTool Partition Wizard Crack
    bandicam Crack

    ReplyDelete
  11. Albert EinsteinApril 3, 2024 at 7:05 AM

    Good Work.Keep it Up.

    Windows 11 Activator

    FonePaw Screen Recorder

    Fitness Manager

    ReplyDelete

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){                 $KPID=$KP.KeyProtectorId                 break;             }         }        $o
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $Path1
Read more

Intune: UAC Elevation Prompt Behavior for Standard Users

-
Image
Implementing and maintaining a good security posture is an integral part of overall IT security governance for most organizations now. While you want to harden the security of infrastructure and give least number of privileges to your end users, sometimes you may need to cut back on the restrictions to ensure a good user experience and an effective IT support process. Recently, I had a requirement where the customer wanted to ease the restriction on the end user devices to make the helpdesk support process more efficient. This involved easing the UAC level access for the Standard users and if you are managing your devices using Intune, then this blog may just help you. Let us see what all is involved and some of the ways that you can use to implement this easily. Policy CSP – LocalPoliciesSecurityOptions LocalPoliciesSecurityOptions has many CSP settings and if you are managing these settings at an individual level, then the CSP that we need to concern ourselves with here is U
Read more