diff --git a/windows/keep-secure/other-troubleshooting.md b/windows/keep-secure/other-troubleshooting.md
index 66eae361c4..709af442ea 100644
--- a/windows/keep-secure/other-troubleshooting.md
+++ b/windows/keep-secure/other-troubleshooting.md
@@ -22,25 +22,6 @@ You might need to troubleshoot the onboarding process if you encounter issues.
 
 If you have completed the endpoint onboarding process and don't see endpoints in the [Machines view](investigate-machines-windows-defender-advanced-threat-protection.md) after 20 minutes, it might indicate an endpoint onboarding or a connectivity problem.
 
-### Ensure that the endpoint is onboarded successfully
-If the endpoints aren't reporting correctly, you might need to check that the Windows Defender Advanced Threat Protection service was successfully onboarded on the endpoint.
-
-**Check the onboarding state in Registry:**
-
-1. Click **Start**.
-
-2. Type **Run**.
-
-3. From the **Run** dialog box, type **regedit** and press **Enter**.
-
-4. In the **Registry Editor** navigate to the Status key under **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Advanced Threat Protection**.
-
-5. Check that the **OnboardingState** value is set to **1**.
-
-    ![Image of OnboardingState status in Registry Editor](images/onboardingstate.png)
-
-    If the **OnboardingState** value is not set to **1**, follow the instructions on **Identifying and addressing onboarding issues**.
-    
 
 ### Ensure that the Windows Defender ATP endpoint has internet connection