Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | WU_E_AU_NOSERVICE_OFFTIMERS | WindowsUpdate.log | -> indicates the issue |
| Affected build range | Windows 11 23H2 | System Information | |
| Registry key involved | HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate | Registry Editor | -> WSUS URL |
| Relevant service/endpoint URL | <WSUS server URL> | Group Policy Management Console | |
| Log line signature | 0x8024a105 WU_E_AU_NOSERVICE_OFFTIMERS | WindowsUpdate.log | -> indicates the issue |
Log Files to Check
C:\Windows\WindowsUpdate.logC:\Windows\System32\winevt\Logs\Microsoft-Windows-WindowsUpdateClient%4Operational.evtx
What This Error Actually Means
The error code 0x8024a105, also known as WU_E_AU_NOSERVICE_OFFTIMERS, is raised by the Automatic Updates (AU) component of Windows Update when it fails to apply metadata or if the self-update mechanism has broken. This can occur due to a variety of reasons including changes in WSUS server configuration without proper client re-registration or misconfigurations related to proxy settings that prevent the update client from accessing necessary endpoints. This error is particularly significant because it indicates an issue with the core functionality of Windows Update, which is essential for maintaining system integrity and security. The AU component relies on a continuous loop of metadata updates and self-updates to ensure that all systems are kept up-to-date with the latest patches and features provided by Microsoft.Affected Versions and Scope
This error primarily affects Windows 11, specifically build 23H2. It is also relevant for any environment where WSUS (Windows Server Update Services) is used to manage updates centrally. The issue does not affect systems that are directly connected to Microsoft's public update servers without a WSUS intermediary. The scope of this error is limited to environments where Windows Update clients are configured to use a WSUS server, which can include both on-premises and hybrid cloud configurations. It is important to note that the error will not appear in scenarios where systems are set to receive updates directly from Microsoft's servers without any intermediary update services.Where To Look First: Logs and Event IDs
To diagnose this issue, start by examining the WindowsUpdate.log file located atC:\Windows\WindowsUpdate.log. This log contains detailed information about the operations performed by the Windows Update service. You should look for lines containing the exact error string "0x8024a105 WU_E_AU_NOSERVICE_OFFTIMERS" to pinpoint where and when the issue occurred.
Additionally, inspect the Operational event logs related to Windows Update in C:\Windows\System32\winevt\Logs\Microsoft-Windows-WindowsUpdateClient%4Operational.evtx. These logs provide a broader context around the error, including timestamps and additional details that can help identify the root cause.
Event IDs 7031 and 7036 are particularly relevant in this scenario. Event ID 7031 indicates when Windows Update has started or stopped, while Event ID 7036 provides information about errors encountered during the update process. These events can be queried using PowerShell cmdlets such as Get-WinEvent -LogName "Microsoft-Windows-WindowsUpdateClient/Operational" -FilterXPath "*[System[(EventID=7031 or EventID=7036)]]".
Root Causes
WSUS Server URL Changed Without Client Re-Registration
This is a common cause of the 0x8024a105 error. If the WSUS server's URL has been changed, clients must be reconfigured to point to the new server address. This can happen during migrations or when updating infrastructure.Proxy WPAD Misconfiguration Blocking WU Client
Another frequent cause is misconfigurations in proxy settings that prevent the Windows Update client from accessing its required endpoints. If a Web Proxy Auto-Discovery (WPAD) configuration is incorrect, it may block necessary traffic to WSUS or Microsoft's update servers.Expired Self-Update Sequence
The self-update sequence of the Windows Update client can expire if there are prolonged periods without updates being applied successfully. This expiration prevents further updates from occurring until the issue is resolved.Fix Procedure
- Verify WSUS URL via Group Policy: Navigate to the Group Policy Management Console and check under Computer Configuration > Administrative Templates > Windows Components > Windows Update for any policies that might have been updated or misconfigured.
- Run wuauclt commands: Open an elevated command prompt and execute
wuauclt /resetauthorization, followed bywuauclt /detectnow. This will reset the client's authorization status and trigger a new detection cycle. - Check WindowsUpdate.log for context: Review the WindowsUpdate.log file around the time of the error to understand what was happening when 0x8024a105 occurred. Look specifically at entries related to metadata application or self-updates.
Warning: Running certain commands, such as those that reset authorization settings, can temporarily disrupt the update process and may cause issues with enrolled devices until they are re-authorized.
Error Code Variants
| Error Code | Description | Distinguishing Features |
|---|---|---|
| 0x8024a105 (WU_E_AU_NOSERVICE_OFFTIMERS) | AU service fails to apply metadata or self-update mechanism is broken. | Error occurs during AU operations, often after WSUS changes. |
| 0x8024a106 (WU_E_AU_NOSERVICE_OFFLINE) | AU service fails due to offline status or network issues. | Error occurs when the system is disconnected from the internet. |
Verification
To verify that the issue has been resolved, monitor the WindowsUpdate.log for successful detection and installation cycles following the fix procedure. Look for entries indicating a new authorization attempt (e.g.,"[AU] Authorization: AU service is initializing.") and subsequent detections without errors.
Additionally, check the status of managed devices in the Intune admin center > Devices > Managed Devices to ensure that they are not reporting any update-related issues.
Prevention
To prevent recurrence of this error, it's crucial to maintain proper documentation and communication regarding changes made to WSUS server configurations. Implement a policy where all clients are re-registered after any significant updates or migrations involving the WSUS environment. Ensure that proxy settings are correctly configured across your network, especially if WPAD is in use. Regularly review and test these configurations to ensure they do not inadvertently block necessary update traffic.Tip: Use PowerShell cmdlets like Get-WinEvent -LogName "Microsoft-Windows-WindowsUpdateClient/Operational" | Where-Object { $_.Id -eq 7031 } to quickly filter and analyze relevant event logs for troubleshooting.