diff --git a/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding.md b/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding.md index 89d71da554..2e1d1f2adb 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding.md +++ b/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding.md @@ -250,15 +250,15 @@ If the verification fails and your environment is using a proxy to connect to th ### Ensure that Microsoft Defender Antivirus is not disabled by a policy > [!IMPORTANT] -> The following only applies to devices that have **not** yet received the August 2020 update to Microsoft Defender Antivirus. +> The following only applies to devices that have **not** yet received the August 2020 (version 4.18.2007.8) update to Microsoft Defender Antivirus. > -> The update ensures that Microsoft Defender Antivirus cannot be disabled via a policy. +> The update ensures that Microsoft Defender Antivirus cannot be turned off on client devices via system policy. **Problem**: The Microsoft Defender ATP service does not start after onboarding. **Symptom**: Onboarding successfully completes, but you see error 577 or error 1058 when trying to start the service. -**Solution**: If your devices are running a third-party antimalware client, the Microsoft Defender ATP agent needs the Early Launch Antimalware (ELAM) driver to be enabled. You must ensure that it's not disabled in system policy. +**Solution**: If your devices are running a third-party antimalware client, the Microsoft Defender ATP agent needs the Early Launch Antimalware (ELAM) driver to be enabled. You must ensure that it's not turned off by a system policy. - Depending on the tool that you use to implement policies, you'll need to verify that the following Windows Defender policies are cleared: @@ -271,7 +271,7 @@ If the verification fails and your environment is using a proxy to connect to th - `` > [!IMPORTANT] -> The `disableAntiSpyware` setting is discontinued and will be ignored, as of the August 2020 update to Microsoft Defender Antivirus. +> The `disableAntiSpyware` setting is discontinued and will be ignored on all client devices, as of the August 2020 (version 4.18.2007.8) update to Microsoft Defender Antivirus. - After clearing the policy, run the onboarding steps again.