From 34481b526b221c2baa1ee260c92e59c163d833b9 Mon Sep 17 00:00:00 2001 From: jcaparas Date: Mon, 9 May 2016 19:05:21 +1000 Subject: [PATCH] Update other-troubleshooting.md --- windows/keep-secure/other-troubleshooting.md | 31 ++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/windows/keep-secure/other-troubleshooting.md b/windows/keep-secure/other-troubleshooting.md index 30794e6303..7e360ec2a0 100644 --- a/windows/keep-secure/other-troubleshooting.md +++ b/windows/keep-secure/other-troubleshooting.md @@ -131,3 +131,34 @@ Check the startup type from the command line: 5. A success message is displayed. Verify the change by entering the following command and press **Enter**: sc qc diagtrack +Check the startup type in the services console: + +1. Open the services console: + + a. Click **Start** and type **services**. + + b. Press **Enter** to open the console. + +2. Scroll through the list of services until you find **Connected User Experiences and Telemetry**. + +3. Check the **Startup type** column - the service should be set as **Automatic**. + +ASK ALON HOW SET TO AUTOMATIC IF IT'S NOT SET FROM THE CONSOLE. + +Check that the service is running from the command line: + +1. Open an elevated command-line prompt on the endpoint: + + a. Click **Start** and type **cmd**. + + b. Right-click **Command prompt** and select **Run as administrator**. + +2. Enter the following command and press **Enter**: sc query diagtrack + + If the service is running, the result should look like the following screenshot: + + ![Result of the sc query command for sc query diagtrack](images/windefatp-sc-query-diagtrack.png) + +3. If the service **STATE** is not set to **RUNNING**, then you'll need to enter the following command and press **Enter**: sc start diagtrack + +4. A success message is displayed. Verify the change by entering the following command and press **Enter**: sc query diagtrack