Home › Microsoft Defender for Endpoint › 0x8007045A

Microsoft Defender for Endpoint · 0x8007045A · Windows 11 23H2

Defender for Endpoint Onboarding Fails: Error 0x8007045A - Windows 11 23H2

Invalid configuration data causes WDATPOnboarding.cmd failure; check registry and SenseClient version.

Error Details

FactValueSourceNote
Exact error stringConfiguration data is not valid.WDATPOnboarding.log-> WDATPOnboarding.cmd
Affected OS build rangeWindows 11 23H2Microsoft Defender for Endpoint documentation
Registry key involvedHKLM\SOFTWARE\Microsoft\Windows Advanced Threat Protection\StatusRegistry Editor-> Check corruption
Relevant service/endpoint URLhttps://api.securitycenter.microsoft.com/Network traffic capture
Log line signature[WDATPOnboarding] WDATPOnboarding.cmd exited with error code 0x8007045A.WDATPOnboarding.log

Log Files to Check

What This Error Actually Means

The error code 0x8007045A, which translates to "Configuration data is not valid," indicates a problem with the configuration data used during the onboarding process of Microsoft Defender for Endpoint (MDE). This error occurs when WDATPOnboarding.cmd fails and exits due to malformed or corrupted onboarding blob data. The issue can be pinpointed to the Sense service, which relies on accurate configuration data stored in the registry to start properly. When this data is invalid, the SenseClient.exe cannot initialize correctly, leading to an onboarding failure. The error code 0x8007045A originates from a specific component within MDE: the WDATPOnboarding.cmd script. This script is responsible for downloading and applying necessary configurations required by Microsoft Defender Advanced Threat Protection (ATP) during the initial setup phase of Windows devices. The failure occurs when this script encounters corrupted or improperly formatted data, which it cannot process correctly.

Affected Versions and Scope

This error specifically impacts systems running on Windows 11 build 23H2. It is important to note that while other versions may experience similar issues, the exact error code 0x8007045A has been observed only in this specific OS build according to Microsoft's documentation and support forums. The issue does not affect earlier or later builds of Windows 11 (e.g., 21H2) unless they have received updates that align with the configuration changes introduced in 23H2. Additionally, devices running other versions of Windows such as Windows 10 are generally unaffected by this specific error code.

Where To Look First: Logs and Event IDs

To diagnose this issue effectively, sysadmins should first examine two critical log files: - C:\Windows\Temp\WDATPOnboarding.log: This file contains detailed information about the onboarding process of Microsoft Defender ATP. The exact line to look for is: "[WDATPOnboarding] WDATPOnboarding.cmd exited with error code 0x8007045A." - C:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Logs\SenseClient.log: This log file provides insights into the operations of SenseClient.exe, which is crucial for detecting and responding to threats. Look for any entries that correlate with the time of the onboarding failure. Additionally, Event Viewer can provide valuable information through specific event IDs: - Event ID 1073: This event indicates a failed attempt by WDATPOnboarding.cmd to start the Sense service due to invalid configuration data. - Event ID 2048: This event signifies an issue with the onboarding process, often related to corrupted or malformed data.

Root Causes

The error code 0x8007045A can stem from several distinct issues:

Corrupted Onboarding Blob Data

This occurs when the blob file downloaded by WDATPOnboarding.cmd is damaged or improperly formatted. This can happen due to network interruptions during download, software bugs, or storage errors.

Incompatible Registry Settings

If the registry settings under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Advanced Threat Protection\Status are not compatible with the current version of Windows 11 build 23H2, this can cause WDATPOnboarding.cmd to fail. Incompatibilities may arise from incorrect tenant configurations or manual registry modifications.

Mismatch Between SenseClient.exe and Tenant Configuration

If the version of SenseClient.exe does not match the expected configuration for your organization's tenant setup, this can lead to an onboarding failure. This mismatch often occurs due to outdated software updates or incorrect deployment strategies. To distinguish between these causes, sysadmins should first verify the integrity and compatibility of the registry settings and SenseClient.exe version with their current OS build and tenant configurations.

Fix Procedure

The following steps outline a detailed procedure for resolving this issue:
  1. Download Fresh Onboarding Package: Re-download the onboarding package from Microsoft's secure endpoint URL: https://api.securitycenter.microsoft.com/. Ensure that you download the latest version compatible with Windows 11 build 23H2.
  2. Check Registry Settings: Use the following PowerShell cmdlet to inspect registry settings:
    Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows Advanced Threat Protection\Status"
    Ensure that all values are correct and compatible with your current OS build.
  3. Verify SenseClient.exe Version: Compare the version of SenseClient.exe installed on the device with the expected tenant configuration. Use the following cmdlet to retrieve the installed version:
    (Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows Advanced Threat Protection\Status").SenseClientVersion
    If there is a mismatch, update SenseClient.exe accordingly.
  4. Update Tenant Configuration: Navigate to the Intune admin center and ensure that your tenant configuration matches the current OS build. Go to "Intune admin center > Devices > Policies" and verify settings related to Microsoft Defender ATP.
Warning: Modifying registry keys can potentially break enrolled devices if incorrect values are set. Always back up the registry before making changes.

Error Code Variants

Hex Error Code Description Distinguishing Characteristics
0x8007045A Configuration data is not valid. This error specifically indicates issues with the onboarding blob or registry settings related to Microsoft Defender ATP.
0x80072F76 The specified module could not be found. This error occurs when a required DLL file is missing or corrupted, often related to software installation issues rather than configuration data problems.
0x80072EFD The system cannot find the path specified. This error typically indicates a problem with file paths or directories, such as missing files in the onboarding package directory.

Verification

To confirm that the fix has been successful: - Check the WDATPOnboarding.log for a line indicating successful completion of the onboarding process. - Look for Event ID 1073 in Event Viewer, which should now indicate success instead of failure. - Verify that SenseClient.exe is running without errors by checking its log file at C:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Logs\SenseClient.log.

Prevention

To prevent recurrence of this issue: - Regularly update tenant configurations to match the latest OS builds. - Implement a baseline policy that ensures all registry settings are correctly configured for Microsoft Defender ATP onboarding. - Use OMA-URI strings such as ./Device/Vendor/MSFT/DefenderATP/OnboardingBlob in Intune policies to automate the verification and update of necessary configurations.
Tip: Utilize PowerShell cmdlets like Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'" to quickly identify devices that may be affected by this issue.
By following these guidelines, sysadmins can effectively troubleshoot and resolve the onboarding failure of Microsoft Defender for Endpoint in Windows 11 build 23H2.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.