Windows Smart App Control blocks unsigned bsk.exe; extension remains disconnected

The installed Windows bsk.exe cannot launch, including a version-only invocation. Windows returns: An Application Control policy has blocked this file.

File size: 11958272 bytes
SHA256: 772026d5204dc5659794d68055a98507415d06222d1ef8e4e2578f8aba465eee
Authenticode: NotSigned
CodeIntegrity event 3077 identifies policy {0283ac0f-fff1-49ae-ada1-8a933130cad6}. Event 3099 maps it to VerifiedAndReputableDesktop. VerifiedAndReputablePolicyState is 1.

The extension popup reports Ext 0.2.1, Disconnected, and [WSTransport] disconnect during connect. The installed CLI was previously reported as 0.2.0; it cannot currently execute to reconfirm its version. Multiple update staging artifacts exist; their existence does not establish the cause of the security block.

The latest release checked on 2026-09-16 is cli-v0.2.1 (2026-09-09). Its release notes mention Windows self-update and pipe fixes. We found no statement in those release notes confirming a fix for this Smart App Control block. We have not executed a replacement build or modified security policy.

Please confirm:

1. Is an officially signed Windows build available, with verifiable publisher and checksum?
2. Is Smart App Control supported, and what supported remediation preserves Windows protection?
3. After approved recovery, what is the supported way to inspect and clean up prior owned sessions without affecting user tabs or other profiles?

No credentials, customer data, browser tokens or business screenshots are included.

Start by reviewing the Windows Smart App Control evidence for the installed bsk.exe and the cli-v0.2.1 release notes. Verify whether an officially signed build and supported remediation exist, then determine the supported session-cleanup procedure that avoids user tabs and other profiles. Done means the signing, recovery, and cleanup guidance is confirmed.