Windows Update Error 0x80244011

[Nirmata]

Hey guys,

Windows 10 Enterprise 22H2 Lenovo Workstation fully patched and updated here but can't install Windows CU Updates since last month (CU3)
Error Screenshot 1 - then I vleaned Windows Update with Wureset completely.
After I get another error -> Screenshot 2. He downloads the file from wsus and tries to install and aborts at 5%



I attached all CBS logs and ComponentScanner.txt

 

[Nirmata]

push for visability if not allowed, just delete.

 

[Maxstar]

Hi and welcome to Sysnative,

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[Nirmata]

DISM ran fine, logs in attachement. Will try to install CU5 tomorrow when machine is available and reply here. Thx so far. From the log I found you set some permissions new that I found in the above CBS.log as well. Was it regarding the ownership?

 

[Maxstar]

Great, let me know the result. If the update fails attach a new copy of the CBS logs.

 

[Nirmata]

Update fails with the same error. CBS logs in the attachement.

 

[Maxstar]

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.

 

[Nirmata]

here we go, thx for the support

 

[Maxstar]

• Click the Start button and in the search box, type Command Prompt
• When you see Command Prompt on the list, right-click on it and select Run as administrator.
• Copy and paste the following command line and press Enter.

reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" "%userprofile%\desktop\RegExp.txt"

• When finished, a logfile called RegExp.txt is saved on your desktop.
• Post the logfile as attachment in your next reply.

 

[Nirmata]

Changed the WUServer entry (gpdr) These GPO's do work on 1200 other clients in the domain, btw.

 

[Maxstar]

The error you see means that a WUServer policy value is missing in the registry. Which changes do you have made?

 

[Nirmata]

honestly, none. If you are referring to the change that I posted above: I just deleted the dns name of our wuserver from that log for privacy reasons. In these two fields were I put a XXX you would normally find the wuserver.

 

[Maxstar]

Can you please provide the same REG export from a system without issues, just to compare all the values.

 

[Nirmata]

you are right. However i did find 2 more entries in the broken machine compared to the working one, no missing things...

rsop of that machine/user also shows the same working gpo...weird.

Tried a freshly deployed machine now with same gpo - difference is only in the value for detectionfrequency which is not leading in the right direction I guess? Sorry my mistake, working_regexp is a machine with special WU Settings.

 

[Maxstar]

There are a few different values set on the broken, system. I would first try to delete all the values and then import the keys from a working machine to see what happens.

 

[Nirmata]

if I delete the AU hive and then do a gpupdate it should set the standard values, can I try it that way?

 

[Maxstar]

Yes, you can try that as well.

 

[Nirmata]

k settings are the same now. You recommend deleting the update store first or just try to run the cu installation?

 

[Maxstar]

Yes I would definitely clear the Software Distribution folder, just to be sure there are no corrupted items and/or incomplete packages...

 

[Nirmata]

same error, same problem - very nasty machine this is...