windowsupdatefailure3 event on server 2016

Question

windowsupdatefailure3 event on server 2016

sajid attar 6

Hi Team,

We are getting continuously below event ID 1001 in the windows 2016 application Event.

Need help how to resolve this

Current Status - server patching is happening though SCCM server only and the Internet option disable for all servers.
Please suggest how to stop these alerts from servers

"Fault bucket, type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.14393.4283
P2: 80072ee2
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 1
P7: 8024500b
P8: Device Driver Retrieval Client
P9: {9482F4B4-E343-43B6-B170-9A65BC822C77}
P10: 0

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9852.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_10.0.14393.4283_998b34747ecf2dbfce23f69b2fff66bde75ef44_00000000_cab_1add9871

Analysis symbol:
Rechecking for solution: 0
Report Id: 2d2db152-9cfc-11eb-a2bd-0050568a4a17
Report Status: 96
Hashed bucket: "

Simon Ren-MSFT 40,341 Reputation points Microsoft External Staff

2021-04-16T07:27:13.04+00:00

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

Per my personal experience, for Event ID 1000 or 1001, we should analyze the dump file to solve the issue, however the Q&A forum has limited resource about this. To get better support, it’s recommended to submit a case with Microsoft:
https://support.microsoft.com/en-us/help/28808/microsoft-store-contact-support

Thanks for your understanding.

Best regards,
Simon
Docs 15,761 Reputation points

2021-04-16T18:12:36.21+00:00

Problem signature:
P1: 10.0.14393.4283
P2: 80072ee2
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 1
P7: 8024500b
P8: Device Driver Retrieval Client
P9: {9482F4B4-E343-43B6-B170-9A65BC822C77}
P10: 0

0x80072ee2 = The operation timed out

0x8024500b = WU_E_REDIRECTOR_SLS_GENERIC_ERROR
There was an error in connecting to or parsing the response from the Service Locator Service redirector server.

https://learn.microsoft.com/en-us/windows/deployment/upgrade/windows-error-reporting
I'm not seeing a dump.

You may be able to troubleshoot the CBS and CBSPersist log files.
Simon Ren-MSFT 40,341 Reputation points Microsoft External Staff

2021-04-19T08:51:23.273+00:00

Hi,

Debugging windows log is beyond scope of forums support so if further assistance were needed you could open a request ticket with Microsoft support. Thank you for your kind understanding.
https://support.serviceshub.microsoft.com/supportforbusiness

Best regards,
Simon
Remo 10 Reputation points

2023-05-31T06:17:49.7966667+00:00

This is bad help from microsoft.

As Andrew Cirel is responsing this is helping

1 answer

Your answer

Simon Ren-MSFT 40,341 Reputation points Microsoft External Staff

2021-04-16T07:27:13.04+00:00

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

Per my personal experience, for Event ID 1000 or 1001, we should analyze the dump file to solve the issue, however the Q&A forum has limited resource about this. To get better support, it’s recommended to submit a case with Microsoft:
https://support.microsoft.com/en-us/help/28808/microsoft-store-contact-support

Thanks for your understanding.

Best regards,
Simon
Docs 15,761 Reputation points

2021-04-16T18:12:36.21+00:00

Problem signature:
P1: 10.0.14393.4283
P2: 80072ee2
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 1
P7: 8024500b
P8: Device Driver Retrieval Client
P9: {9482F4B4-E343-43B6-B170-9A65BC822C77}
P10: 0

0x80072ee2 = The operation timed out

0x8024500b = WU_E_REDIRECTOR_SLS_GENERIC_ERROR
There was an error in connecting to or parsing the response from the Service Locator Service redirector server.

https://learn.microsoft.com/en-us/windows/deployment/upgrade/windows-error-reporting
I'm not seeing a dump.

You may be able to troubleshoot the CBS and CBSPersist log files.
Simon Ren-MSFT 40,341 Reputation points Microsoft External Staff

2021-04-19T08:51:23.273+00:00

Hi,

Debugging windows log is beyond scope of forums support so if further assistance were needed you could open a request ticket with Microsoft support. Thank you for your kind understanding.
https://support.serviceshub.microsoft.com/supportforbusiness

Best regards,
Simon
Remo 10 Reputation points

2023-05-31T06:17:49.7966667+00:00

This is bad help from microsoft.

As Andrew Cirel is responsing this is helping

Answer 1

Hi ,

You don't need to do debugging or a windows dump as this problem is easy to replicate and, as far as I can tell, a flaw in Windows Server 2016.

If you don't use Windows Update to do your Windows Updates (you use another product) you will get spammed with constant WindowsUpdateFailure3 Application Error events in Windows Server 2016 filling up the logs.

If you turn Windows update off through sconfig and/or Local Group Policy Editor (Configure Automatic Updates) you still get these annoying messages.

It is frustrating that Microsoft's own methods don't work!

You can turn off the Windows Update service all together which works, but I am not sure if there are any other knock-on effects of doing this like breaking Windows Defender... Any comments?

Share via

windowsupdatefailure3 event on server 2016

1 answer

Your answer