Having troubles after update Windows 11 yesterday

As an update to this - I was having this issue after the update. it has to do with core isolation. Once I disabled Core Isolation, all my utilities worked. CPU-Z, FanControl, HWInfo, and Corsair iCUE on my system were all not working. But after disabling CI, all are working again.
 
vpr5703 said:
As an update to this - I was having this issue after the update. it has to do with core isolation. Once I disabled Core Isolation, all my utilities worked. CPU-Z, FanControl, HWInfo, and Corsair iCUE on my system were all not working. But after disabling CI, all are working again.
Click to expand...
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 features) to an allow list on the local PC, they need to stop this crap and give devs of paid software a helping hand to correct these issues without the end user having to turn off an entire security feature (that is still useful for the most part) for one binary that is from a trusted source.
 
Some vendors have tried to discuss this with Microsoft and what MS claims is not quite what we observe. As our drivers should be HVCI-compliant (verified using MS tools), they should not be blacklisted. So we're still not sure whether this is some bug in Windows resulting in incorrect blocking of drivers, or there are some other criteria enforced now which we're unaware of yet. A vary bad way of MS treating their customers and vendors creating software for their systems.
 
so what's new? Microsoft thinks they're too big and important to ever be wrong.
Martin said:
Some vendors have tried to discuss this with Microsoft and what MS claims is not quite what we observe. As our drivers should be HVCI-compliant (verified using MS tools), they should not be blacklisted. So we're still not sure whether this is some bug in Windows resulting in incorrect blocking of drivers, or there are some other criteria enforced now which we're unaware of yet. A vary bad way of MS treating their customers and vendors creating software for their systems.
Click to expand...
 
We still don't know. The initial discussion evolved until the point where we said that we're not aware of being non-compliant and asked them to explain us the reason why are they blocking us. Beyond that point we haven't received an answer...
 
Martin said:
We still don't know. The initial discussion evolved until the point where we said that we're not aware of being non-compliant and asked them to explain us the reason why are they blocking us. Beyond that point we haven't received an answer...
Click to expand...

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
 
Looks like this issue might be a bug in Windows code and Microsoft will fix it. That might happen in 1-2 weeks if all goes well.
 
You must log in or register to reply here.
Back
Top