It's almost certainly an environment specific setup that causes the problem. Unfortunately with these problems it's hard to diagnose what's wrong because we cannot replicate the issue. I would check the link I shared as that had some more info on this problem. Any pointers would be highly appreciated. Note: These systems are part of the domain. On 3rd, again failed on the remaining 2 and on 4th attempt, it worked on the remaining two.
#0x8024401f wsus windows 2016 update#
On second attempt, update worked on 2 and failed on remaining 2. On first attempt, update failed on all the 4 vms. Yesterday before reporting this issue, I deployed 4 vms.If I will try to run the update 10 times, after 4-5 iteration it will work.Have checked that and time is always showing correct with in the OS level. > Time is correctly set based on the deployment region and its configured via NTP servers. Because once the update failed via ansible, if I will login to the OS and start the update, its working well. Is your environment set up with a WSUS server or is it connecting directly to Microsoft Update? From Ansible's perspective we are calling the COM API to search/download/install updates and are at the mercy of what it for your response. I recommend you run Get-WindowsUpdateLog after a failed run to see if there is any more info in the log file as to why it's failing. Unfortunately there's very little help on the Windows Update documentation as to why this might occur. Is your environment set up with a WSUS server or is it connecting directly to Microsoft Update? gives 3 different reasons why this has appeared It doesn't seem to apply to the OS you've mentioned though so I doubt the KB will solve the problem. Review KB2883975 for instructions to resolve the issue. This issue occurs because Windows cannot renew the cookies for Windows Update. The error 0x80244007 refers to WU_E_PT_SOAPCLIENT_SOAPFAULT. Even if it doesn't it will at least give you a better error message.
There's a tiny chance the latest release ( 1.7.x) of this collection will fix your issue so I recommend you try that out.
0 kommentar(er)
