mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-08 02:27:22 +00:00
Merge remote-tracking branch 'refs/remotes/origin/atp-ELAM'
This commit is contained in:
jcaparas
commit
38340bcf46
BIN
windows/keep-secure/images/atp-disableantispyware-regkey.png
Normal file
BIN
windows/keep-secure/images/atp-disableantispyware-regkey.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 49 KiB |
@ -113,4 +113,4 @@ When Windows Defender is not the active antimalware in your organization and you
|
||||
## Windows Defender Early Launch Antimalware (ELAM) driver is enabled
|
||||
If you're running Windows Defender as the primary antimalware product on your endpoints, the Windows Defender ATP agent will successfully onboard.
|
||||
|
||||
If you're running a third-party antimalware client and use Mobile Device Management solutions or System Center Configuration Manager (current branch) version 1606, you'll need to ensure that the Windows Defender ELAM driver is enabled. For more information on how to validate and enable the Windows Defender ELAM driver see, [Ensure the Windows Defender ELAM driver is enabled](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md#ensure-the-windows-defender-elam-driver-is-enabled).
|
||||
If you're running a third-party antimalware client and use Mobile Device Management solutions or System Center Configuration Manager (current branch) version 1606, you'll need to ensure that the Windows Defender ELAM driver is enabled. For more information, see [Ensure that Windows Defender is not disabled by policy](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md#ensure-that-windows-defender-is-not-disabled-by-a-policy).
|
||||
|
||||
@ -65,7 +65,7 @@ Event ID | Error Type | Resolution steps
|
||||
5 | Offboarding data was found but couldn't be deleted | Check the permissions on the registry, specifically ```HKLM\SOFTWARE\Policies\Microsoft\Windows Advanced Threat Protection```.
|
||||
10 | Onboarding data couldn't be written to registry | Check the permissions on the registry, specifically<br> ```HKLM\SOFTWARE\Policies\Microsoft\Windows Advanced Threat```.<br>Verify that the script was ran as an administrator.
|
||||
15 | Failed to start SENSE service |Check the service status (```sc query sense``` command). Make sure it's not in an intermediate state (*'Pending_Stopped'*, *'Pending_Running'*) and try to run the script again (with administrator rights).
|
||||
15 | Failed to start SENSE service | If the message of the error is: System error 577 has occurred. You need to enable the Windows Defender ELAM driver, see [Ensure the Windows Defender ELAM driver is enabled](#ensure-the-windows-defender-elam-driver-is-enabled) for instructions.
|
||||
15 | Failed to start SENSE service | If the message of the error is: System error 577 has occurred. You need to enable the Windows Defender ELAM driver, see [Ensure that Windows Defender is not disabled by a policy](#ensure-that-windows-defender-is-not-disabled-by-a-policy) for instructions.
|
||||
30 | The script failed to wait for the service to start running | The service could have taken more time to start or has encountered errors while trying to start. For more information on events and errors related to SENSE, see [Review events and errors on endpoints with Event viewer](event-error-codes-windows-defender-advanced-threat-protection.md).
|
||||
35 | The script failed to find needed onboarding status registry value | When the SENSE service starts for the first time, it writes onboarding status to the registry location<br>```HKLM\SOFTWARE\Microsoft\Windows Advanced Threat Protection\Status```.<br>The script failed to find it after several seconds. You can manually test it and check if it's there. For more information on events and errors related to SENSE, see [Review events and errors on endpoints with Event viewer](event-error-codes-windows-defender-advanced-threat-protection.md).
|
||||
40 | SENSE service onboarding status is not set to **1** | The SENSE service has failed to onboard properly. For more information on events and errors related to SENSE, see [Review events and errors on endpoints with Event viewer](event-error-codes-windows-defender-advanced-threat-protection.md).
|
||||
@ -124,7 +124,7 @@ If the deployment tools used does not indicate an error in the onboarding proces
|
||||
- [Ensure the telemetry and diagnostics service is enabled](#ensure-the-telemetry-and-diagnostics-service-is-enabled)
|
||||
- [Ensure the service is set to start](#ensure-the-service-is-set-to-start)
|
||||
- [Ensure the endpoint has an Internet connection](#ensure-the-endpoint-has-an-internet-connection)
|
||||
- [Ensure the Windows Defender ELAM driver is enabled](#ensure-the-windows-defender-elam-driver-is-enabled)
|
||||
- [Ensure that Windows Defender is not disabled by a policy](#ensure-that-windows-defender-is-not-disabled-by-a-policy)
|
||||
|
||||
|
||||
### View agent onboarding errors in the endpoint event log
|
||||
@ -222,98 +222,31 @@ To ensure that sensor has service connectivity, follow the steps described in th
|
||||
|
||||
If the verification fails and your environment is using a proxy to connect to the Internet, then follow the steps described in [Configure proxy and Internet connectivity settings](configure-proxy-internet-windows-defender-advanced-threat-protection.md) topic.
|
||||
|
||||
### Ensure the Windows Defender ELAM driver is enabled
|
||||
If your endpoints are running a third-party antimalware client, the Windows Defender ATP agent needs the Windows Defender Early Launch Antimalware (ELAM) driver to be enabled.
|
||||
### Ensure that Windows Defender is not disabled by a policy
|
||||
**Problem**: The Windows Defender ATP service does not start after onboarding.
|
||||
|
||||
**Check the ELAM driver status:**
|
||||
**Symptom**: Onboarding successfully completes, but you see error 577 when trying to start the service.
|
||||
|
||||
1. Open a command-line prompt on the endpoint:
|
||||
**Solution**: If your endpoints are running a third-party antimalware client, the Windows Defender ATP agent needs the Windows Defender Early Launch Antimalware (ELAM) driver to be enabled. You must ensure that it's not disabled in system policy.
|
||||
|
||||
a. Click **Start**, type **cmd**, and select **Command prompt**.
|
||||
- Depending on the tool that you use to implement policies, you'll need to verify that the following Windows Defender policies are set to ```0``` or that the settings are cleared:
|
||||
|
||||
2. Enter the following command, and press Enter:
|
||||
- ```DisableAntiSpyware```
|
||||
- ```DisableAntiVirus```
|
||||
|
||||
For example, in Group Policy:
|
||||
|
||||
```<Key Path="SOFTWARE\Policies\Microsoft\Windows Defender"><KeyValue Value="0" ValueKind="DWord" Name="DisableAntiSpyware"/></Key>
|
||||
```
|
||||
sc qc WdBoot
|
||||
```
|
||||
If the ELAM driver is enabled, the output will be:
|
||||
- After clearing the policy, run the onboarding steps again on the endpoint.
|
||||
|
||||
```
|
||||
[SC] QueryServiceConfig SUCCESS
|
||||
- You can also check the following registry key values to verify that the policy is disabled:
|
||||
|
||||
SERVICE_NAME: WdBoot
|
||||
TYPE : 1 KERNEL_DRIVER
|
||||
START_TYPE : 0 BOOT_START
|
||||
ERROR_CONTROL : 1 NORMAL
|
||||
BINARY_PATH_NAME : \SystemRoot\system32\drivers\WdBoot.sys
|
||||
LOAD_ORDER_GROUP : Early-Launch
|
||||
TAG : 0
|
||||
DISPLAY_NAME : Windows Defender Boot Driver
|
||||
DEPENDENCIES :
|
||||
SERVICE_START_NAME :
|
||||
```
|
||||
If the ELAM driver is disabled the output will be:
|
||||
```
|
||||
[SC] QueryServiceConfig SUCCESS
|
||||
1. Open the registry ```key HKEY_LOCAL_MACHINE\ SOFTWARE\Policies\Microsoft\Windows Defender```.
|
||||
2. Find the value ```DisableAntiSpyware```.
|
||||
3. Ensure that the value is set to 0.
|
||||
|
||||
SERVICE_NAME: WdBoot
|
||||
TYPE : 1 KERNEL_DRIVER
|
||||
START_TYPE : 0 DEMAND_START
|
||||
ERROR_CONTROL : 1 NORMAL
|
||||
BINARY_PATH_NAME : \SystemRoot\system32\drivers\WdBoot.sys
|
||||
LOAD_ORDER_GROUP : _Early-Launch
|
||||
TAG : 0
|
||||
DISPLAY_NAME : Windows Defender Boot Driver
|
||||
DEPENDENCIES :
|
||||
SERVICE_START_NAME :
|
||||
```
|
||||
|
||||
#### Enable the ELAM driver
|
||||
|
||||
1. Open an elevated PowerShell console on the endpoint:
|
||||
|
||||
a. Click **Start**, type **powershell**.
|
||||
|
||||
b. Right-click **Command prompt** and select **Run as administrator**.
|
||||
|
||||
2. Run the following PowerShell cmdlet:
|
||||
|
||||
```text
|
||||
'Set-ExecutionPolicy -ExecutionPolicy Bypass’
|
||||
```
|
||||
3. Run the following PowerShell script:
|
||||
|
||||
```text
|
||||
Add-Type @'
|
||||
using System;
|
||||
using System.IO;
|
||||
using System.Runtime.InteropServices;
|
||||
using Microsoft.Win32.SafeHandles;
|
||||
using System.ComponentModel;
|
||||
|
||||
public static class Elam{
|
||||
[DllImport("Kernel32", CharSet=CharSet.Auto, SetLastError=true)]
|
||||
public static extern bool InstallELAMCertificateInfo(SafeFileHandle handle);
|
||||
|
||||
public static void InstallWdBoot(string path)
|
||||
{
|
||||
Console.Out.WriteLine("About to call create file on {0}", path);
|
||||
var stream = File.Open(path, FileMode.Open, FileAccess.Read, FileShare.Read);
|
||||
var handle = stream.SafeFileHandle;
|
||||
|
||||
Console.Out.WriteLine("About to call InstallELAMCertificateInfo on handle {0}", handle.DangerousGetHandle());
|
||||
if (!InstallELAMCertificateInfo(handle))
|
||||
{
|
||||
Console.Out.WriteLine("Call failed.");
|
||||
throw new Win32Exception(Marshal.GetLastWin32Error());
|
||||
}
|
||||
Console.Out.WriteLine("Call successful.");
|
||||
}
|
||||
}
|
||||
'@
|
||||
|
||||
$driverPath = $env:SystemRoot + "\System32\Drivers\WdBoot.sys"
|
||||
[Elam]::InstallWdBoot($driverPath)
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -64,6 +64,12 @@ EU region:
|
||||
|
||||
See the topic [Review events and errors on endpoints with Event Viewer](event-error-codes-windows-defender-advanced-threat-protection.md) for a list of event IDs that are reported by the Windows Defender ATP service. The topic also contains troubleshooting steps for event errors.
|
||||
|
||||
### Windows Defender ATP service fails to start after a reboot and shows error 577
|
||||
|
||||
If onboarding endpoints successfully completes but Windows Defender ATP does not start after a reboot and shows error 577, check that Windows Defender is not disabled by a policy.
|
||||
|
||||
For more information, see [Ensure that Windows Defender is not disabled by policy](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md#ensure-that-windows-defender-is-not-disabled-by-a-policy).
|
||||
|
||||
|
||||
### Related topic
|
||||
- [Troubleshoot Windows Defender Advanced Threat Protection onboarding issues](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user