TrustAppManager — Create App Control for Business policies from audit to enforce, and keep a record of your decisions

A Windows app that takes App Control for Business (formerly WDAC) through app inventory, audit, impact review, allow and block decisions, and enforce policy creation (paid version).

Last updated: 2026-11-19

Features Free and paid Limitations Requirements Support 日本語

The problem it addresses

App Control for Business blocks apps that you have not allowed. If you apply enforce mode first, apps your business uses can be blocked. You need to record activity in audit mode and review the impact before you move to enforce. However, apps that do not appear in the audit log are also blocked in enforce mode unless you allow them. Running audit does not guarantee that no app stops after you enforce.

TrustAppManager guides you through these steps on screen. It keeps a record of which apps you allowed, blocked, or put on hold.

Features

PC scan

Lists the installed apps and the state of their signatures. Signature verification uses only the standard Windows signature check, which also confirms that the signature matches the file contents. It does not check revocation or catalog signatures. A signature shown as valid is not a guarantee of safety. You can also add the executables in a folder that you specify, so portable apps that are not installed can be covered. You can export the list and import it again.

Log diagnosis

Reads EVTX files (exported Windows event log files) or this PC's event logs (Code Integrity, which is where Windows records code signature and policy checks, and the AppLocker "MSI and Script" channel only) and summarizes the number of devices and runs for each app. It explains the impact of blocking in plain language. It does not modify or clear the logs.

Allow, block, and hold decisions

Choose the basis for allowing an app (publisher, file-content hash, the path of one file, or a folder) and enter a reason. You can also act on checked rows or on all apps from one signer (bulk action per signer). People make the decisions; the app never decides automatically.

Audit policy creation and export

Creates an audit policy (a policy that records events and does not block app execution) in two kinds. Even in audit mode, however, PowerShell can run in a restricted way and mshta can be blocked. Try it in an evaluation environment before you use it. "Initial" contains no allowed apps and is used for the first log collection. "Including allowed apps" includes the apps you allowed in log diagnosis as allowed, and is used to check how they behave under audit. You can also create one by adding your current allows to a policy (XML) you created earlier; signed policies are not supported. Exports distribution files, including guides for Intune and for a single PC, and a GPO guide (which explains that GPO settings cannot distribute the policy, and gives alternatives). You can choose whether to use Dynamic Code Security (policy option 19, which restricts code generated while an app runs and can stop apps that use it) after reading its impact. It is off by default. On Windows versions earlier than Windows 11 24H2, if you turn this setting on, the dynamic code restriction is enforced even in an audit-mode policy, and apps that use dynamic code can stop.

Enforce policy creation

Creates an enforce-mode policy when no apps are left in the state "Undecided", "Reviewed", or "On hold" (every app is allowed or blocked) and at least one is allowed. A single app left on hold prevents creation. Apps that do not appear in the audit log are also blocked in enforce mode unless you allow them; not appearing in the log does not mean an app is not used. If you enforce without checking the impact, apps you need can be blocked. Try it on a small number of devices first. In enforce mode, PowerShell runs in constrained language mode (a mode with fewer features), and some features become unavailable. Your choice on Dynamic Code Security (policy option 19) also applies to the enforce policy. Applying the exported steps to real devices with Intune, and the rollback, have not yet been checked. GPO settings cannot distribute this policy. The export includes rollback files that replace the policy with an allow-everything one to undo it (the administrator applies and rolls back).

Code signing

