Application signed and blocked by Smart App Control

Question

Hello,

For the past few weeks, the software we publish has been blocked by Smart App Control for many of our users running Windows 11 25H2. We have signed all .exe and .dll files with RSA 4096-bit code.

According to the page https://learn.microsoft.com/fr-fr/windows/apps/develop/smart-app-control/code-signing-for-smart-app-control, this signature should have allowed unblocked execution. However, this is not the case, and .exe and .dll files are being blocked regularly. Disabling Smart App Control seems to be the only solution.

Do you have a solution so that our customers can use our software without this blocking and without disabling Smart App Control, please ?

Sincerely.

Answer 1

Eroare de instalare - 0x8007064c

Answer 2

This is a known issue affecting many developers right now. Smart App Control doesn't just check if your code is signed — it also checks your software's reputation in Microsoft's cloud-based trust system. Even with a valid signature, new or low-distribution software gets blocked until enough users have safely installed it, and Microsoft's systems build trust for your files.

A few things that can help:

• Submit your software to Microsoft for review through the Microsoft Security Intelligence portal. This can speed up reputation building.
• Sign your installer (MSI/MSIX) in addition to individual exe and dll files. Smart App Control treats signed installers differently from loose executables.
• Consider distributing through the Microsoft Store if feasible, as Store apps bypass Smart App Control entirely.

Answer 3

Smart App Control (SAC) does not rely only on key length or the fact that binaries are signed. It combines:

1. Cloud-based reputation (Intelligent Security Graph / app intelligence services)
2. Code integrity policy
3. Signature validity and trust chain (certificate must chain to a CA in the Microsoft Trusted Root Program)

If the cloud service cannot confidently classify the app as safe, SAC will then check whether the binaries are signed with a certificate issued by a trusted root CA. If either the reputation is bad/unknown or the certificate chain is not trusted as expected, SAC will block the binaries even if they are RSA 4096-bit signed.

To allow customers to run the software without disabling Smart App Control:

1. Ensure all code is signed correctly
   • Sign every executable component that SAC can load: .exe, .dll, installers, temp installer files, scripts, uninstallers, and any binaries loaded by integrations (for example Office add-ins).
   • Use a code signing certificate from a CA that is part of the Microsoft Trusted Root Program, or use Microsoft Trusted Signing.
   • Verify the full certificate chain on an affected Windows 11 25H2 device to confirm it chains to a trusted root.
2. Test the app with Smart App Control audit policies
   • Use the documented SAC audit policy to test the app in an environment where SAC logs what it would block without actually blocking execution.
   • After enabling the audit policy and refreshing with citool.exe -r, reproduce installation and all major features so SAC evaluates all code paths.
3. Review Code Integrity event logs on affected machines
   • On a device where the app is blocked, open Event Viewer → Application and Services Logs → Microsoft → Windows → CodeIntegrity → Operational.
   • Look for SAC-related events:
     • Event ID 3076: evaluation mode
     • Event ID 3077: enforcement mode
   • These events show which specific files are blocked and why. Use this to identify unsigned or mis-signed binaries, or components loaded indirectly (for example helper EXEs, plug-ins, or scripts) that were missed during signing.
   • Note that the log records only blocked/audited files, not high-level “installation failed” reasons, so each blocked file must be addressed.
4. Address any blocked or misconfigured components
   • For each blocked file in the CodeIntegrity log:
     • Confirm it is signed with the same trusted certificate and timestamped correctly.
     • If it is intentionally unsigned (for example a script), consider signing it or refactoring so that only signed binaries execute.
   • Rebuild and redistribute the installer after ensuring all binaries are properly signed and trusted.
5. Keep Windows and Defender up to date
   • SAC’s cloud intelligence is updated regularly. Ensure customers have current Windows and Microsoft Defender updates so reputation and classification are up to date.

If, after verifying trusted-root signing and fixing all blocked components, SAC still blocks the app, collect the relevant CodeIntegrity 3076/3077 events and engage Microsoft support so the app’s reputation and any false positives can be investigated using those event details.

---

References:

• Smart App Control overview
• Test your app's signature with Smart App Control
• Application Control for Windows
• Smart App Control Frequently Asked Questions
• App & browser control in the Windows Security App
• Application and driver control