[SOLVED] Windows 2016 DC update fail - Error 0x80070005

[benum47]

Update KB5043051 failing

I followed the steps on the Windows Update Forum Posting Instructions; CBS and Component scanner files attached.

Thanks

 

[benum47]

I understand that you have a high volume but is there any chance you could take a look at this one? This server is unable to apply the September security update and now the October update is ready.

Thanks for all that you do! (second donation incoming)

 

[Maxstar]

Hi,

Which security software is installed on this server?
Please provide also the following log.

Export the Windows Update log

• Right-click on the Start button and click Windows PowerShell (Admin).
• Copy and paste the following command into it, press enter afterwards

Get-WindowsUpdateLog

• Wait for the message "WindowsUpdate.log written to C:\Users\<username>\Desktop\WindowsUpdate.log".
• Attach the logfile WindowsUpdate.log to your next reply.

 

[benum47]

Hello! please find requested file attached. I meant security as in the Microsoft Security updates like KB5043051

 

[Maxstar]

Hi,

Thanks, but I meant which Security Software is installed on this server because the access denied issue!

 

[benum47]

Microsoft Defender, it should have the same policy as all our other servers but this is the only one that failed KB5043051.
This is one of three servers that failed updates back in August that you assisted with (corrput DRIVERS; [SOLVED] - Windows update errors on 3 systems, 2 fixed by ComponentsScanner.exe)

 

[Maxstar]

2024/10/17 06:20:48.2493171 1164  6512  Agent           Caller UpdateOrchestrator failed to opt in to service 7971f918-a847-4430-9279-4a52d1efe18d, hr=0X8024500C
2024/10/17 06:20:48.2498851 1164  6512  Misc            EP: error: 0x8024500C : - failed to get SLS data
2024/10/17 06:20:48.2498885 1164  6512  Misc            Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Client/Server URL, error = 0x8024500C
2024/10/17 06:20:48.2498894 1164  6512  ProtocolTalker  PTError: 0x8024500c
2024/10/17 06:20:48.2498981 1164  6512  ProtocolTalker  Initialization failed for Protocol Talker Context 0x8024500c

1. It seems this server is connected to an WSUS server, (0x8024500C) - Connections to the redirector server are disallowed by managed policy.
2. Are you able to update this server when it's completely disconnected from the WSUS server?

 

[benum47]

Interesting, I will try this. I will report back

 

[Maxstar]

Great, let me know the result...

 

[benum47]

It looks like it was SMB 1.0
The WSUS server had a change applied to no longer accept SMB 1.0 and this server was trying to connect with it.
Updates now successfully applied

Thanks!

 

[Maxstar]

Hi,

You're welcome. Glad you have found the issue to resolve this problem...
I will mark this thread as solved.