See elsewhere in this thread why the registry hack is not a good idea.
Windows 11 will not show incompatible drivers
In new windows 11 up to date as of writing this. Core isolation memory integrity does not work and will not turn on. Every time I scan for incompatible drivers, none are listed. Checked the windows update, the system is up to date, and no errors in device drivers were found. All drivers appear up to date. BIOS most recent available (the same driver that was installed prior to this error occurring. None of the threads seem to address this, only ones where the driver is known. The DG readiness tool is not user-friendly for everyday users. Need a solution that can be done at home without having to be an IT guru or MSCE certified. It will not let me upload the screenshot or picture, keep getting errors in that as well.
Windows for home | Windows 11 | Devices and drivers
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
164 answers
Sort by: Oldest
-
Anonymous
2024-10-04T07:44:36+00:00 -
Anonymous
2024-10-04T08:00:36+00:00 HST222 left a long list of security problems from using that HypervisorEnforcedCodeIntegrity hack.
read HST222's post here.
You might need to manually go to page 11 and HST222 "Replied on September 10, 2024"
then decide if you REALLY want to do that HypervisorEnforcedCodeIntegrity hack.
-
Anonymous
2024-10-04T08:01:21+00:00 Be careful, those instructions pointing to hvciscan_amd64
https://answers.microsoft.com/en-us/windows/forum/all/check-incompatible-device-system-drivers-for-hvci/d5bd48a6-0953-4dae-85dc-334bddd24e5a do not discuss the vulnerability associated with this tool and Microsoft's intention to deprecate this tool as I mentioned in a post 10 mins ago.
-
Anonymous
2024-10-04T08:15:27+00:00 Hi Harry,
BING found many links to the HVCIscan module.
I found a Sophos article
Microsoft Patch Tuesday: 74 CVEs plus 2 “Exploit Detected” advisories – Sophos NewsIt basically said it's an incomplete EXE that shouldn't have been certified by Microsoft. But the author said no other details from Microsoft on WHAT vulnerabilities exist. I'm thinking it was "marked" as vulnerable for the stated reasons.
I can't see it as creating genuine immediate or ongoing vulnerabilities unless
a) is stayed running in memory after use and after rebootor
b) the Microsoft.com download was hackedor
c) some malware was already stealth-installed and just waiting for me to execute that obscure tool.
Seeing as it only ran for 2 minutes in a command window, then stopped, it was never installed, therefore, I can't think of a way it would cause ongoing problems. I'm far from a security expert.
THANK you for getting into the weeds.
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more