ERROR_SECUREBOOT_POLICY_NOT_SIGNED - 4424 (0x1148)
The Secure Boot policy is either not signed or is signed by a non-trusted signer.
Updated: Feb 21, 2026
Introduction
This error code, ERROR_SECUREBOOT_POLICY_NOT_SIGNED with the numeric value 4424 or hexadecimal 0x1148, indicates that a Secure Boot policy is either unsigned or signed by a non-trusted signer. This can impact system security and boot process integrity.
Technical Meaning
Secure Boot is a feature in Windows designed to ensure that only trusted operating systems and drivers are loaded during the boot process. The Secure Boot policy defines which digital signatures are considered valid for booting the system. If this policy is not signed or is signed by an untrusted entity, it can compromise the security of the system.
Error Details
The error ERROR_SECUREBOOT_POLICY_NOT_SIGNED suggests that there is a discrepancy in the Secure Boot policy's signing status. This could be due to several reasons such as incorrect configuration, mismanagement of certificates, or potential tampering with the boot environment.
Usage Context
This error typically occurs during system initialization when the operating system attempts to validate the Secure Boot policy against known trusted signers. It can also appear in scenarios where the system is being configured or updated, particularly involving changes to the boot configuration data (BCD) or secure boot settings.
Developer Interpretation
Developers should interpret this error as an indication that the system's security posture may be compromised. This could lead to unauthorized software execution during the boot process and potentially allow malicious code to bypass security checks. Developers are advised to ensure that all Secure Boot policies are correctly signed by trusted entities before deploying any updates or configurations.
Related Errors
ERROR_SECUREBOOT_POLICY_INVALID(0x1149): Indicates an invalid Secure Boot policy.ERROR_SECUREBOOT_POLICY_NOT_FOUND(0x114A): Suggests that the Secure Boot policy could not be located.
FAQ
Q: What does this error mean?
A: This error indicates that the Secure Boot policy is either unsigned or signed by a non-trusted signer, which can compromise system security during boot.
Q: How can I resolve this issue?
A: Ensure that all Secure Boot policies are correctly signed by trusted entities. Review and update any certificates used in the secure boot configuration to ensure they are valid and trusted.
Summary
The ERROR_SECUREBOOT_POLICY_NOT_SIGNED error highlights a critical security concern related to the Secure Boot policy's signing status. Developers should take immediate action to verify and correct any issues with the Secure Boot policy to maintain system integrity during the boot process.