[SOLVED] Cannot install 2025-05 update KB058385 21h2

daemenseth

Contributor
Joined
Feb 17, 2024
Posts
26
Cannot install update 2025-05 update KB5058385 21h2

Create the asked files.

This is error code in windows update

Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x8007000d)
 

Attachments

Last edited:
Hi @daemenseth,

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
 
Looks like same as this topic from @

KatkineServer

I have also sql and azure arc
 
I solved a lot of errors with sfcfix tool.
But everytime when I try to install the kb I get new errors to solve.
Is there a more easy way to find all errors instead of fixing one and trying again?
 
Hi and welcome to Sysnative,

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.
 
@Maxstar thx for you reply
In the attachment the components file
I also attached 2 latest cbs files.
I think I have solved most errors Patch installation takes longer but Now I see


Code:
2025-05-28 23:20:37, Info                  CBS    Setting ExecuteState key to: ExecuteStateNone
2025-05-28 23:20:37, Info                  CBS    Clearing HangDetect value
2025-05-28 23:20:37, Info                  CBS    Saved last global progress. Current: 0, Limit: 1, ExecuteState: ExecuteStateNone
2025-05-28 23:20:37, Info                  CBS    Configured poqexec to pend to SetupExecute.
2025-05-28 23:20:37, Info                  CBS    Exec: Restoring driver operations because of a CSI commit failure.
2025-05-28 23:20:37, Error                 CBS    Exec: Failed to pend CSI transaction because transactions cannot be merged: 0. [HRESULT = 0x80070308 - ERROR_REQUEST_OUT_OF_SEQUENCE]
2025-05-28 23:20:37, Info                  CBS    Perf: InstallUninstallChain complete.
2025-05-28 23:20:37, Info                  CSI    000013dd@2025/5/28:21:20:37.476 CSI Transaction @0x17a048133e0 destroyed
2025-05-28 23:20:37, Info                  CBS    Failed to execute execution chain. [HRESULT = 0x80070308 - ERROR_REQUEST_OUT_OF_SEQUENCE]
2025-05-28 23:20:37, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80070308 - ERROR_REQUEST_OUT_OF_SEQUENCE]
2025-05-28 23:20:37, Info                  CBS    WER: Generating failure report for package: Package_for_ServicingStack_3440~31bf3856ad364e35~amd64~~20348.3440.1.0, status: 0x80070308, failure source: Execute, start state: Installed, target state: Installed, client id: WindowsUpdateAgent
2025-05-28 23:20:37, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-05-28 23:20:37, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
2025-05-28 23:20:37, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20250528200946.log to WER report.
2025-05-28 23:20:37, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20250528195340.log to WER report.
2025-05-28 23:20:37, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20250528193946.log to WER report.
2025-05-28 23:20:37, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20250528185445.log to WER report.
2025-05-28 23:20:37, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20250528182447.log to WER report.
2025-05-28 23:20:37, Info                  CBS    Not able to add %windir%\winsxs\pending.xml to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-05-28 23:20:37, Info                  CBS    Not able to add %windir%\winsxs\pending.xml.bad to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-05-28 23:20:37, Info                  CBS    Reboot mark cleared
2025-05-28 23:20:37, Info                  CBS    Winlogon: Simplifying Winlogon CreateSession notifications

 

Attachments

It seems one of the fixes was incomplete.

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 try to update again. If it fails attach a new copy of the CBS logs.
 

Attachments

I see this error
Code:
2025-05-29 19:30:38, Info                  CSI    000013da Over-removing a TLC, s/b internal error Microsoft-Windows-LanguagesDB-OneCore, version 10.0.20348.3207, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2025-05-29 19:30:38, Error                 CSI    000013db@2025/5/29:17:30:38.882 (F) onecore\base\wcp\componentstore\analysis.cpp(1252): Error STATUS_REQUEST_OUT_OF_SEQUENCE originated in function CServicingFamilyEntries::RemoveInstalledTlc expression: (null)
[gle=0x80004005]

In some other topic with also Over-removing a TLC, s/b internal error I see it has something to do with [HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\

So i think is something with the
Code:
microsoft-w..-deployment_31bf3856ad364e35_10.0.20348.3207_ce12b420f74cf78d
microsoft-w..-deployment_31bf3856ad364e35_10.0.20348.3207_5f479bbade680b75

But how i find the correct registry keys.

Are I am on the good way @Maxstar Can you help me further and also explain something
 
Hi,

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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-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 try to update again. If it fails attach a new copy of the CBS logs.
 

Attachments

The attached SFCFix.txt is not the result of the SFCFixScript in post #11? Now it's going to be a mess with wrong fixes.
 
@Maxstar Sorry don't know what I messed up. Reverted snapshot. So I have situation after first fix from you.
And tried again the fix from post 11
Update failed.
Logging is attached
 

Attachments

Okay, please provide a new copy of the COMPONENTS hive and an export of the SBS hive.

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.

Export SBS (SideBySide) hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    Code:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    652ff1dfded79-622dbdc454cdb-Export-SBS-hive.png

  • Name this file SideBySide (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send > Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Here's the next fix, but don't do anything else.

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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-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 if it fails attach a new copy of the CBS logs.
 

Attachments

@Maxstar super thx the fix works the patch is installing successfully.
This machine is a clone from the production vm can I reapply the fixes in the same order on the production machine?

Can you explain some more details how to find these fixes?
I asked also @Will about the updates academy
 
Great, and when it is an identical clone you can use the same fixes on the production server.

Can you explain some more details how to find these fixes?

Each problem is different, so it's rather difficult to explain some things in a few words. I can only point out that if you cannot fully understand the error or corruption, don't try to use fixes from other threads or creating them by yourself, because it may cause other issues and/or strange log results.
 
@Maxstar Many thanx for your help. Production server is also working now.
I have donated a small amount to Sysnative. Thanks again and keep up the good work :-)
 

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

Back
Top