Still broken in Windows 11 insider Dev build 25158
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.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.
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.
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...
Can confirm, no error when Core Isolation is active and HWiNFO just works (again).Apparently Windows 11 build 25174 should fix the issue.
This happen to me also today after the w11 update but i reinstall the hwinfo64 again and it's working again.Hi Team,
Yesterday My windows 11 was updated.
I can't run HWinfo64 anymore,
Please help me find what is blocking it.