[SOLVED] DISM is throwing Error 193 on execution

V

valenti

Member
Joined
Nov 25, 2015
Posts
8
Hello, there! I have the same problems after migrating to an nvme drive. :huh: SFC shows corrupted files that cannot be repaired and DISM shows error 193 (not even run). :banghead::banghead::banghead: Here are my logs. View attachment Logs.zip
I would be grateful if you can help me.
 
Hi valenti :)

My name is Aura and I'll be assisting you with your issue. Follow the instructions below please.

myjIXnC.png
SFCFix - Fix Time

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to download and execute a SFCFix fix, and provide the log.
  • Download SFCFix and move the executable on your Desktop;
  • Download the attached SFCFix.zip and move the archive to your Desktop;
    Note: Make sure that the file is named SFCFix.zip, do not rename it.
  • Save any work you have open, and close every programs;
  • Drag the SFCFix.zip archive file over the SFCFix.exe executable and release it;
    mMabJGT.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;
SFCFix.zip
 
That's the outcome: :)

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-11-30 23:39:56.799
Microsoft Windows 8.1 - amd64
Using .zip script file at D:\Users\Helias Valenti\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll

Successfully copied file C:\Users\Helias Valenti\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll to C:\WINDOWS\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll.

Successfully restored ownership for C:\WINDOWS\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll
Successfully restored permissions on C:\WINDOWS\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2015-11-30 23:39:56.990
Script hash: SPhJgk57HkoTrdMLtWrtMfeOccJRwa6Z8fwFua8SZKg=
----------------------EOF-----------------------
 
Let's see what DISM returns :)

EndqYRa.png
DISM - Fixing Component Store Corruption
Follow the instructions below to run a DISM operation on your system.
  • On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
  • On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
  • Enter the command below and press on Enter;
    Code: 
    DISM /Online /Cleanup-Image /RestoreHealth
  • Let the scan run until the end (100%). Depending on your system, it can take some time;
  • Copy the C:\Windows\Logs\DISM folder and C:\Windows\Logs\CBS\CBS.log file on your Desktop, then right-click on it, go to Send to... and select Compressed .zip archive;
  • Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;
Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the DISM scan is completed, it won't contains the information from the scan anymore. So archive it and upload it as soon as you can.
 
From what I can see, DISM completed it's scan successfully and no error was returned. Did it throw an error code 193 this time?
 
Well at first yes (error 193). I checked dism log; and it seems that the custom temporary folder i had defined, for some reason, couldn't be accessed by dism.exe... (I had given it the same permissions as the default temp folder, but...)
Then, when I reset it to default direction, it run without any problems or error. So, now I triggered it back to my custom location (my windows drive is SSD, and i like to be reserved from unnecessary writes).
 
Which means that C:\Users\$USERNAME\AppData\Local\Temp isn't your temp folder? If you set it elsewhere, DISM fails to run, but if you set it to the default location, it works?
 
It could be a limitation of DISM. It's the first time I've heard of that to be honest. I guess I could try it in a VM and see what happens. You modified your %temp% variable, or did you redirect the Temp folder elsewhere?
 
I made a change in environment variables. Both user temporaries: TEMP and TMP were relocated into another drive.
 
I don't have that kind of setup in a VM sadly (like a second drive). I could always try with a second partition on the same drive and see what it gives.
 
As you like! :)
For me, the problem seems solved :thumbsup2: :smile9::rofl12::smile9:
 
Then we'll leave it at this :P Marking this thread as solved now :)
 
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