[SOLVED] KB5025221 don't install with error code 0x80073701

Re,

Error DISM
Missing files error 0x800f081f

Version : 10.0.19041.844

Version de l’image : 10.0.19045.2788

[==========================100.0%==========================]
Erreur : 0x800f081f

Impossible de trouver les fichiers sources.
Utilisez l’option « Source » pour indiquer l’emplacement des fichiers requis pour restaurer la fonctionnalité. Pour plus d’informations sur la spécification d’un emplacement source, voir Configure a Windows Repair Source.

Le fichier journal DISM se trouve à l’emplacement C:\Windows\Logs\DISM\dism.log
 

Attachments

  • Go to ... Control Panel > Programs > Turn Windows features on or off
  • Windows Features window will open
  • Leave this window open while you do the following ....

Download FRST64 to your Desktop

  • Double click Frst64.exe to launch it.
  • FRST will start to run.
    • When the tool opens click Yes to the disclaimer.
    • Copy/Paste or Type the following line into the Search: box.
    SearchAll:wow64_microsoft-windows-securestartup-core_31bf3856ad364e35_10.0.19041.1865_none_b3b45b00dbe19efb
    Click to expand...
    • Press the Search Files button.
    • When finished searching a log will open on your Desktop ... Search.txt
    • Please post it in your next reply.

You can now close the Windows Features window.
 
OK thanks. Just checking that the files and Registry key we'd just patched were in fact present on your machine, because your last CBS.log for some reason indicates that they're not.

Going to have to consult on this, because it's not clear to me why that is.

Could take a while, but I will get back to you ASAP.
 
Found a problem with one of the .manifest files I used to patch your machine in post #40, so have sourced a new replacement from a different source, which will hopefully resolve the disparity in your CBS.log

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.
1p8eDnI.gif

  • 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 ...
    • If it completes successfully, try updating again ...
    • If successful please let me know.
    • If DISM does not complete, or if an update attempt is unsuccessful ...
    • 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
 

Attachments

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.
1p8eDnI.gif

  • 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 ...
    • If it completes successfully, try updating again ...
    • If successful please let me know.
    • If DISM does not complete, or if an update attempt is unsuccessful ...
    • 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
 

Attachments

Latest log is flagging the .manifest file we've just replaced. Can't see anything wrong with the file we used, so going to have to consult my more experienced colleagues to see if they can see something that I can't.

May take a while, but I'll be back as soon as I can.
 
Please try the following ....

Download the
61c988c2082b1-updateassistent.png
Windows 10 Update Assistant to your desktop.
  • Right-click on Windows10Upgrade9252.exe and select the option: Run as administrator.
  • Press the Update now button, click after the compatibility check on Next.
  • The Update Assistant will now download the latest Feature Update.
  • After verifying the download, the Feature Update will be installed.
  • When this process is ready, click on the Restart now button to complete the installation.
 
Hello,

Nothing Happen.
When i lauch the file, it's saying "My windows is up to date." immediately

After rebooting and retrying an update. Same error message on windows update.
 
OK thanks.

Which edition of Windows are you using (Home, Pro, Ultimate, Education etc etc) because I'm having trouble sourcing a Registry key that I think is causing the latest error that's being flagged in your CBS.log

This is possibly because the VM I've set up for sourcing files may not be the same edition as the one on your machine. Normally, as long as it's the same version, that doesn't usually matter, but in this case it might.
 
OK, thanks.

Edition I used to create my VM was Home, so I'm going to set up a VM with Pro, and see whether that allows me to source what I need. Wiil take a while, since I'll have to update it appropriately as well.

No guarantees this will work, but worth a try if it allows us to proceed.
 
Using Pro did not work, but I've been able to source what I need from elsewhere, so hopefully we should be able to proceed.

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.
1p8eDnI.gif

  • 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 ...
    • If it completes successfully, try updating again ...
    • If successful please let me know.
    • If DISM does not complete, or if an update attempt is unsuccessful ...
    • 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
 

Attachments

Latest CBS.log doesn't tell me what I need to know. I need you to send me the whole CBS folder.

  • Open Windows Explorer and browse to the ... C:\Windows\Logs\CBS ... folder.
  • Right click on it, and select ... Send to > Compressed (zipped) folder
  • A message will appear stating, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
    • Answer Y to create a folder CBS.zip on your Desktop.
  • Please attach it to your next post.
    • If the file is too large, please upload it to a file sharing service and provide the link to it in your next reply.
    • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 
Re,
After reading CBS.

I could see that the 0x80073701 errors were on the following lines.

2023-04-21 10:47:03, Error CSI 0000054a@2023/4/21:08:47:03.159 (F) onecore\base\wcp\componentstore\csd_locking.cpp(95): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)
[gle=0x80004005]
2023-04-21 10:47:03, Error CSI 0000054b (F) STATUS_SXS_ASSEMBLY_MISSING #69921022# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2023-04-21 10:47:03, Error CSI 0000054c (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #69920877# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = Microsoft-Windows-Printing-InternetPrinting-Client-Opt-Deployment, version 10.0.19041.1806, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Microsoft-Windows-Printing-InternetPrinting-Client-Opt-Package~31bf3856ad364e35~amd64~~10.0.19041.1806.8f55eb4632a834ffc236ffffaf542c28', rah = (null), manpath = (null), catpat[gle=0x80073701]
2023-04-21 10:47:03, Error CSI h = (null), ed = 0, disp = 0)[gle=0x80073701]
2023-04-21 10:47:03, Info CBS Failed to pin deployment while resolving Update: Microsoft-Windows-Printing-InternetPrinting-Client-Opt-Package~31bf3856ad364e35~amd64~~10.0.19041.1806.8f55eb4632a834ffc236ffffaf542c28 from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2023-04-21 10:47:03, Info CBS Failed to bulk stage deployment manifest and pin deployment for package:Multimedia-RestrictedCodecsCore-WCOSHeadless-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.2673 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2023-04-21 10:47:03, Info CBS CommitPackagesState: Started persisting state of packages
2023-04-21 10:47:03, Info CBS CommitPackagesState: Completed persisting state of packages
2023-04-21 10:47:03, Info CSI 0000054d@2023/4/21:08:47:03.168 CSI Transaction @0x277c02b08d0 destroyed
2023-04-21 10:47:03, Info CBS Perf: Resolve chain complete.
2023-04-21 10:47:03, Info CBS Failed to resolve execution chain. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2023-04-21 10:47:03, Error CBS Failed to process single phase execution. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2023-04-21 10:47:03, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.2846.1.6, status: 0x80073701, failure source: Resolve, start state: Absent, target state: Installed, client id: UpdateAgentLCU
2023-04-21 10:47:03, Info CBS Not able to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]




I see a missing package on my PC: Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.2846.1.6.
Wouldn't the solution come from this package?
 
Few things missing from the list you've found, also we replaced ... Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.2846.1.6 ... in one of our earlier fixes. By the way, despite the name, that's not a package as such, actually it's 2 files, a .cat file and a .mum file.

Will get back to you as soon as I've finished looking through the latest logs you've posted.
 
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