[SOLVED] DISM, MSC, SFC, Error 193

M

MEMikie

Contributor
Joined
Dec 6, 2021
Posts
10
Windows Server 2019 Standard. Sudden halt of system processes/components.

SFCCrashFix Dump files were also automatically uploaded to you.
 

Attachments

Hmm, there appears to be couple of different errors here and we'll need to find out a little more information before we can proceed.

Rich (BB code): 
2021-12-07 10:14:34, Info                  CSI    00005e68 [SR] Verify complete
2021-12-07 10:14:34, Info                  CSI    00005e69 [SR] Verifying 100 components
2021-12-07 10:14:34, Info                  CSI    00005e6a [SR] Beginning Verify and Repair transaction
2021-12-07 10:14:35, Error                 CSI    00005e6b@2021/12/7:18:14:35.793 (F) onecore\base\wcp\componentstore\deltastore.cpp(2483): Error STATUS_INVALID_PARAMETER originated in function ComponentStore::CRawStoreLayout::DecompressFile expression: Parameter check failed

Could you please provide a Process Monitor trace using the following steps:

Capture Process Monitor Trace
  1. Once again, we will need you to run Process Monitor.
  2. This time, try to start Process Monitor as close as you can to when the failure occurs when running DISM /Online /Cleanup-Image /RestoreHealth (within 1-5 minutes of failure).
    Read More:
  3. Stop Process Monitor as soon as DISM fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
    i3yiUac.png

  4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
  5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
 
Thanks, could you please provide another trace as you did before, however, this time using the sfc /scannow command? You should be able to attach the CBS log to your forum post.
 
Thanks for providing the trace and the log file again. I believe I've possibly found some of the files which need to be repaired, however, I've asked for a more experienced helper to verify this before doing so. As soon as I have a response, then I'll let you know.
 
I understand it's the holidays etc... Wondering if there is any progress? Thank you for your assistance!
 
I've managed to trace some of the missing files. There a few which I'm slightly confused about, such as:

Rich (BB code): 
C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.4650_none_7eeb34dc2202872c\wer.dll
C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.4650_none_7eeb34dc2202872c\AEPIC.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.4650_none_7eeb34dc2202872c\en-US\TiWorker.exe.mui
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.4650_none_7eeb34dc2202872c\en\TiWorker.exe.mui
C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.4650_none_7eeb34dc2202872c\TiWorker.exe.Local

These should be part of KB5005698: Servicing stack update for Windows 10, version 1607: September 14, 2021

However, they aren't included in the update package and aren't part of my VM which has that update successfully installed. I think we'll ignore those for now and focus on the other ones. I'll work on providing a fix script later tonight.
 
Step 1:
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.

Step 2:
Run SFC /SCANNOW in an elevated commandprompt and report the result.
If it fails copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 

Attachments

SFCFix version 3.0.2.1 by niemiro.
Start time: 2021-12-30 18:49:28.939
Microsoft Windows Server 10 Build 14393 - amd64
Using .zip script file at C:\Users\Administrator\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\Temp\InFlight

