Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Windows » Fix unable to start the Application Identity Service

Fix unable to start the Application Identity Service

Posted on 22/08/202404/09/2024 IT Expert By IT Expert No Comments on Fix unable to start the Application Identity Service
AppLocker

In this article, you will learn how to “fix unable to start the Application Identity Service”. The Application Identity service (AppIDSvc) is a Windows service that determines and verifies the identity of an application. This service is crucial for enforcing AppLocker policies, which help control which applications and files users can run on a system. Please see How to enable or disable User Account Control, ow to Check if Windows Updates were installed, and how to “Prevent Local Administrators from managing BitLocker with the manage-bde command‘.

Note: According to Microsoft, AppLocker is a defense-in-depth security feature and not considered a defensible Windows security feature. Since the rise of Ransomware and high profile attacks, AppLocker can help in the prevention of malware infection. To help protect against these risks, the Defense in Depth approach must be employed.

Please see “how to Disable UAC with Group Policy and enable PIN in Windows Hello, how to fix “Application pool has been disabled or Changing identity user for IIS Application Pool (Event ID 5059)“, and how to WinPE USB Drive: Fixing System Boot Issues.

Reason for “Application Identity Service Access Denied“

The Application Identity Service could not start via the Services Manager due to the error message prompted as shown below is related to system configuration issues.

Starting with Windows 10, the Application Identity service is now a protected process. As a result, you can no longer manually set the service Startup type to Automatic by using the Services snap-in

Error 5 Access denied
Access denied

Note: The Application Identity service determines and verifies the identity of an app. When this service is not running, AppLocker policies from being enforced.

Configure Application identity Services to Start

Starting a service through the Services Manager might not always prompt for elevation or the correct administrative rights. Group Policies and Registry modifications often ensure that the necessary permissions are applied.

Note: The Application Identity Service might require elevated permissions that are not granted when starting it manually through the Services Manager.

To fix this issue, open the Registry Editor by pressing Win + R, type regedit, and press Enter to open the Registry Editor.

Note: If prompted by User Account Control (UAC), click Yes.

Launch registry

Navigate to the Application Identity Service Key via the Registry Editor

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AppIDSvc
AppIDSVC-Start

This registry key contains the configuration settings for the Application Identity service.

Check and Modify the Registry Values. In the AppIDSvc key, locate the Start value in the right pane. The Start value determines the startup type of the service.

Change from 3 to 2

Set the Start value to 2 to configure the service to start automatically:

  • Value: 2 (Automatic)
  • Value: 3 (Manual)
  • Value: 4 (Disabled)

To change the value, double-click on Start and enter 2 in the Value data field and click OK

Changed to 2

After making these changes, close the Registry Editor. Restart your computer to apply the changes.

restart PC

Upon device restart, you should be able to set the Application identity Services to Automatic.

Application identity properties

The Application identity service is running as shown below.

Application Identity set to automatic

Please see Microsoft Account Password Reset via Web and Windows, and ‘MFA on Root Account: Create a User on AWS and Register MFA“.

Note: To disable this service in the future, you also have to use the GPO or Windows Registry Editor. Else, you will be prompted with the Access Denied wizard.

Set AppIDSvc via command prompt or PowerShell

Open an elevated command prompt or PowerShell and enter the command below and press Enter.

sc.exe config appidsvc start=auto

I prefer to use this command below since I also want to have the services started.

sc config "AppIDSvc" start=auto & net start "AppIDSvc"
Enable Application Identity Service

Note: The Startup type of the AppIDSvc cannot be set to Manual using sc.exe. Therefore, it is recommend to perform a system backup before changing it.

Start the Application Identity service automatically using GPO

Please launch the Group Policy Management Console (gpmc.msc) ad navigate to the console tree

Computer Configuration\Windows Settings\Security Settings, select System Services

In the details pane, double-click Application Identity. In Application Identity Properties, configure the service to start automatically.

I hope you found this guide very useful on how to Fix unable to start the Application Identity Service. Please feel free to leave a comment below.

5/5 - (1 vote)

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Windows Tags:Microsoft Windows, Windows 10, Windows 11

Post navigation

Previous Post: Creating a WinPE USB Drive: Fixing System Boot Issues
Next Post: How to create Bitbucket Repository

Related Posts

  • Featured image Windows Security
    How to clear Cache and Manually Update Microsoft Defender Anti-Virus Solution
  • WinRM set up for specific IP
    Configure WinRM to accept connection from a specific IP Address Windows
  • Slide2 2
    Oracle VirtualBox: Installing Windows 11 without TPM Support Virtualization
  • Migrate RDS CALs
    How to Migrate RDS CALs Windows
  • Trellix Native Encryption
    Manage BitLocker and FileVault with Trellix Native Encryption Mac
  • Featured Image 1
    How to enable or disable a Remote WMI Connection in Windows Windows

More Related Articles

Featured image Windows Security How to clear Cache and Manually Update Microsoft Defender Anti-Virus Solution
WinRM set up for specific IP Configure WinRM to accept connection from a specific IP Address Windows
Slide2 2 Oracle VirtualBox: Installing Windows 11 without TPM Support Virtualization
Migrate RDS CALs How to Migrate RDS CALs Windows
Trellix Native Encryption Manage BitLocker and FileVault with Trellix Native Encryption Mac
Featured Image 1 How to enable or disable a Remote WMI Connection in Windows Windows

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • The Port used for the Virtualhost is not an Apache Listen Port
    Fix the Port used for the Virtualhost is not an Apache Listen Port Web Server
  • PowerShell Exec
    Determine the execution policy configured on Windows PC Windows
  • Screenshot 2020 12 30 at 01.03.14
    Device cannot use a Trusted Platform Module: Allow BitLocker without a compatible TPM Windows
  • Azure VM Creation With CLI 1
    Deploy a Linux virtual machine (VM) on Azure using the Azure CLI AWS/Azure/OpenShift
  • Screenshot
    An error occurred while attempting to start the selected VM Virtualization
  • switchlinuxusers
    How to Switch between Users in Linux Linux
  • HyperV copy
    How to convert a VHDX file to a VHD Virtualization
  • SCSI Controoler HyperV issue failed to start VM
    Failed to Power on with Error ‘A virtual machine disk support provider for the specified file was not found Virtualization

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,803 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

AWS Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.