[SOLVED] Update Error on 0x8007000d on server 2022 21h2 03

[Gary R]

How things get corrupted is open to a whole bunch of reasons, but the real trouble begins because of the limitations of the tools that Microsoft supply for tracing and repairing them when they occur.

CBS (Component Based Servicing) has a nasty habit of only revealing things a bit at a time, so you never get to see everything at once. So it's only when you've patched one thing, that others appear. That and the fact that you're patching things manually, and that takes time, whereas Windows Updating Engine works a whole lot faster when it screws things up.

It's frustrating I know, but all we can do is work with what we've got.

Just so you know, the DISM log isn't actually very helpful most of the time, so unless I ask for it, there's no need for you to supply it.

Anyway, enough said, I'm looking over your logs now, and will get back to you as soon as I can.

 

[Gary R]

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFixScript.txt and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFixScript.txt 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
• Open the file, then copy and paste its content in your next reply.

Next ...

• Click Search button and type Command Prompt
• From the results, right click on the Command Prompt icon, and select Run as administrator
• A Command Window will open.
• Copy paste the command below into it, then press Enter
• Dism /Online /Cleanup-Image /RestoreHealth
• Once DISM has finished running ...
  • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
• If the file is too large, upload it to a file sharing service, and post me the link.
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Can you also post me a new copy of your COMPONENTS hive file ...

• 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.
• The file will likely be too large to upload here, if so please upload to a file sharing service.
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file

 

[Yaza]

Thank you for sharing the details. Attached you'll find the requested files

 

[Gary R]

OK, your latest CBS.log (like the last one) is flagging a couple of manifests that we've already patched.

2024-09-26 18:45:57, Info                  CBS    Checking System Update Readiness.
2024-09-26 18:45:57, Info                  CBS   
2024-09-26 18:45:57, Info                  CBS    (p)    CSI Manifest Corrupt    (n)            amd64_microsoft-onecore-a..e-merged-deployment_31bf3856ad364e35_10.0.20348.2582_none_63ed7700d7d70bdb
2024-09-26 18:45:57, Info                  CBS    Repair failed: Missing replacement manifest.
2024-09-26 18:45:57, Info                  CBS    (p)    CSI Manifest Corrupt    (n)            amd64_microsoft-windows-s..tures-deployment070_31bf3856ad364e35_10.0.20348.2582_none_8fda33e80965eb55
2024-09-26 18:45:57, Info                  CBS    Repair failed: Missing replacement manifest.
2024-09-26 18:45:57, Info                  CBS

I've checked through your latest COMPONENTS hive, and as far as I can see all the Registry entries that relate to those two files are present (we patched them earlier), so now I need to ascertain whether the manifest files themselves are still present (we patched them as well, but I have known protective programs to remove things that were patched).

So .....

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFixScript.txt and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFixScript.txt 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
• Open the file, then copy and paste its content in your next reply.

Getting late here, and I've had a pretty busy day, so will probably see your reply in the morning.

 

[Yaza]

Good morning, Gary. Here we go again.

 

[Gary R]

So, for some reason it appears that the 2 manifest files we replaced earlier are now not present on your machine. Why that is I couldn't say, but I propose that we add them again and see where that gets us.

So ....

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all programs.
• 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
• Open the file, then copy and paste its content in your next reply.

Next ...

• Click Search button and type Command Prompt
• From the results, right click on the Command Prompt icon, and select Run as administrator
• A Command Window will open.
• Copy paste the command below into it, then press Enter
• Dism /Online /Cleanup-Image /RestoreHealth
• Once DISM has finished running ...
  • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
• If the file is too large, upload it to a file sharing service, and post me the link.
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

 

[Yaza]

Mhh interesting I checked Microsoft Defender for Endpoint but it did not block anything. IMHO there are no other tools are running that could interfere with it.

DISM now ran without an error.

 

[Gary R]

Please try updating again.

If successful please let me know.

If not, please post your latest CBS.log


Going to be out for the next few hours, so it will be sometime this afternoon before I see your reply.

 

[Yaza]

It worked I was finally able to update the system. Thank you. Two to go

 

[Gary R]

You're welcome, glad we were able to get there in the end.

I'll mark this topic as Solved then.

 

[Yaza]

Yes resolve it. I was accepted in the academy btw ;-)

 

[Gary R]

Excellent, look forward to seeing how you get on with the course. It's fun.

Saw your other topic by the way, but I know I'm going to be tied up with things for the next few days, so I've left it for one of the other helpers to assist you with it, as you'll get it attended to quicker that way.

If you haven't had any help with it by Tuesday please let me know, and I'll see what I can do.