STATUS_SECUREBOOT_NOT_BASE_POLICY: meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

A supplemental Secure Boot policy was supplied where Windows requires a base policy.

Previous	Next
STATUS_SECUREBOOT_REQUIRED_POLICY_FILE_MISSING	STATUS_SECUREBOOT_NOT_SUPPLEMENTAL_POLICY

STATUS_SECUREBOOT_NOT_BASE_POLICY

STATUS_SECUREBOOT_NOT_BASE_POLICY (NTSTATUS 0xC043000F) This NTSTATUS value reports that a supplemental policy was passed where a base policy is required.

What to check

Verify the policy role expected by the API or deployment step.
Keep the base policy and supplemental policy deployment paths separate.
Use the correct signed package rather than repurposing the policy file.

Read-only checks

Get-SecureBootPolicy | Format-List

Base and supplemental policies are different policy roles, not interchangeable file names. Select the actual base-policy package for the device and establish it before deploying supplements that depend on it.

Base and supplemental policies have different deployment roles. Correct the artifact selection at the caller or deployment stage; renaming the file or forcing installation does not change the policy type encoded in it.

Microsoft: Confirm-SecureBootUEFI

Microsoft: Get-SecureBootPolicy

Microsoft: Viewing Code Integrity events

Looking for a different code? Search another status or error code.