I have multiple Window Server 2016's (v. 1607) that when running a Windows Update, it would fail with an error "There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x8024500c)".
Looking at the Windows Update logs like ReportingEvents.log and CBS.log, it looks like it's trying to reach out - maybe outside of the WSUS.
ReportingEvents.log:
{19F548A8-36AA-4C0C-AC57-EAB8ADA38464}2020-06-16 13:15:28:042-07001147 [AGENT_DETECTION_FINISHED]101{00000000-0000-0000-0000-000000000000}00
UpdateOrchestratorSuccessSoftware SynchronizationWindows Update Client successfully detected 0 updates.
{8F1D680B-E3F3-4863-942D-C1319DC755E5}2020-06-16 13:15:28:058-07001156 [AGENT_STATUS_30]101{00000000-0000-0000-0000-000000000000}00
UpdateOrchestratorSuccessPre-Deployment CheckReporting client status.
{8061B3DA-16B9-421C-8139-A779E72822FF}2020-06-16 13:15:28:121-07001148 [AGENT_DETECTION_FAILED]101{00000000-0000-0000-0000-000000000000}08024500cUpdateOrchestratorFailureSoftware SynchronizationWindows Update Client failed to detect with error 0x8024500c.
CBS.log:
2020-06-16 12:57:21, Info CBS DWLD: Failed to begin WU search [HRESULT = 0x8024500c - Unknown Error]
2020-06-16 12:57:21, Info CBS Failed to search Windows update [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2020-06-16 12:57:21, Info CBS Failed to enumerate cloud capabilities [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
We have a GPO that specifies to a WSUS server.
The server should be checking the WSUS, right? But, running the Windows Update and checking the firewall monitor, the server 2016 looks like it's trying to reach out to Microsoft Online Update Servers. Could this be what's causing the error for 0x8024500c?
Is there a way to prevent the Server 2016's not to check online but directly to the WSUS?
Let me what you think..
Here's the GPO settings