Fix unable to start the Application Identity Service

Running into the “Unable to start the Application Identity Service” error on Windows? You’re not alone. This service is key for features like AppLocker, and when it won’t start, it can break app whitelisting and even mess with group policies. The good news? You can fix it.

What Is the Application Identity Service?

The Application Identity Service helps Windows identify and verify software running on your computer. It’s crucial if you use AppLocker or need strict application controls for security.

If this service fails to start, you might see errors like:

• Error 1079: The account specified for this service is different from the account specified for other services running in the same process.
• Error 1068: The dependency service or group failed to start.

Here’s how to troubleshoot and resolve these issues.

Step 1: Check and Start the Service Manually

1. Press Windows + R, type services.msc, and press Enter.
2. In the Services window, find Application Identity.
3. Right-click it and choose Start.

If it starts, you’re good. If not, continue below.

Step 2: Fix Dependencies

The Application Identity Service depends on other services—especially the Remote Procedure Call (RPC). Here’s how to check:

1. In Services, double-click Application Identity.
2. Click the Dependencies tab.
3. Make sure all listed services are running (especially RPC).

If a dependency isn’t running, try to start it. If you see errors, note them—they’ll point to what’s broken.

Step 3: Set the Service to Automatic

1. In Services, right-click Application Identity > Properties.
2. Set Startup type to Automatic.
3. Click Apply, then OK.

Restart your PC and check if the service starts.

Step 4: Reset the Service Account

If you get Error 1079:

1. Double-click Application Identity in Services.
2. Go to the Log On tab.
3. Select This account and type Local Service or select Local System account.
4. Remove any passwords, click OK, and restart the service.

Step 5: Check for Corrupted System Files

Sometimes, system file corruption is the problem. Fix it with these commands:

1. Open Command Prompt as Administrator.
2. Type:
   sfc /scannow
   Press Enter and let it finish.
3. (Optional) Also run:
   DISM /Online /Cleanup-Image /RestoreHealth

Restart after these scans.

Step 6: Check Windows Event Viewer

If none of the above works:

1. Open Event Viewer (eventvwr.msc).
2. Go to Windows Logs > System.
3. Look for errors related to Application Identity.

These logs can help pinpoint what’s wrong.

When All Else Fails

If the service still refuses to start, your Windows install may be deeply corrupted. You can try:

• System Restore to a point before the issue started.
• Repair Install using the Windows installation media.
• Consult your IT admin if you’re on a company PC.

Conclusion

The “Unable to start the Application Identity Service” error is annoying, but with these steps, you’ll likely get things running again. If you’re stuck or run into a unique error message, drop a comment below—I’ll help you out.

Need more Windows troubleshooting tips? Subscribe to the blog for regular, real-world fixes!

Mark Vincent

Tech enthusiast and content creator passionate about making technology simple for everyone. I share practical tips, guides, and reviews on the latest in computers, software, and gadgets. Let’s explore the digital world together!