Successfully created directory tree \\?\C:\Windows\WinSxS\Temp\InFlight\744fa0624bedd70117b00000282a902a\wow64_microsoft.packagema..iprovider.resources_31bf3856ad364e35_10.0.14393.0_en-us_bb971e8d4bca80b1.
Successfully created directory tree \\?\C:\Windows\WinSxS\Temp\InFlight\aac677624bedd70113b00000282a902a\wow64_microsoft.managemen..e.cimcmdlets.module_31bf3856ad364e35_10.0.14393.0_none_d7b27c7d33ba7796.
Successfully created directory tree \\?\C:\Windows\WinSxS\Temp\InFlight\a7da6b624bedd70112b00000282a902a\wow64_microsoft.backgroun..r.management.module_31bf3856ad364e35_10.0.14393.4046_none_596cf43e29c982c4.
Successfully created directory tree \\?\C:\Windows\WinSxS\Temp\InFlight\0c297a624bedd70115b00000282a902a\wow64_microsoft.packagema..ement.coreproviders_31bf3856ad364e35_10.0.14393.4046_none_867f5acb56f0bed3.
Successfully created directory tree \\?\C:\Windows\WinSxS\Temp\InFlight\417869624bedd70111b00000282a902a\wow64_microsoft-xbox-shel..-gamingui-component_31bf3856ad364e35_10.0.14393.4169_none_762523f600a1a78b.

Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\744fa0624bedd70117b00000282a902a\wow64_microsoft.packagema..iprovider.resources_31bf3856ad364e35_10.0.14393.0_en-us_bb971e8d4bca80b1\Microsoft.PackageManagement.MsiProvider.resources.dll to C:\Windows\WinSxS\Temp\InFlight\744fa0624bedd70117b00000282a902a\wow64_microsoft.packagema..iprovider.resources_31bf3856ad364e35_10.0.14393.0_en-us_bb971e8d4bca80b1\Microsoft.PackageManagement.MsiProvider.resources.dll.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\aac677624bedd70113b00000282a902a\wow64_microsoft.managemen..e.cimcmdlets.module_31bf3856ad364e35_10.0.14393.0_none_d7b27c7d33ba7796\CimCmdlets.psd1 to C:\Windows\WinSxS\Temp\InFlight\aac677624bedd70113b00000282a902a\wow64_microsoft.managemen..e.cimcmdlets.module_31bf3856ad364e35_10.0.14393.0_none_d7b27c7d33ba7796\CimCmdlets.psd1.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\a7da6b624bedd70112b00000282a902a\wow64_microsoft.backgroun..r.management.module_31bf3856ad364e35_10.0.14393.4046_none_596cf43e29c982c4\BitsTransfer.Format.ps1xml to C:\Windows\WinSxS\Temp\InFlight\a7da6b624bedd70112b00000282a902a\wow64_microsoft.backgroun..r.management.module_31bf3856ad364e35_10.0.14393.4046_none_596cf43e29c982c4\BitsTransfer.Format.ps1xml.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\a7da6b624bedd70112b00000282a902a\wow64_microsoft.backgroun..r.management.module_31bf3856ad364e35_10.0.14393.4046_none_596cf43e29c982c4\BitsTransfer.psd1 to C:\Windows\WinSxS\Temp\InFlight\a7da6b624bedd70112b00000282a902a\wow64_microsoft.backgroun..r.management.module_31bf3856ad364e35_10.0.14393.4046_none_596cf43e29c982c4\BitsTransfer.psd1.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\0c297a624bedd70115b00000282a902a\wow64_microsoft.packagema..ement.coreproviders_31bf3856ad364e35_10.0.14393.4046_none_867f5acb56f0bed3\microsoft.packagemanagement.coreproviders.dll to C:\Windows\WinSxS\Temp\InFlight\0c297a624bedd70115b00000282a902a\wow64_microsoft.packagema..ement.coreproviders_31bf3856ad364e35_10.0.14393.4046_none_867f5acb56f0bed3\microsoft.packagemanagement.coreproviders.dll.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\417869624bedd70111b00000282a902a\wow64_microsoft-xbox-shel..-gamingui-component_31bf3856ad364e35_10.0.14393.4169_none_762523f600a1a78b\gamingtcui.dll to C:\Windows\WinSxS\Temp\InFlight\417869624bedd70111b00000282a902a\wow64_microsoft-xbox-shel..-gamingui-component_31bf3856ad364e35_10.0.14393.4169_none_762523f600a1a78b\gamingtcui.dll.

Successfully restored ownership for C:\Windows\WinSxS\Temp\InFlight
Successfully restored permissions on C:\Windows\WinSxS\Temp\InFlight
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2021-12-30 18:49:40.127
Script hash: iWcXqDlBW2wLGxczgqy165WiqZtL04TfaUG8PRV7HyU=
----------------------EOF-----------------------
 

Attachments

Rich (BB code): 
2021-12-30 19:34:55, Info                  CSI    00005e64 [SR] Verify complete
2021-12-30 19:34:55, Info                  CSI    00005e65 [SR] Verifying 100 components
2021-12-30 19:34:55, Info                  CSI    00005e66 [SR] Beginning Verify and Repair transaction
2021-12-30 19:34:58, Error                 CSI    00005e67@2021/12/31:03:34:58.423 (F) onecore\base\wcp\componentstore\deltastore.cpp(2483): Error STATUS_INVALID_PARAMETER originated in function ComponentStore::CRawStoreLayout::DecompressFile expression: Parameter check failed
[gle=0x80004005]

Unfortunately, it seems we've got the same error as last time, could you please capture a new process monitor trace as before while executing the sfc /scannow command? Once complete, please provide the trace file and the CBS log.
 
Thanks, if SFC appears to have run longer then that is a good sign. I'll try and trace the missing files for you again.

In the meantime, it may be worthwhile running MemTest86 for at least 8 passes (will require two runs of 4 passes). Please note that the test can take from time to complete and therefore it is recommended when you aren't going to be using the machine.

Test RAM with PassMark MemTest86
 
I can only do the MEM test if I have someone go onsite, as I am remote. I will wait and see if you find anything. I've never encountered behavior/issues with a server like this! Craziness.
 
I've managed to find some of the missing files, however, looking through the ProcMon log there is quite substantial corruption, which why I recommended to run MemTest86 to ensure there isn't any hardware issues which may be corrupting those files.
 
Quick question, do you know if you've had power losses or any abrupt system shut downs? It's possible that the system crashed or shut down in a middle of an update.
 
x BlueRobot said:
Quick question, do you know if you've had power losses or any abrupt system shut downs? It's possible that the system crashed or shut down in a middle of an update.
Click to expand...
Not that I am aware of. Updates are performed manually each week.
 
I could not uninstall the September Windows update KB5005698. Given that updates after that uninstalled and reinstalled without fixing the issue, I decided to reinstall the operating system.

Thank you VERY much for your help!!! I wish we could have found a simple fix, but the issue is now resolved.
 
Okay, thank you for informing me, hopefully you won't have any further issues.
 
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