4 4dro1d Active member Joined Mar 23, 2023 Posts 32 Mar 23, 2023 #1 Hello, I am currently having problems installing Windows updates on a Windows Server 2022. Installed Build: 20348.1006 The error message I receive after the installation is: 0x8007000d. In this regard, I have also already tried some standard troubleshooting: 1. Running the Windows Update troubleshooter. 2. A manual installation via the Windows Update Catalog. 3. Renaming the SoftwareDistribution and Catroot2 folders under C:\Windows\System32\ and then restarting the Windows Update services. 3. sfc /scannow 4. Repairing the image via DISM using the Windows Server 2022 ISO. None of the actions have been successful so far. Attached my COMPONENTS hive and Exported CBS (Component Based Servicing) Registry hive. I think it could be the same error in this thread: [SOLVED] - Problem with Windows Updates - 0x8007000d ERROR_INVALID_DATA Attachments ComponentBasedServicing.zip 1 MB · Views: 2 COMPONENTS.zip 12.1 MB · Views: 2
Hello, I am currently having problems installing Windows updates on a Windows Server 2022. Installed Build: 20348.1006 The error message I receive after the installation is: 0x8007000d. In this regard, I have also already tried some standard troubleshooting: 1. Running the Windows Update troubleshooter. 2. A manual installation via the Windows Update Catalog. 3. Renaming the SoftwareDistribution and Catroot2 folders under C:\Windows\System32\ and then restarting the Windows Update services. 3. sfc /scannow 4. Repairing the image via DISM using the Windows Server 2022 ISO. None of the actions have been successful so far. Attached my COMPONENTS hive and Exported CBS (Component Based Servicing) Registry hive. I think it could be the same error in this thread: [SOLVED] - Problem with Windows Updates - 0x8007000d ERROR_INVALID_DATA
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,362 Location The Netherlands Mar 24, 2023 #2 Hi and welcome to Sysnative, Upload a copy of the CBS folder Open Windows Explorer and browse to the C:\Windows\Logs folder. Right-click on the CBS folder and choose Send to > Compressed (zipped) folder. Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?" Click on the Yes button here. Attach the file CBS.zip to your next reply.
Hi and welcome to Sysnative, Upload a copy of the CBS folder Open Windows Explorer and browse to the C:\Windows\Logs folder. Right-click on the CBS folder and choose Send to > Compressed (zipped) folder. Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?" Click on the Yes button here. Attach the file CBS.zip to your next reply.
4 4dro1d Active member Joined Mar 23, 2023 Posts 32 Mar 24, 2023 #3 Hello Maxstar, thank you for your help. I uploaded the CBS.zip to wetransfer: CBS.zip It's too large for the forum.
Hello Maxstar, thank you for your help. I uploaded the CBS.zip to wetransfer: CBS.zip It's too large for the forum.
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,362 Location The Netherlands Mar 24, 2023 #4 Hi, 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. Code: DISM /online /cleanup-image /RestoreHealth Attachments SFCFix.zip 8.8 KB · Views: 21
Hi, 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. Code: DISM /online /cleanup-image /RestoreHealth
4 4dro1d Active member Joined Mar 23, 2023 Posts 32 Mar 24, 2023 #5 Hi, thank you. After step 1+2, Windows Update could be installed successfully. Can you explain the fix to me? I had invested many hours before - also with expensive Microsoft Business Support who finally recommended a reinstallation.
Hi, thank you. After step 1+2, Windows Update could be installed successfully. Can you explain the fix to me? I had invested many hours before - also with expensive Microsoft Business Support who finally recommended a reinstallation.
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,362 Location The Netherlands Mar 24, 2023 #6 Hi, You're welcome. Glad to hear the latest LCU installed without any issues this time... As you pointed out in the first post, Windows Update failed with 0x8007000D (Invalid Data). So I have replaced the corrupted payload file with a known good copy from my Server 2022 VM. Rich (BB code): 2023-03-24 06:18:17, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-terminalserver-adm_31bf3856ad364e35_10.0.20348.1_none_0be345596266e825\TerminalServer.admx 2023-03-24 06:18:17, Info CBS Repair failed: Missing replacement payload.
Hi, You're welcome. Glad to hear the latest LCU installed without any issues this time... As you pointed out in the first post, Windows Update failed with 0x8007000D (Invalid Data). So I have replaced the corrupted payload file with a known good copy from my Server 2022 VM. Rich (BB code): 2023-03-24 06:18:17, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-terminalserver-adm_31bf3856ad364e35_10.0.20348.1_none_0be345596266e825\TerminalServer.admx 2023-03-24 06:18:17, Info CBS Repair failed: Missing replacement payload.
4 4dro1d Active member Joined Mar 23, 2023 Posts 32 Mar 24, 2023 #7 Thank you very much. How can something like this happen? The problems have already appeared a few weeks after Server 2022 installation.
Thank you very much. How can something like this happen? The problems have already appeared a few weeks after Server 2022 installation.
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,362 Location The Netherlands Mar 24, 2023 #8 There are several reasons for these kind of corruptions, although it is difficult to ascertain what the exact cause was. What we do know is that it is a well-known problem, see this thread for a more detailed information about corrupt payload files and how to repair them.
There are several reasons for these kind of corruptions, although it is difficult to ascertain what the exact cause was. What we do know is that it is a well-known problem, see this thread for a more detailed information about corrupt payload files and how to repair them.