Windows Update Error 0x80244011

Please try to install this update using DISM.

Follow these instructions to install an update with DISM.
  • Open the Start menu of Windows and type CMD.
  • When you see Command Prompt on the list, select the option Run as administrator.
  • Copy and paste the following command into it, and press enter. (Leave the CMD window open!)
Code: 
MD C:\WUTemp
  • Now, download the following update (KB5037768) to: C:\WUTemp - Or copy this file from the download directory to C:\WUTemp. (Important!)
    Downloadlink: KB5037768
  • Copy and paste the following commands one at a time into the command prompt and press enter after each.
Code: 
CD C:\WUTemp
EXPAND.exe windows10.0-kb5037768-x64_a627ecbec3d8dad1754d541b7f89d534a6bdec69.msu -f:* C:\WUTemp
DISM.exe /Online /Add-Package /PackagePath:C:\WUtemp\Windows10.0-KB5037768-x64.cab
  • Let me know if it says it was successful or if there are any errors. Or take a screenshot of the command prompt window and paste it into your next reply.
 
i will have to do this remotely via psexec since the machine is in use right now, ill come back to you asap.

edit: same error at 5%, find the DISM log attached.

Command Prompt:

Microsoft Windows [Version 10.0.19045.4046]
(c) Microsoft Corporation. Alle Rechte vorbehalten.

C:\WINDOWS\system32>MD C:\WUTemp

C:\WINDOWS\system32>cd C:\wutemp

C:\WUTemp>EXPAND.exe windows10.0-kb5037768-x64_a627ecbec3d8dad1754d541b7f89d534a6bdec69.msu -f:* C:\WUTemp
Microsoft (R) Dateiexpansions-Hilfsprogramm
Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten.

C:\WUTemp\Windows10.0-KB5037768-x64.cab wird zur Extrahierungswarteschlange hinzugefügt
C:\WUTemp\Windows10.0-KB5037768-x64-pkgProperties.txt wird zur Extrahierungswarteschlange hinzugefügt
C:\WUTemp\Windows10.0-KB5037768-x64_uup.xml wird zur Extrahierungswarteschlange hinzugefügt
C:\WUTemp\WSUSSCAN.cab wird zur Extrahierungswarteschlange hinzugefügt
C:\WUTemp\SSU-19041.4351-x64.cab wird zur Extrahierungswarteschlange hinzugefügt

Dateien werden erweitert ....

Erweitern der Dateien ist abgeschlossen ...
5 Dateien insgesamt

C:\WUTemp>DISM.exe /Online /Add-Package /PackagePath:C:\WUtemp\Windows10.0-KB5037768-x64.cab

Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.19041.3636

Abbildversion: 10.0.19045.4046

1 von 1 wird verarbeitet - Paket "Multiple_Packages~~~~0.0.0.0" wird hinzugefügt

[= 2.0% ]

[= 2.6% ]

[= 3.0% ]

[== 4.0% ]

[== 5.0% ]

Es ist ein Fehler aufgetreten - Fehler: 0x8007000d

Fehler: 13

Die Daten sind unzulässig.

Die DISM-Protokolldatei befindet sich unter "C:\WINDOWS\Logs\DISM\dism.log".
 

Attachments

Last edited:
I edited the post, what I did to resolve this issue in March was an inplace upgrade. However I can't do this every month cause this machine has no maintenance window for us. (machine is used for several different systems at a 24/7 workspace)
 
Rich (BB code): 
2024-05-15 12:35:15, Error                 DISM   DISM Package Manager: PID=9340 TID=9312 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x8007000d)
2024-05-15 12:35:15, Info                  DISM   DISM Package Manager: PID=9340 TID=9312 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log

Unfortunately the DISM log is not very helpful, so please attach the latest CBS logs.
 
there is a huge cbspersist log in there now with best compression I can offer this file is still over 100MB. You want me to only send you the CBS.log?

uploaded it here: test
 
Last edited:
Please upload a copy of the COMPONENTS hive, there are some hydration issue which are related to the April (preview) update KB5036979.

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Thanks I'll need to reload a VM to install this preview update to provide the next fix. So this can take some time.
 
take as much time as u need.
We are really glad someone can help us with such in depth knowledge. tbh we just registered here cause we didn't see any way out and you guys are very competent.
Allthough this is actually for my employer I appreciate you guys work - donation inc.
 
You're welcome and thankt for the kind words and your donation to Sysnative, that's much appreciated... (y)

Here's the next fix.

Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Afterwards attempt to update again using DISM and post the result. If it fails attach a new copy of the CBS logs.
 

Attachments

Rich (BB code): 
2024-05-15 15:06:56, Error                 CSI    00000616 (F) Hydration failed with error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) . Delta Type: Forward Delta , IntegrityState Valid: true , RetrievedChecksum: 231066470 , ComputedChecksum: 231066470[gle=0x80004005]
2024-05-15 15:06:56, Error                 CSI    00000617 (F) Hydration failed for component Microsoft-Windows-Deployment-Image-Servicing-Management-WinProviders, version 10.0.19041.4355, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} on file WimProvider.dll with NTSTATUS -1073283059. Matching Component = Microsoft-Windows-Deployment-Image-Servicing-Management-WinProviders, version 10.0.19041.3758, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}. FileHasForwardReverseDeltas  = false, GenerateReverseDelta = true[gle=0x80004005]

Here's the next fix for another component.


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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Afterwards attempt to update again using DISM and post the result. If it fails attach a new copy of the CBS logs.
 

Attachments

Rich (BB code): 
2024-05-15 17:27:18, Error                 CSI    00000098 (F) Hydration failed for component Microsoft-Windows-Deployment-Image-Servicing-Management-WinProviders, version 10.0.19041.4355, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} on file WimProvider.dll with NTSTATUS -1073283059. Matching Component = Microsoft-Windows-Deployment-Image-Servicing-Management-WinProviders, version 10.0.19041.3758, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}. FileHasForwardReverseDeltas  = false, GenerateReverseDelta = true[gle=0x80004005]
2024-05-15 17:27:18, Error                 CSI    00000099 (F) Matching binary WimProvider.dll missing for component Microsoft-Windows-Deployment-Image-Servicing-Management-WinProviders, version 10.0.19041.4355, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}[gle=0x80004005]

Same error, this time for the x86 component.

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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Afterwards attempt to update again using DISM and post the result. If it fails attach a new copy of the CBS logs.
 

Attachments

by any chance - can you provide a manual way to do this via cmd so that I do not have to interrupt the user every time?
I can access cmd and powershell in system context without the user knowing. would be cool to do the sfcfix via cmd.
 
You can run SFCFix.exe in the command line as follows when both files are in the same location on te remote machine.
Code: 
SFCfix.exe SFCFix.zip
 
Here's the next fix.

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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Afterwards attempt to update again using DISM and post the result. If it fails attach a new copy of the CBS logs.
 

Attachments

You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top