Windows 10: dism always returns an error when changing system packages

I am trying to repair a system in order to get updates working.

I am working with a copy of the vhdx, so I am free to experiment.....


dism /online /cleanup-image /scanhealth says all is fine.

Summary:

Operation: Detect only

Operation result: 0x0

Last Successful Step: CSI store detection completes.

Total Detected Corruption: 0

CBS Manifest Corruption: 0

CBS Metadata Corruption: 0

CSI Manifest Corruption: 0

CSI Metadata Corruption: 0

CSI Payload Corruption: 0

Total Repaired Corruption: 0

CBS Manifest Repaired: 0

CSI Manifest Repaired: 0

CSI Payload Repaired: 0

CSI Store Metadata refreshed: True

Total Operation Time: 110 seconds.
2019-04-17 20:09:38, Info CBS CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]
2019-04-17 20:09:38, Info CBS Count of times corruption detected: 0



dism /online /enable-feature /featurename:rasrip returns "The referenced assembly could not be found."



2019-05-05 09:10:43, Info CBS Exec: 1 deployments need bulk staging

2019-05-05 09:10:43, Error CSI 00000008@2019/5/5:13:10:43.048 (F) onecore\base\wcp\componentstore\csd_locking.cpp(200): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)

[gle=0x80004005]

2019-05-05 09:10:43, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.

2019-05-05 09:10:43, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2019-05-05 09:10:43, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2019-05-05 09:10:43, Info CBS Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2019-05-05 09:10:43, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2019-05-05 09:10:43, Error CSI 00000009 (F) STATUS_SXS_ASSEMBLY_MISSING #1594# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]

2019-05-05 09:10:43, Error CSI 0000000a (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #1442# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = Microsoft-Windows-RasRipListener-Deployment, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Microsoft-Windows-RasRip-Package~31bf3856ad364e35~amd64~~10.0.14393.0.RasRip', rah = (null), manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]

2019-05-05 09:10:43, Info CBS Failed to pin deployment while resolving Update: Microsoft-Windows-RasRip-Package~31bf3856ad364e35~amd64~~10.0.14393.0.RasRip from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

2019-05-05 09:10:43, Info CBS Failed to bulk stage deployment manifest and pin deployment for package:Microsoft-Windows-RasRip-Package~31bf3856ad364e35~amd64~~10.0.14393.0 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

2019-05-05 09:10:43, Info CBS CommitPackagesState: Started persisting state of packages

2019-05-05 09:10:43, Info CBS CommitPackagesState: Completed persisting state of packages

2019-05-05 09:10:43, Info CSI 0000000b@2019/5/5:13:10:43.548 CSI Transaction @0x23828973a80 destroyed

2019-05-05 09:10:43, Info CBS Perf: Resolve chain complete.

2019-05-05 09:10:43, Info CBS Failed to resolve execution chain. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

2019-05-05 09:10:43, Error CBS Failed to process single phase execution. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

2019-05-05 09:10:43, Info CBS WER: Generating failure report for package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.14393.0, status: 0x80073701, failure source: Resolve, start state: Installed, target state: Installed, client id: DISM Package Manager Provider




AFAIK this is telling me that the Microsoft-Windows-Foundation-Package is missing "something"


The log files are pretty worthless.

I have tried ProcMon to get a clue about what is missing, but unable to find it.


I believe I have to use windbg and/or Time Travel Tracing in order to find this elusive assembly.


How do I determine what it is complaining about ?


Does anyone have any experience resolving these issues ?



already tried:

dism /online /cleanup-image /scanhealthdism /online /cleanup-image /restorehealth

dism /online /cleanup-image /analyzecomponentstore

sfc /scannow

repair install -- fails with same error 0x80073701
copy COMPONENTS hive from same version DVD, then reinstall -- fails with same error 0x80073701

:)

 

Programs not working


In post 26 there were steps listed to fix the operating system corruption.
Are you able to follow them?
In post 29 was the suggested dism repair command.

 

"WINDOWS 10 error The application has failed to start because the side by side configuration is incorrect.

Here are the error lines I received:

2018-02-25 18:58:10, Error DISM DISM Package Manager: PID=17800 TID=18024 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070570)

2018-02-25 18:58:10, Error DISM DISM Package Manager: PID=17800 TID=18024 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80070570)

2018-02-25 18:58:10, Error DISM DISM Package Manager: PID=17800 TID=18024 Failed to restore the image health. - CPackageManagerCLIHandler:rocessCmdLine_CleanupImage(hr:0x80070570)

2018-02-25 18:58:10, Error DISM DISM Package Manager: PID=17800 TID=18024 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070570)

2018-02-25 18:58:10, Info DISM DISM Package Manager: PID=17800 TID=18024 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

2018-02-25 18:58:10, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070570

 

DISM - Parameter "Cleanup-Image" is not known (error 87)

Hello Eric,

To troubleshoot your concern, we suggest that you run DISM Restore Health command. Refer to the steps provided below:

• Open Command Prompt (Administrator).
• Type the following command:

DISM /Online /Cleanup-Image /RestoreHealth

3. Press Enter.

Let us know how it goes.

Thank you.