Can't turn on Memory Integrity

empleat · Dec 26, 2022

It says there is incompatible driver, but when I click review incompatible drivers nothing shows. I also tried google and run some CMD command to show bad drivers and it didn't show anything... How do I find offending drivers?

Thank you!

neemobeer · Dec 26, 2022

The device guard hardware readiness tool should help with that. Download Device Guard and Credential Guard hardware readiness tool from Official Microsoft Download Center

empleat · Dec 26, 2022

It opens and instantly closes.

When I open PS 7.3.1 as admin and run this command in the folder:

Code:

DG_Readiness_Tool_v3.6.ps1 -capable -hvci

It says:

DG_Readiness_Tool_v3.6.ps1: The term 'DG_Readiness_Tool_v3.6.ps1' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Same this doesn't seem it will tell me about drivers, what is command for checking drivers?

I don't think this even helps with my problem:

Tool to check if your device is capable to run Device Guard and Credential Guard.

Seems like it is only for evaluation compatibility!

neemobeer · Dec 26, 2022

HVCI is basically what memory integrity is. You would need to run the following (assumpting you are running from the directory with the script)

Code:

. .\DG_Readiness_Tool_v3.6.ps1 -Capable -HVCI

This does enable driver verifier so you have to reboot and rerun the command.

It should dump results into C:\DGLogs\

empleat · Dec 26, 2022

Well I have no idea what is wrong, I don't recognize these drivers!

BTW these readme files are strange, what a strange command . .\ never seen that before... But it wasn't listed there...

neemobeer · Dec 27, 2022

It does list the incompatible driver at the bottom. Remove the Aomei software

empleat · Dec 28, 2022

Oh no I need that, OMG. Well I can try like Acronis, but ffs...

glasskuter · Dec 28, 2022

I suggest you remove using Revo Uninstaller free which removes all traces of software.

empleat · Dec 29, 2022

It wasn't the reason, I removed all residual drivers from Aomei and it still doesn't turn on! Unless you want from me to use Revo again, but it is 99% waste of time - I use install monitor, which monitors all changes during install and can remove all files really thoroughly (trust me)! It removed multiple drivers! I try to check, but i am pretty sure i saw this driver name before: "ambakdrv.sys". There is no driver like that left in Windows folder anymore, deleted!!!

PS: revo is useless couldn't find even drivers, i will try uninstall and make sure this driver is missing again to test it!

I deleted this driver by hand and it didn't work... There wasn't any other offending driver right?

empleat · Dec 30, 2022

It is strange that in Windows Settings it doesn't show any incompatible drivers.

Log also lists these:

Incompatible HVCI Kernel Driver Modules found

NX Protector is absent
SMM Mitigation is absent

empleat · Jan 1, 2023

Wait what NX Protector lead me to Windows Defender Credential Guard service not running, but that feature is only for Enterprise so it can't be that: Enable or Disable Credential Guard in Windows 11/10 by using Group Policy I Am pretty sure that HVCI is supposed to work on Pro, It works on my other computer on Windows 10!!! It also showed incompatible drivers, I deleted them and it worked, but not here... Is there anything else from that log, deleting that AOMEI driver in whole Windows folder - didn't work... And even complete uninstall of all drivers/files/registry of AOMEI... Google is also super unhelpful, found literally nothing all these keywords...

ALso it says:

Machine is not Device Guard / Credential Guard compatible because of the following:
OS SKU unsupported

Weird I upgraded from original Windows 10 Pro. I Am on latest 22H2, build: 22621.963

empleat · Jan 10, 2023

ANY IDEAS?

neves · Jan 10, 2023

Memory Integrity is virtualization based. Did you disabled Virtualization by any chance (be it from Windows or BIOS)?

Birk · Jan 10, 2023

I had the same problem. Here's what worked for me:

How to delete non-existent driver?

WIndows Security is showing me this: However, there is no such file c:\windows\system32\drivers. It is not shown by Autoruns. How can I find whatever it is and delete it? I'm running WIN64/Home latest build.

www.elevenforum.com

empleat · Jan 10, 2023

I don't have even any other drivers to delete, unless there are some other in that log ppl mised. In incopatible drivers it showed none, I had to use dgreadiness_v3.6 tool to even see what the issue is... But thanks!

glasskuter · Jan 11, 2023

empleat said:
Oh no I need that, OMG. Well I can try like Acronis, but ffs...

If, indeed, Aoemi is the problem and you don't like Acronis, you have other free and paid options-https://www.elevenforum.com/t/poll-on-backup-software.4622/page-21#post-220406
OR
You can uninstall Aoemi from your system and uses its recovery media to backup your system offline.
OR
Many people run with memory integrity turned off. It's no huge deal to have it off. It's just another layer of protection. Even with it on, you can still get infected. IMO, having backups available to save you is more important in the long run that memory integrity.

empleat · Jan 11, 2023

neves said:
Memory Integrity is virtualization based. Did you disabled Virtualization by any chance (be it from Windows or BIOS)?

It is enabled.

AOMEI doesn't seem to be a problem, i deleted AOMEI with install monitor which is powerful tool to get rid of all files (deleted several drivers) and i deleted on 2nd try manually driver which was showing to be offending in DGlog - didn't work!

Hmm I guess it is whatever...

I WOULD STILL LIKE THIS ON THO...

empleat · Feb 11, 2023

