[SOLVED] W10 21H2 update fails 0x80070003, SFC cannot start repair service

Error 87 "the cleanup-image option is unknown" occurred again
 

Attachments

  • DISM-ResetBase_results.jpg
    DISM-ResetBase_results.jpg
    47.9 KB · Views: 1
Please try the Update Assistant, if it fails the CBS - and or Rollback logs - may give more information about this issue.

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.
 
The update is in process (it will take some time to complete).

In the meantime, I thought it might be helpful to mention that during my various research prior to posting on SysNative, I had stumbled upon this info in SysNative: Windows 10 Upgrade fails with error 0x8007007e and Windows Updates fail with code 0x8 . I couldn't understand the last two paragraphs though.

(I'm not sure, but I suspect maybe the Servicing Stack is corrupt - no idea how to confirm this or fix it if it is true).

I'll let you know the outcome of the Update. (The rollback logs would be setupact.log and setupact.err, in C:\$Windows.~BT\Sources\Rollback\, correct?)
 
The update failed with a simple box that states "Windows 10 installation has failed". There were no logs in C:\$Windows.~BT\Sources\Rollback\.

I found this MS that lists which log files are created under various circumstances. Log files that are created when you upgrade to a new version of Windows

"The following log files are created when an upgrade fails during installation before the computer restarts for the second time:
  • C:\$Windows.~BT\Sources\panther\setupact.log
  • C:\$Windows.~BT\Sources\panther\miglog.xml
  • C:\Windows\setupapi.log
  • [Windows 10:] C:\Windows\Logs\MoSetup\BlueBox.log"

I've attached the setupact.log (had to zip this), miglog.xml,and BlueBox.log (there was also a setuperr.log - not mentioned by MS but I saw it so I included it). There was NO setupapi.log file, however, I did notice a setupact.log and setuperr.log (this one is 0Kb so not attached) in C:\Windows, so I attached setupact.log as well. I changed it's name to cWindows-setupact.log for clarity.

Thank you so much for all your help so far! It is greatly appreciated!
 

Attachments

Hi,

Could you please run the following commands in a elevated command prompt. Attach Dirlist.txt to your next post.

Code:
dir /s /a C:\Windows\WinSxS\amd64_microsoft-windows-deliveryoptimization_31bf3856ad364e35_10.0.16299.15_none_ed464d1a38296141 >> "%userprofile%\desktop\Dirlist.txt"
dir /s /a C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.16299.371_none_943aa0ecef573388 >> "%userprofile%\desktop\Dirlist.txt"
dir /s /a C:\Windows\WinSxS\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_10.0.16299.248_none_bc721a14145ef109 >> "%userprofile%\desktop\Dirlist.txt"
 
Rich (BB code):
2022-06-01 07:49:46, Error                 CSI    00000006 (F) [SR] Component not found: Microsoft-Windows-WindowsUpdateClient-Core, version 10.0.16299.248, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}[gle=0x80004005]
2022-06-01 07:49:46, Error                 CSI    00000007@2022/6/1:12:49:46.587 (F) onecore\base\wcp\servicingapi\cmirepair.cpp(313): Error HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) originated in function Windows::ServicingAPI::CCSIRepairTransaction::LockComponent expression: HRESULT_FROM_WIN32(14081L)
[gle=0x80004005]
2022-06-01 07:49:48, Error                 CSI    00000008 (F) [SR] Component not found: Microsoft-Windows-Update-OrchestratorCore, version 10.0.16299.371, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}[gle=0x80004005]
2022-06-01 07:49:48, Error                 CSI    00000009@2022/6/1:12:49:48.118 (F) onecore\base\wcp\servicingapi\cmirepair.cpp(313): Error HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) originated in function Windows::ServicingAPI::CCSIRepairTransaction::LockComponent expression: HRESULT_FROM_WIN32(14081L)
[gle=0x80004005]
2022-06-01 07:49:48, Error                 CSI    0000000a (F) [SR] Component not found: Microsoft-Windows-DeliveryOptimization, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}[gle=0x80004005]
2022-06-01 07:49:48, Error                 CSI    0000000b@2022/6/1:12:49:48.353 (F) onecore\base\wcp\servicingapi\cmirepair.cpp(313): Error HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) originated in function Windows::ServicingAPI::CCSIRepairTransaction::LockComponent expression: HRESULT_FROM_WIN32(14081L)
[gle=0x80004005]

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.
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.
 

Attachments

Pleas run the following command in a elevated commandprompt and let me know the result.
Code:
DISM /online /cleanup-image /RestoreHealth
 
Failed with error 87: "the cleanup-image option is unknown"
 

Attachments

  • DISM-RestoreHealth_results.jpg
    DISM-RestoreHealth_results.jpg
    43.3 KB · Views: 4
Please run the System File Checker as well and post the result.
Code:
sfc /scannow
 
Completed successfully "Windows Resource Protection did not find any integrity violations"
 
Please run the following command and attach DISM.txt
Code:
COPY %windir%\logs\dism\DISM.log "%userprofile%\Desktop\DISM.txt"
 
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.
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.
 

Attachments

Hi,

Open a elevated command prompt and run the following command. Attach Services.txt to your next post.
Code:
WMIC SERVICE GET caption, name, startmode, state > "%userprofile%\desktop\Services.txt"
 
Please try to start the TrustedInstaller service and let me know the result.
Code:
net start trustedinstaller
 

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

Back
Top