deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-17 15:57:23 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

we have a version number!

Browse Source
This commit is contained in:
Marty Hernandez Avedon 2020-08-06 14:42:41 -04:00
parent 04d258141c
commit 873775f30e
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding.md
View File

@ -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 ### Ensure that Microsoft Defender Antivirus is not disabled by a policy
> [!IMPORTANT] > [!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. **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. **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: - 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
- `<Key Path="SOFTWARE\Policies\Microsoft\Windows Defender"><KeyValue Value="0" ValueKind="DWord" Name="DisableAntiVirus"/></Key>` - `<Key Path="SOFTWARE\Policies\Microsoft\Windows Defender"><KeyValue Value="0" ValueKind="DWord" Name="DisableAntiVirus"/></Key>`
> [!IMPORTANT] > [!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. - After clearing the policy, run the onboarding steps again.