Search results

I mean if there is a possible undisclosed CVE 0 day in your driver code they should be letting you know so you can resolve it sooner rather than later. Sounds like they are using other means to plug an API they have not yet patched

Yeah that is a known fix highlighted at the start of the thread, the main issues is that, microsoft have created an AV feature (Core Isolation) that does not provide the ability for an end user to add trusted and signed code (in this case a software driver that monitors critical hardware...

@Martin and everyone this can be upvoted here in the Windows Insider feedback hub https://aka.ms/AAhgopy

Still broken in Windows 11 insider Dev build 25158

Also still broken in this week's Windows 11 insider Dev build 25151

I guess this only highlights that the driver is in serious need of repair, if you are able to modify and sign code that is not from the vendor to bypass HVCI protection then it just exposes another hole that Microsoft will need to plug

This is indeed sad, and I hope they work out how to open things up via APIs or provide vendors with a way to get WHQL signing for drivers like this. Windows defender is very primitive compared to other enterprise Core Isolation AV software where we can add rules to allow signed code.

I'm experiencing the same issue after updating to the latest Windows 11 dev insider build 25145 today. Core isolation was on previously. For me the app will not launch at all. I just get the Can't install driver error.