How to fix vscode .exe blocked

On a personal Windows 11 PC, check whether Smart App Control is enabled and turn it off if you need to repeatedly run newly compiled, unsigned C executables.

Personal PC: check Smart App Control

1. Open Windows Security.
2. Select App & browser control.
3. Open Smart App Control settings.
4. If its status is On, change it to Off.
5. Rebuild the program, then start debugging again.

Smart App Control checks an application's reputation and signature. If Windows cannot confidently classify a newly built executable and it has no valid signature, it can be treated as untrusted and blocked. There is currently no per-application exception for Smart App Control; the supported choices are disabling it or signing the executable. Recent Windows updates permit Smart App Control to be enabled again when available on the device.^1^

Security impact: turning it off reduces protection against unknown or unsigned applications. Only run executables built from code and libraries you trust.

Confirm which policy blocked it

If Smart App Control is already off—or the setting is unavailable—identify the active Application Control policy:

1. Press Windows key + R, enter eventvwr.msc, and press Enter.
2. Navigate to: Applications and Services Logs → Microsoft → Windows → CodeIntegrity → Operational
3. Rebuild and run the executable until it is blocked.
4. Refresh the log and inspect events at that time:
   • 3077: an enforced App Control policy blocked the executable.
   • 3089: signature details associated with the block.
   • 3099: identifies a loaded Application Control policy.
5. Open the event’s Details tab and note PolicyName, PolicyId, File Name, and Process Name.

These events identify the policy responsible rather than merely reporting the PowerShell launch failure.^2^

If this is managed by work or school

If Event 3077 names an organizational policy, or Windows says settings are managed by your organization, changing VS Code, PowerShell, or the debugger will not bypass it. Ask the administrator to review the 3077/3089 events and create an appropriate allow rule for your development workflow. Microsoft’s troubleshooting guidance specifically recommends checking active policies and correlated block/signature events.^3^

Do not apply .exe file-association registry fixes: executable launching works, and the reported failure is an explicit Application Control block rather than a broken file association.

References

1. Smart App Control Frequently Asked Questions | Microsoft Support
2. Understanding App Control events
3. App Control debugging and troubleshooting