Back to Blog

Event ID 3076 App Control Audit Block and How to Allow the File

Christopher 4 min read
referencewindows

Event ID 3076 is written to the Code Integrity operational log when an App Control for Business policy in audit mode finds a file it would have blocked. Microsoft's event reference describes it as "the main App Control block event for audit mode policies. It indicates that the file would have been blocked if the policy was enforced." In Event Viewer the log is under "Applications and Services Logs" > "Microsoft" > "Windows" > "CodeIntegrity" > "Operational". Scripts and MSI installers are logged under "AppLocker" > "MSI and Script" as event 8028 instead.

What it means

The file still ran, because the policy is in audit mode. Once audit mode is removed from the policy, the same file is blocked and the log shows event 3077. A separate 3076 event is written for each active policy that would block the file.

How to find the cause

List the latest audit block events with the time and message of each.

Get-WinEvent -FilterHashtable @{ LogName='Microsoft-Windows-CodeIntegrity/Operational'; Id=3076 } -MaxEvents 50 | Select-Object TimeCreated,Message

Read these fields in each event's details.

Find the signature details in event 3089. Windows writes one 3089 event for each signature on the file, and an unsigned file gets a single 3089 with "TotalSignatureCount" of 0. Match a 3089 to its 3076 by the "Correlation ActivityID" in the "System" section of both events. The "VerificationError" field gives the reason a signature failed the policy.

List the policies active on the machine on Windows 11 22H2 and later or Windows Server 2025.

citool.exe -lp -json

Look up a status code from an event with certutil.exe -error <status>.

Fixes

Build rules from the audit events on a machine where the files still exist. This example uses the FilePublisher level with a hash fallback and writes warnings to a text file.

New-CIPolicy -FilePath .\EventsPolicy.xml -Audit -Level FilePublisher -Fallback SignedVersion,FilePublisher,Hash -UserPEs -MultiplePolicyFormat 3> .\EventsPolicyWarnings.txt

Review EventsPolicy.xml and remove any rule for a file you don't want to allow. EventsPolicyWarnings.txt lists each file that couldn't get a rule at the level or fallback you chose. New-CIPolicy only creates rules for files still on disk, so add rules by hand for a file that's gone.

Merge the new rules into your base policy, or deploy them as a supplemental policy.

Merge-CIPolicy -PolicyPaths '.\BasePolicy.xml','.\EventsPolicy.xml' -OutputFilePath '.\MergedPolicy.xml'

Convert the merged policy to a binary named after its PolicyId, copy it to C:\Windows\System32\CodeIntegrity\CIPolicies\Active\, and activate it. Use CiTool --update-policy on Windows 11 22H2 and later and Windows Server 2025. Use the App Control policy refresh tool (RefreshPolicy.exe) on Windows 10 version 1903 and later and Windows Server 2022.

ConvertFrom-CIPolicy .\MergedPolicy.xml .\{PolicyId}.cip

Remove audit mode once the 3076 events show no file you still need to allow, then convert and deploy the policy again.

Set-RuleOption -FilePath .\MergedPolicy.xml -Option 3 -Delete

For the first ring of an enforced policy, Microsoft recommends adding option 9, which lets a user turn off enforcement for one boot from a pre-boot menu, and option 10, which switches the policy to audit if a boot critical driver is blocked.

Related events

Where ET Ducky shows it

I build ET Ducky. It keeps a per-organization list of approved applications and lists the software detected across your fleet that isn't on it, with a count of how many agents have each app. The approved-app-hash-mismatch rule runs cloud-side, is off by default until your organization enables it, and flags an approved application whose main binary hash differs from your organization's reference hash.

Sources

Approved applications across your fleet

Read how to keep an approved software list and review the software across your fleet that isn't on it.

Read the Approved Applications docs