From eec00898f5414c3de3b6a24ad66ae67d349b3ccc Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Wed, 13 Jul 2016 19:09:13 +1000 Subject: [PATCH] add line break --- ...-onboarding-windows-defender-advanced-threat-protection.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md b/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md index 0aebce483d..59f71186dd 100644 --- a/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md @@ -56,9 +56,9 @@ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Advanced Threat Protection If the **OnboardingState** value is not set to **1**, you can use Event Viewer to review errors on the endpoint. If you configured your endpoints with a deployment tool that required a script, you can check the event viewer for the onboarding script results. - -**Check the result of the script**:
+**Check the result of the script**: + 1. Click **Start**, type **Event Viewer**, and press **Enter**. 2. Go to **Windows Logs** > **Application**.