After the Digital Signature Driver Verification (Windows Driver Signature Enforcement) has been enabled.You fixed in a new hard disk drive (HDD) or solid state drive (SSD).After upgrading to a new version of Windows.After flushing or resetting UEFI/BIOS to factory settings.

After the installation of a secondary operating system on your PC (dual boot configuration).

The error can occur in any of the following scenarios: When the PC is turned on, and the OS that’s detected is not compatible with the feature, a boot is prevented and the Secure Boot Violation error message is displayed.Īlthough the problem was later patched by Microsoft, it somehow still exists in later versions of Windows, including Windows 10. It is therefore not fully enabled on machines running on the OS.īut once the update is installed, Secure Boot gets fully activated. This happened because the Secure Boot Technology present in ASUS motherboards is not compatible with some versions of Windows. The purpose was achieved but coincidentally, the update also resulted in the “Invalid signature detected” error on ASUS PCs. KB3133977 was meant to fix a problem that prevented drive encryption by BitLocker.

The issue began on Windows 7, after the KB3133977 update was released.

Ventoy secure boot violation