Creates a self-signed certificate or imports a PFX (a certificate file that includes the private key), and signs PowerShell scripts (.ps1, .psm1) and .exe and .dll files. Signing the policy itself is not supported. Shows certificate expiry and exports the public certificate (.cer) and the certificate with its key (.pfx) separately. For a signature without a timestamp, the following was observed on one environment (a Windows 11 virtual machine). When the certificate expired, a .ps1 file that was signed was no longer allowed and ran in a restricted way in enforce mode (.exe and .dll files were not affected in the range checked). A .pfx contains the private key, so keep it in a place where you control who can sign. The app does not manage the files you export. The certificate with its key (.pfx) can be exported only when the key of the certificate is exportable. A certificate created in the app can be exported. The key of an imported PFX is stored in a form that cannot be exported, so it cannot be exported. A certificate you select from the certificate store can be exported only if its key is exportable. A timestamp is optional. If you set the URL of a timestamp server (a service that attests the time of signing; the effect of adding a timestamp has not been verified) that starts with http:// and select the check that confirms you have read the timestamp server's terms of use, the app tries to add a timestamp when it signs. The hash of each file you sign is sent to the timestamp server every time, unencrypted. Whether one is added depends on the response and supported format of the timestamp server; the file is still signed if none is added.

Ledger

Review the allowed list, the blocked and on-hold list, and the decision history. You can export the decision history and the allowed list to CSV (CSV cannot be imported). The ledger can be exported to and imported from a ledger file in JSON format. The signing history and certificate list are in the paid version. The signing history scans a folder you specify and lists the signer and expiry of its files. For .exe and .dll files, signature verification uses only the standard Windows signature check, which also confirms that the signature matches the file contents; it does not check revocation or catalog signatures for them. The signature of a script (such as .ps1) is judged by Windows PowerShell. A signature shown as valid is not a guarantee of safety (read-only; the app does not save the result automatically, and you can also export it to CSV).

Japanese and English

The app screens are available in Japanese and English.

Demo mode

You can check every tab with fictional sample data. Your actual data is not used.

TrustAppManager does not apply policies to a PC. It saves the policy, and the administrator applies and distributes it.

How it works

What it cannot do

Who it is for

IT administrators in companies and organizations who introduce or operate app execution control on Windows PCs.

Free and paid versions

The free version lets you try the steps from the PC scan through audit policy creation, log diagnosis, and decision records. Enforce policy creation and code signing are paid features. In the app, locked features show "Available in the paid version" and become available after you buy the Microsoft Store add-on or redeem a promotion code. The paid add-on is "TrustAppManager Pro", and one purchase gives use without an expiry date.

FeatureFreePaid
PC scanYesYes
Log diagnosis (allow, block, and hold decisions; bulk actions)YesYes
Audit policy creation and distribution file exportYesYes
Ledger (allowed list, blocked and on-hold list, decision history, CSV export of the history and allowed list, ledger file export and import)YesYes
Enforce policy creation—Yes
Code signing (certificate creation and import, signing, timestamp, certificate export)—Yes
Ledger signing history and certificate list—Yes

Requirements and availability

Frequently asked questions

Does creating an enforce policy apply it to my PC?

No. The app saves the policy, and the administrator applies it.

Does the app send my logs or app lists anywhere?

Logs and app lists are not sent to the developer (Sumikko Lab) or to any external party. The external communication that the app itself performs occurs only in the following three cases. Communication that an OS such as Windows performs on its own to verify signatures is not included in the app's communication. (1) A connection to the timestamp server URL that you specify when you use code signing (the hash of each file you sign is sent every time, unencrypted). (2) The Microsoft Store license check performed by Windows. (3) When you select "Redeem" in the paid version guide, your default browser opens a Microsoft redemption page; the code you enter is included in the address of that page (the browser that opens does the communicating). See the Privacy Policy for details.

How do I unlock the paid features?

Buy the Microsoft Store add-on, or redeem a promotion code. "Redeem" is the button in the app's paid version guide: after you enter a code and select it, your default browser opens a Microsoft redemption page. The code you enter is included in the address of that page. When you finish redeeming, select "Check redemption" in the app. The price is shown on the Store page. You cannot purchase while the app runs as administrator. Restart it with standard rights.

What happens if the app cannot reach the Store?

If the app cannot confirm the purchase status, the paid features are not available. The free features, and viewing and exporting your decision records, remain available.

Where can I get help?

Write to the email address on the Support page.