Windows 10: Driver can't load. Core integrity....

Does anyone know ab quick and easy work around so as to use the driver I need for a program. I don't want to disable the core integrity. I just want to unblock a simple driver.

:)

 

Core Isolation preventing a driver from loading

The driver "gdvr3.sys" was causing core isolation to turn off. After turning it back on and restarting, get the message that Core Isolation has blocked the driver from loading. However, it is not showing up under problems when I look under core isolation details. Not sure what next steps need to be.

 

Core Isolation / Memory Integrity Issues

Hi Matthias Heier,

Welcome to Microsoft Community.

I can understand your confusion.

Memory integrity is designed to protect important core processes in Windows.

Memory integrity works by creating an isolated environment using hardware virtualization.





Based on the information you provided, Og software has a real impact on the memory integrity of Windows.

OG software still exists, incompatible drivers are still in the system and can be scanned.

Operations on memory integrity imply changes to the virtualization underlay, and any changes to the memory integrity state can create unexpected problems, such as the blue screen you encounter, until the incompatible driver is removed.

If you want to enable core isolation, we recommend that you remove the incompatible driver first.

You can refer to the steps below to remove the incompatible driver.

• Personally, it is recommended to operate in safe mode.
  
  Start your PC in safe mode in Windows - Microsoft Support
  
• Click Settings >> Privacy & Security >> Windows Security, Select Device Security.
  
  Select Core isolation details.Check if there is a "View incompatible drivers" option.
  
• If so, click to view details and expand incompatible drivers to get the Published name.
  
• When you get the Published name for incompatible drivers. Please following the steps below.
  

1. Type Device Manager, find and run it.
   
2. Click View tab, change to Devices by driver.
   
3. Find the corresponding driver according to the Published name and delete it.
   

If there is anything not clear, please do not hesitate to let me know.



Best Regards,



| Microsoft Community Support Specialist

 

Windows Security - Core Isolation - Memory Integrity - No incompatible drivers found

I own a Dell XPS 13 9300, with all latest updates of Windows 11 and drivers through Dell's SupportAssist software installed, as of May 26th, 2023. I've noticed an alert icon on Windows Security a couple days ago and it says my Memory Integrity was disabled due to incompatible drivers, and it was specifically pointing out a smart card reader related to digital signing certificates called "AlcGener.sys - Giesecke & Devrient GmbH".

Let's get the obvious out of the way:

• Windows is updated to its latest version
  
• Ran winget /upgrade --all to get the latest version of all software installed (nothing related to the driver issue or the programs that use the device was shown)
  
• Already used windows update and dell software to look for updated drivers
  
• No issues are shown in device manager, all drivers seem to be working fine
  
• Virtualization and Hypervisor are enabled
  
• I use this machine with WSL2 enabled
  

I've looked it up and multiple answers in videos and help forums such as this one stated I should delete it in order to enable the core isolation again (yes, it was working before). So multiple sources helped identify the offending driver using:

It was not possible to delete the driver at first, so they recommended using "/uninstall /force" with the command as well. This did seem to work. Unfortunately, despite the driver no longer existing on my system, I still got the Memory Integrity alert.

When I ran the scan verifying driver compatibility, it stated there is an issue, and recommended fixing driver incompatibility issues before being able to enable the Memory Integrity, only this time, when I wen to check on driver incompatibility, nothing was shown, no drivers whatsoever.





I figured I've done something wrong so I set to uninstall all related programs that were supposed to use the smart card digital signing certificate thing, restarted the computer, ran Windows Update and Dell SupportAssist once again (nothing was added nor installed), and still the Memory Integrity status says there are driver incompatibility issues that need resolving.

I've been looking for this for a couple days now and could not find anything on this particular case, when there is no info on the offender driver show by Windows Security. Just so you know I already covered the basics, here are some of the links I've already went through:

• On Microsoft Community
  
  • Memory Integrity turned itself off due to incompatible drivers. - Microsoft Community
    
  • Memory Integrity: Core Isolation Error - Microsoft Community
    
  • Cannot enable Core Isolation in Windows 11 due to incompatible drivers - Microsoft Community
    
  • Core Isolation (Memory Integrity) disabled due to incompatible driver - Microsoft Community
    
  • Core isolation can't be activated because of incompatible driver - Microsoft Community
    
  • Drives incompatíveis - Isolamento de Núcleo - integridade da memória - Microsoft Community
    
  • A integridade da memória está desativada. Seu dispositivo pode estar - Microsoft Community
    
  • Why do incompatible drivers prevent using Memory integrity? - Microsoft Support
    
• On YouTube:
  
  • 
    
  • 
    
  • 
    
• Other Websites:
  
  • Core Isolation Failed- Incompatible Driver - Microsoft Community
    
  • Core isolation can't be activated because of incompatible driver called AlcGener.sys How... (****)
    
  • AlcGener.sys: What Is This Smart Card Reader Driver and What Is It For? – Maison da Silva
    
  • How to Enable Core Isolation to resolve “Kernel-mode Hardware-enforced Stack Protection is off – Maison da Silva
    
• On the driver itself:
  
  • Giesecke & Devrient GmbH StarSign CUT - Should I Remove It?
    

I know I shouldn't have forced removing the driver in the first place, but given I already put this much effort on solving this, I would appreciate any help on figuring out and solving this issue on my computer.