WDAC / Code Integrity policy blocks a legitimate executable on my personal Windows P

Question

WDAC / Code Integrity policy blocks a legitimate executable on my personal Windows P

ardıl gedikli 0

Hello,

I am using a personal Windows PC and I am trying to set up a development environment for creating my own mobile application.

Windows is blocking a legitimate executable because of an active WDAC / Code Integrity policy.

When I try to run a developer tool, Windows reports that the file was blocked by an Application Control policy.

In the Code Integrity event log, I found Event ID 3077 with the following Policy ID:

{0283AC0F-FFF1-49AE-ADA1-8A933130CAD6}

I also found an active Code Integrity policy file with the same ID:

C:\Windows\System32\CodeIntegrity\CIPolicies\Active{0283AC0F-FFF1-49AE-ADA1-8A933130CAD6}.cip

The blocked executable is a legitimate developer tool.

I checked the device status and my PC is not Azure AD joined, Enterprise joined, or Domain joined.

I do not want to disable WDAC, Code Integrity, Smart App Control, or other Windows security features.

I would like to understand:

Where did this Code Integrity policy come from, and why is it active on my personal PC?

What does this Policy ID represent?

Why are legitimate developer executables being blocked?

What is the Microsoft-supported way to allow trusted developer tools without disabling Windows security?

Would a controlled supplementary policy be appropriate in this situation?

I can provide additional Code Integrity Event 3077/3089 logs and other non-sensitive diagnostic information if needed.

Thank you.

0 comments

1 answer

Your answer

Answer 1

Alex-L 12,555 Microsoft External Staff Moderator

Hi ardıl gedikli

The Policy ID you found,{0283AC0F-FFF1-49AE-ADA1-8A933130CAD6}, is a Microsoft inbox Code Integrity policy associated with Smart App Control ("VerifiedAndReputableDesktop") on Windows 11. Its presence in the Active CI Policies folder is normal on supported consumer devices where Smart App Control is enabled.

A legitimate developer tool can still be blocked if Microsoft's reputation service cannot confidently determine that the file is trusted, if the file is unsigned, or if its signature/reputation does not satisfy the policy requirements. Smart App Control uses the same App Control/Code Integrity engine that generates Event ID 3077 block events.

To investigate further without disabling security features, please share the Event ID 3077 and related Event ID 3089 details (redacting any personal information), including:

Full file name and path
Signer/publisher information
Any "Signing Level" or "Verification" details shown in Event 3089

That information can help determine whether the block is due to missing reputation, a signing issue, or another policy condition. A supplementary WDAC policy is generally an advanced App Control management scenario and is typically used in managed environments rather than as the first troubleshooting step on a personal Windows PC.

Alex-L 12,555 Reputation points Microsoft External Staff Moderator

2026-09-01T14:42:56.94+00:00

Hi ardıl gedikli
Did you get a chance to check my reply? Feel free to reach out if anything is unclear.
ardıl gedikli 0 Reputation points

2026-09-04T12:35:26.7433333+00:00
Hello,

Thank you for your explanation. I checked the Code Integrity events you requested and collected the requested information.

The blocked executable is the Dart executable bundled with my Flutter SDK:

C:\src\flutter\bin\cache\dart-sdk\bin\dart.exe

The Event ID 3077 contains the following information:

Policy Name: VerifiedAndReputableDesktop

Policy GUID: {0283AC0F-FFF1-49AE-ADA1-8A933130CAD6}

Policy ID: 27555.1000.240208

Requested Signing Level: 2

Validated Signing Level: 1

Status: 0xc0e90002

SHA-256: EE0F77F91285A74D005519F288E0DFC4DC9AB8CB46438C52AD6B381667A5A4A8

Process attempting to load the file: C:\Windows\System32\cmd.exe

The Event ID 3089 contains the following signature information:

TotalSignatureCount: 0

SignatureType: 0

ValidatedSigningLevel: 0

VerificationError: 0

PublisherName: Unknown

IssuerName: Unknown

KnownRoot: 0

I have not disabled Smart App Control, Code Integrity, or any other Windows security feature.

Based on these events, could you please help me determine whether this block is specifically caused by the file's lack of signature, Microsoft's reputation requirements, the signing level mismatch, or another condition of the VerifiedAndReputableDesktop policy?

My goal is to keep Smart App Control and the other Windows security features enabled while using Flutter for legitimate software development.

Could you also clarify the Microsoft-supported approach for running legitimate developer tools such as Flutter's bundled Dart SDK in this situation?

In particular:

Is there a supported way to allow a trusted developer executable while keeping Smart App Control enabled?

If supplementary App Control/WDAC policies are not recommended as the first approach on a personal PC, is there another supported mechanism for this scenario?

If the expected solution is to use a signed/reputable version of the Dart executable, is there an official Flutter or Dart distribution that meets the signing requirements of Smart App Control?

I would prefer a solution that preserves Windows security rather than disabling Smart App Control.

Thank you for your assistance.Hello,

Thank you for your explanation. I checked the Code Integrity events you requested and collected the requested information.

The blocked executable is the Dart executable bundled with my Flutter SDK:

C:\src\flutter\bin\cache\dart-sdk\bin\dart.exe

The Event ID 3077 contains the following information:

Policy Name: VerifiedAndReputableDesktop

Policy GUID: {0283AC0F-FFF1-49AE-ADA1-8A933130CAD6}

Policy ID: 27555.1000.240208

Requested Signing Level: 2

Validated Signing Level: 1

Status: 0xc0e90002

SHA-256: EE0F77F91285A74D005519F288E0DFC4DC9AB8CB46438C52AD6B381667A5A4A8

Process attempting to load the file: C:\Windows\System32\cmd.exe

The Event ID 3089 contains the following signature information:

TotalSignatureCount: 0

SignatureType: 0

ValidatedSigningLevel: 0

VerificationError: 0

PublisherName: Unknown

IssuerName: Unknown

KnownRoot: 0

I have not disabled Smart App Control, Code Integrity, or any other Windows security feature.

Based on these events, could you please help me determine whether this block is specifically caused by the file's lack of signature, Microsoft's reputation requirements, the signing level mismatch, or another condition of the VerifiedAndReputableDesktop policy?

My goal is to keep Smart App Control and the other Windows security features enabled while using Flutter for legitimate software development.

Could you also clarify the Microsoft-supported approach for running legitimate developer tools such as Flutter's bundled Dart SDK in this situation?

In particular:

Is there a supported way to allow a trusted developer executable while keeping Smart App Control enabled?

If supplementary App Control/WDAC policies are not recommended as the first approach on a personal PC, is there another supported mechanism for this scenario?

If the expected solution is to use a signed/reputable version of the Dart executable, is there an official Flutter or Dart distribution that meets the signing requirements of Smart App Control?

I would prefer a solution that preserves Windows security rather than disabling Smart App Control.

Thank you for your assistance.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
scan2439 0 Reputation points

2026-09-05T13:58:29.1933333+00:00

The Event 3089 details suggest that Smart App Control is not recognizing a trusted signature for the bundled "dart.exe" ("TotalSignatureCount: 0", "PublisherName: Unknown", "ValidatedSigningLevel: 0").

There are also recent Flutter reports of Windows Application Control blocking other Flutter toolchain binaries, so this may be an upstream Flutter/Dart compatibility or signing issue rather than a device-specific WDAC configuration problem.

Have you tested the latest stable Flutter SDK from the official source and checked whether other bundled binaries are blocked as well?

Also, just for context, is the application you are developing more of a general-purpose app, or does it involve scientific/technical functionality? That may matter if the workflow later depends on additional native tools or packages.