Hi Administrator IT,
How is your issue going? Has it been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)
VP
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Dear Microsoft,
Recently, like the end of March or the start of April, some Windows updates were rolled out, and I think it's affecting most of my users who are using devices running Windows 11 Business or Enterprise. They are all experiencing Device freezing, and the only way to make it respond again is through a cold boot. I have done a malware scan and checked Windows corrupted files but seems not to rectify the issue. When I check Event Viewer, for something specific is causing it, there is nothing out of the ordinary. The interesting thing is that all users who have Windows 11 Business or Enterprise are the ones experiencing this issue. Others using Windows 11 Pro are okay. What could be causing this?
Moved from: Windows for home | Windows 11 | Windows update
Answer accepted by question author
Hi Administrator IT,
How is your issue going? Has it been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)
VP
Hi Administrator IT,
The discrepancy between your Windows 11 Pro and Business/Enterprise installations shows a conflict within the Virtualization-Based Security stack. While Pro editions allow for more flexible security configurations, Enterprise and Business editions often have Credential Guard and Hypervisor-protected Code Integrity enabled by default via Group Policy or Intune. Recent kernel-mode changes in the April cumulative updates can cause a deadlock between the Windows Hypervisor and specific hardware abstraction layers, leading to the total system freezes you described. Because these freezes occur at the ring 0 kernel level, the operating system is unable to commit a crash dump to the disk or write a specific error to the Event Viewer before the CPU execution halts, leaving only a generic Event ID 41 after you perform the cold boot.
To resolve this, you should first identify the specific update installed during the late March or early April window and attempt a roll-back on a single test machine. You can do this by navigating to the Windows Update history or using the command line to remove the specific KB package. If the freezing persists, the issue likely resides in an incompatibility between the new kernel instructions and your hardware microcode. You should immediately verify if there are pending BIOS or UEFI firmware updates from your device manufacturer, as these updates often contain critical fixes for how the CPU handles memory isolation.
If firmware updates are unavailable or do not fix the lockups, you should test the impact of disabling Memory Integrity. You can find this setting in the Windows Security app under Device Security and Core Isolation. If disabling this feature stops the freezing, it confirms a conflict with a specific driver, often related to the chipset or display, that is not fully compatible with the updated security integrity checks. In a production environment, you should look for updated drivers that are HVCI-compliant rather than leaving security features permanently disabled. Monitoring the Microsoft Release Health dashboard for any acknowledged regressions in the Enterprise subscription service is also highly recommended during this period.
Hope this answer brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VP