[SOLVED] Windows 23H2 (22631.4460) - error 0x80004002 - KB5058405

[Bulbazavr]

Hello!
I have an issue with this Windows machine.
Receiving error 0x80004002
Attached screenshot after running sfc/scannow and DISM
Attached CBS logs and Components report.
Thanks a lot!

 

[Windows Update Bot]

Hi @Bulbazavr,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[Maxstar]

Hi and welcome to Sysnative,

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

 

[Bulbazavr]

Hi @Maxstar
Thanks for your reply. Attaching the fixlog. I removed the username and folder name in the description field in the beginning for safety reasons.

 

[Maxstar]

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.

DISM /online /cleanup-image /RestoreHealth

 

[Maxstar]

Hi,

Any updates on this issue?

 

[Bulbazavr]

Hi @Maxstar

DISM got stuck at 54%
Attaching sfcfix and CBS.
I closed CMD and am trying again now.

 

[Bulbazavr]

We ran DISM again and it completed at 100%.
I will try to update the system now.

 

[Maxstar]

Hi,

Great, let me know the result.

 

[Bulbazavr]

Hi @Maxstar, thanks a lot, it worked.
I see that in my case, you replace only Servicingstack (SSU?).. When building this .zip folder, are you taking the servicing stack from the WinSxS folder on a working machine? Does it mean you build a VM for every version that you fix?
Also, if you ever question the root cause of the corruption, what would you look into?

 

[Maxstar]

Hi,

You're welcome. Glad to hear the issue has been resolved.

Yes, I'm running multiple VM's to use as source, but I have also local repositories with replacement files from unpacked SSUs from the MSU-Package etc.
See also this guide: Troubleshooting 0x800f081f / 0x800f0982 Error

Also, if you ever question the root cause of the corruption, what would you look into?

That depends entirely on the issue and sometimes you'll need to update with Process Monitor running to find the corruption...