Configure the Application Identity service
- Windows 10
- Windows Server
This topic for IT professionals shows how to configure the Application Identity service to start automatically or manually.
The Application Identity service determines and verifies the identity of an app. Stopping this service will prevent AppLocker policies from being enforced.
Important: When using Group Policy, you must configure it to start automatically in at least one Group Policy Object (GPO) that applies AppLocker rules. This is because AppLocker uses this service to verify the attributes of a file.
To start the Application Identity service automatically using Group Policy
- On the Start screen, type gpmc.msc to open the Group Policy Management Console (GPMC).
- Locate the GPO to edit, right-click the GPO, and then click Edit.
- In the console tree under Computer Configuration\Windows Settings\Security Settings, click System Services.
- In the details pane, double-click Application Identity.
- In Application Identity Properties, configure the service to start automatically.
Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.
To start the Application Identity service manually
- Right-click the taskbar, and click Task Manager.
- Click the Services tab, right-click AppIDSvc, and then click Start Service.
- Verify that the status for the Application Identity service is Running.
Starting with Windows 10, the Application Identity service is now a protected process. Because of this, you can no longer manually set the service Startup type to Automatic by using the Sevices snap-in. Try either of these methods instead:
Open an elevated commnad prompt or PowerShell session and type:
sc.exe config appidsvc start= auto
Create a security template that configures appidsvc to be automatic start, and apply it using secedit.exe or LGPO.exe.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.