Hi Martins Marco,
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.
I'm trying to improve the security of my work computer, but the Windows Security app is preventing me from enabling the memory integrity option. It keeps reporting an old WIDCOMM driver called Frmupgr.sys (published as oem80.inf) as the cause of the conflict. This thing dates back to 2007, and I have no idea where to find a newer version, or even how to properly remove it so my compliance status returns to green. Help!
Hi Martins Marco,
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 Martins Marco,
The block you are encountering is caused by the Hypervisor-Protected Code Integrity (HVCI) check, which ensures that all kernel-mode drivers are properly signed and compatible with virtualization-based security.
To resolve this, you must first confirm that the driver is still indexed as oem80.inf. Open an elevated Command Prompt or PowerShell and run the command pnputil /enum-drivers. Look for the entry that matches Frmupgr.sys to ensure the "Published Name" is still oem80.inf. Once confirmed, execute pnputil /delete-driver oem80.inf /uninstall /force. This utility removes the driver's INF manifest and purges the binary from the staging area, ensuring the operating system no longer attempts to load or validate the incompatible file.
After that, a full system restart is required to flush the kernel's driver stack. Upon rebooting, navigate to the Device Security page within the Windows Security app and select Core Isolation details. With the conflicting driver purged, the Memory Integrity toggle will no longer be grayed out, allowing you to enable the feature and secure the system. This administrative cleanup is the standard protocol for resolving HVCI compatibility errors without compromising system stability.
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