Share via


[SOLVED] Event 1001 WindowsUpdateFailure3 P2 80070426: Windows Update not working?

Question

Wednesday, May 23, 2018 7:33 PM

I am running Window 10 Pro, version 1709 (build 16299.194) PC at home. I set up policies to notify me of updates so I can apply them myself. As a result, I see red message under

Setup -> Update & Security -> Windows Update

saying "Some settings are managed by your organization". That's fine.

The problem is that in the next "Update Status" section of the page, it indicates in red text

"Your device is at risk because it’s out of date and missing important security and quality updates. Let’s get you back on track so Windows can run more securely. Select this button to get going:"

99% of the time, clicking on "Check for Updates" button below runs for a few seconds and comes back to same error message.

On rare occasion I DO see an update coming through an installing just fine when I click on that button, but then it still reads the above message.

I found that every time it fails, in Events Log that every time I do this, I get Information event 1001 message with name WindowsUpdateFailure3 and P2 value being 80070426.

P8 value is UpdateOrchestrator about 50% of the time and other times it has other values like powershell.exe, TrustedInstaller FOD Enumerate, Update;taskhostw, etc.

P1 is always 10.0.16299.98.

Some things that I tried:

- disabled various SRP policies I had

- Made sure DNS Client and WinHTTP services are running

- Made sure Automatic proxy detection in Internet Options is checked

- Troubleshooting built into Windows (e.g. Setup -> Upgrade & Security -> Troubleshooting -> Windows Update)

- Troubleshooting tool downloaded from https://support.microsoft.com/en-us/help/10164/fix-windows-update-errors

Note: troubleshooting tools say they fixed all found issues (rebuilds the update database) but the issue still persists.

- Made sure KB4073290 (Cumulative Jan update) is applied already on my system (another thread recommended this). Now in the process of installing KB4103714 (Cumulative May update) on top of the January update (thus, I skipped Feb-April updates).

==============

Solution!!! I did not expect it, but manually applied May update (KB4103714) on top of the January update (KB4073290) seems to have cleared the issue! At first, update script was still showing the error but clicking on the button now shows green check mark and that my PC is up to date!