Geez this drives me crazy, it is not Aomei drivers as i uninstalled them with uninstaller which monitors installations and it is very thorough it uninstalled like 15 drivers! I also tried manually exact driver and same... THERE ARE MANY MORE ERRORS:

###########################################################################
Readiness Tool Version 3.4 Release.
Tool to check if your device is capable to run Device Guard and Credential Guard.
###########################################################################
###########################################################################
OS and Hardware requirements for enabling Device Guard and Credential Guard
1. OS SKUs: Available only on these OS Skus - Enterprise, Server, Education, Enterprise IoT, Pro, and Home
2. Hardware: Recent hardware that supports virtualization extension with SLAT
To learn more please visit: https://aka.ms/dgwhcr
###########################################################################

Checking if the device is DG/CG Capable
====================== Step 1 Driver Compat ======================
Driver verifier already enabled
Verifying each module please wait ....
Completed scan. List of Compatible Modules can be found at C:\DGLogs\DeviceGuardCheckLog.txt
Incompatible HVCI Kernel Driver Modules found

Module: ambakdrv.sys
Reason: execute pool type count: 6

====================== Step 2 Secure boot present ======================
Secure Boot is absent / not enabled.
If Secure Boot is supported on the system, enable Secure Boot in the BIOS and run the script again.
====================== Step 3 OS Architecture ======================
gwmi: E:\OLD disk D\Software\Windows\Downloads\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1:756
Line |
756 | $OSArch = $(gwmi win32_operatingsystem).OSArchitecture
| ~~~~
| The term 'gwmi' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the
| spelling of the name, or if a path was included, verify that the path is correct and try again.
InvalidOperation: E:\OLD disk D\Software\Windows\Downloads\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1:758
Line |
758 | if($OSArch.Contains("64-bit"))
| ~~~~~~~~~~~~~~~~~~~~~~~~~~
| You cannot call a method on a null-valued expression.
====================== Step 4 Supported OS SKU ======================
gwmi: E:\OLD disk D\Software\Windows\Downloads\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1:714
Line |
714 | $osname = $((gwmi win32_operatingsystem).Name).ToLower()
| ~~~~
| The term 'gwmi' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the
| spelling of the name, or if a path was included, verify that the path is correct and try again.
InvalidOperation: E:\OLD disk D\Software\Windows\Downloads\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1:714
Line |
714 | $osname = $((gwmi win32_operatingsystem).Name).ToLower()
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| You cannot call a method on a null-valued expression.
InvalidOperation: E:\OLD disk D\Software\Windows\Downloads\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1:721
Line |
721 | if($osname.ToString().Contains($SKUent.ToLower()))
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| You cannot call a method on a null-valued expression.
InvalidOperation: E:\OLD disk D\Software\Windows\Downloads\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1:721
Line |
721 | if($osname.ToString().Contains($SKUent.ToLower()))
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| You cannot call a method on a null-valued expression.
InvalidOperation: E:\OLD disk D\Software\Windows\Downloads\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1:721
Line |
721 | if($osname.ToString().Contains($SKUent.ToLower()))
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| You cannot call a method on a null-valued expression.
InvalidOperation: E:\OLD disk D\Software\Windows\Downloads\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1:721
Line |
721 | if($osname.ToString().Contains($SKUent.ToLower()))
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| You cannot call a method on a null-valued expression.
InvalidOperation: E:\OLD disk D\Software\Windows\Downloads\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1:721
Line |
721 | if($osname.ToString().Contains($SKUent.ToLower()))
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| You cannot call a method on a null-valued expression.
InvalidOperation: E:\OLD disk D\Software\Windows\Downloads\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1:721
Line |
721 | if($osname.ToString().Contains($SKUent.ToLower()))
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| You cannot call a method on a null-valued expression.
This PC edition is Unsupported for Device Guard
====================== Step 5 Virtualization Firmware ======================
gwmi: E:\OLD disk D\Software\Windows\Downloads\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1:794
Line |
794 | $_vmmExtension = $(gwmi -Class Win32_processor).VMMonitorModeExte …
| ~~~~
| The term 'gwmi' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the
| spelling of the name, or if a path was included, verify that the path is correct and try again.
gwmi: E:\OLD disk D\Software\Windows\Downloads\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1:795
Line |
795 | $_vmFirmwareExtension = $(gwmi -Class Win32_processor).Virtualiza …
| ~~~~
| The term 'gwmi' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the
| spelling of the name, or if a path was included, verify that the path is correct and try again.
Virtualization firmware check passed
====================== Step 6 NX Protector ======================
NX Protector is absent
====================== Step 7 SMM Mitigation ======================
SMM Mitigation is absent
====================== End Check ======================
====================== Summary ======================
Machine is not Device Guard / Credential Guard compatible because of the following:
Secure boot validation failed.
OS SKU unsupported

Incompatible HVCI Kernel Driver Modules found
NX Protector is absent
SMM Mitigation is absent

RJARRRPCGP · Feb 11, 2023

A bunch of errors that look like a typo.

empleat · Feb 12, 2023

Not really (how could typo be commnand's output?), look at these for instance:

NX Protector is absent
====================== Step 7 SMM Mitigation ======================
SMM Mitigation is absent
====================== End Check ======================
====================== Summary ======================
Machine is not Device Guard / Credential Guard compatible because of the following:
Secure boot validation failed.
OS SKU unsupported