From 1a1df150ac2ff84d2731208ac972fb48a9c46ad2 Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Fri, 8 Sep 2017 15:22:59 -0700 Subject: [PATCH] Added reg info --- .../application-management/per-user-services-in-windows.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/windows/application-management/per-user-services-in-windows.md b/windows/application-management/per-user-services-in-windows.md index 6d2daad557..ef38831b8b 100644 --- a/windows/application-management/per-user-services-in-windows.md +++ b/windows/application-management/per-user-services-in-windows.md @@ -17,7 +17,9 @@ Per-user services are services that are created when a user signs into Windows o > [!NOTE] > Per-user services are only in available in Windows Server if you have installed the Desktop Experience. If you are running a Server Core or Nano Server installation, you won't see these services. -You can't prevent per-user services from being created, but you can configure the template service to create them in a stopped and disabled state. You do this by setting the template service's **Startup Type** to **Disabled**. +Beginning with Windows 10, version 1709 and Windows Server, version 1709, there are two ways to prevent per-user services from being created: +- Configure the template service to create them in a stopped and disabled state. You do this by setting the template service's **Startup Type** to **Disabled**. +- Create a new Registry entry named UserServiceFlags under the service configuration in the registry as a DWORD (32 bit) value set to 0. > [!IMPORTANT] > If you change the template service's Startup Type, make sure you carefully test that change prior to rolling it out in your production environment.