From 5d3bbf3c0020b4aa39d0d466f47efea345aec16f Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Mon, 2 Apr 2018 14:19:23 -0700 Subject: [PATCH] added options to config appidsvc --- .../applocker/configure-the-application-identity-service.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/applocker/configure-the-application-identity-service.md b/windows/security/threat-protection/applocker/configure-the-application-identity-service.md index 81658b4b49..eace7b9b57 100644 --- a/windows/security/threat-protection/applocker/configure-the-application-identity-service.md +++ b/windows/security/threat-protection/applocker/configure-the-application-identity-service.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library author: brianlic-msft -ms.date: 09/21/2017 +ms.date: 04/02/2018 --- # Configure the Application Identity service @@ -38,7 +38,7 @@ Membership in the local **Administrators** group, or equivalent, is the minimum 2. Click the **Services** tab, right-click **AppIDSvc**, and then click **Start Service**. 3. 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 smnap-in. Try either of these methods instead: +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: