[SOLVED] DISM /online error 193

Status
Not open for further replies.
I took a look at the setupact.log, and setup starts to log errors when it tries to take a look at the dism driver store. so once again we are stuck trying to find a way past the dism 193 error it appears
I have attached a copy of both the setup.act and the setuperr.log for you to peruse to see if you can see anything I missed

View attachment setupact.log
View attachment setuperr.log
 
after having that tweaking repair tool run just about every repair it has, sfc finally came back wih uncorrectable errors.

for all the files it found, it said the there was a hash mismatch and also that the servicing store copy was corrupted.
files listed:

shutdown.exe
Wimgapi.dll
winnat.dll
securekernel.exe
dism.exe

the .exe's in seem to work, with exception to the persistent error 193 from dism

I am not sure where to go from here. I already tried putting a copy of dism from my system32 directory into hers, but it hasn't helped.

update: securekernel.exe gives a cannot be run in win32 error
 
HOT DAMN! I DID IT! I DID IT! I DID IT! I DID IT!

after painstakingly going entry by entry in the registry and directory by directory and comparing entries and comparing them to what was on my pc (which was made really easy thanks to remote desktop), I finally arrived at the system32\downlevel directory. I noticed there were a few of the lengthy named .dlls present on my PC that were not on hers. whats more, the .dll's had the word service in them so I copied took ownership of the downlevel directory and files on her PC and made made some adjustments to the permissions of the files there. while there is a shared clipboard in remote desktop, for some reason, perhaps a security countermeasure, I could not copy directly from my system32 directory to hers using remote desktop. but, what I could do, is copy the the directory onto her desktop, and then move the copied directory to her c:\windows\system32 directory. I then ran dism /online /? at the elevated command prompt I had open already. and lo and behold instead of the error 193 I had been getting, I got what you would expect to see from the command the dism help option plus the option to use with /online. currently I am running the dism /online /cleanup-image /restorehealth command. afterwords I will run a repair install just to fix up all the permissions and stuff I tampered with.
 
results from the dism /online /cleanup-image /restorehealth are in:


Summary:
Operation: Detect and Repair
Operation result: 0x800f081f
Last Successful Step: Entire operation completes.
Total Detected Corruption: 39
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 39
Total Repaired Corruption: 17
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 17
CSI Store Metadata refreshed: True
Total Operation Time: 1483 seconds.

am following up with same command but with /source:wim:x:\sources\install.wim:1 added
 
results from second run are now in.

Summary:
Operation: Detect and Repair
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption: 22
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 22
Total Repaired Corruption: 22
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 22
CSI Store Metadata refreshed: False
Total Operation Time: 1313 seconds.
 
after running dism a third time after noticing that when running it from the windows directory dism was using 10565, I ran dism from the setup file I made earlier, so that dism 10586 was used. it seemed to take forever, but after an additional run the log reported back a final status of 0x0. no errors found. good. I next ran sfc /scannow which took an extraordinarily long time to complete after it fixed something it wanted me to restart, so I did and rani sfc one more. after another long wait for it to finish, I took a look at the cbs.log. it looks like most of the time it spent running was rebuilding the filemaps. but it now reports no integrity violations. next up: windows seup
 
ok I have run into another speed bump here. I am unable to access the com+ applications in component services. it says "Catalog Error" - "You do not have permission to perform the requested action. If security is enabled on the System Application of the target computer make sure you are included in the appropriate roles." I am not sure how to fix this, and the newest solutions to fix this are from either XP or windows 7. I think this restriction is keeping me from successfully running windows setup. - I keep getting a modern setup host has stopped working with the cause being msvcrt.dll I already replaced the file - which was the same version as was on my computer, but it didn't help.


at this point windows setup is crashing right before the point where it asks me what I want to save. I looked in the event log and it says the faulting module is msvcdrt.dll with fault offset 0x0000000000073bde. there was a similar error when I first upgraded the pc to from win7 to win 10, and I discovered that my win7 and hers were different builds, and the msvcrt.dll from my PC when copied to hers, enabled windows setup to function with out crashing. but now we are both running the same version and build of windows, so I don't know what to do next. I do still have a copy of my msvcrt.dll that I posted on online as help to others. but I don't know if it would solve the problem or make it worse.
 
Hi again

I have to admire your dedicated efforts to a nearly line-by-line fix of such a complicated repair. If you succeed, I think you should get some kind of certificate or medal (or get hired by Microsoft). By now, I'm pretty much here for moral support. If I luck into a method that can help when you hit a bump, I'll certainly post it here. I'll have to look around at the error you just saw - it's one I haven't come across before. You might be "going where no tech has gone before" (cue the Star Trek theme!) .... If I had the time, heck, I might try your method just to explore it a bit. Interesting it is indeed.
 
I'm not that familiar with dism, so i'm hoping you might know. I have heard you can apply an image while offline. is it possible to do a repair install or something very much like it using dism while offline? (or online for that matter)
 
Hi again

I haven't tried it myself, but I been giving instructions using the exact steps from a tech source that had tested that method. The wording of the options is a little odd, since they include the /online parameter, but point to a DVD source (in the case of the instructions I refer to - a DVD from the Media Creation tool source). I posted those in post #2 of this thread. You used to get error 193 using just about any source at the time.

Can't hurt?
 
just took a look at that, looks like what you were talking about is just the standard SURT scan/repair using DISM. that operation can be run offline or online. but it does not do anything remotely like a repair install.

I just tried running the command substituting /online for /image:c: (I was at the recovery command line, not In windows) and I also added /scratchdir:c:\scratch (after using md c:\scratch) and the command ran ok but found nothing wrong. meanwhile, sfc /scannow /offwindie:c:\windows /offbootdir:c: says it found errors but could not correct them. oddly enough nothing is added to the cbs.log so I don't know which file has an issue.


Actually I take that back, DISM dis find something, I just don't know what it means or how to fix it. DISM reports the metadata store is corrupt.
it says in the log it is repairable if a repai is requested, but I don't know how to do so, and /cleanup-image /restoehealth doesn't seem to be doing the trick
 
Sorry 'bout that - I didn't mean a repair install, I just thought you meant repair using DISM offline. I haven't yet found a way to do a full in-place repair install without starting things from Windows... If I find such a method, by golly I'll post it here. It would make repairs a bit easier, that's for sure.
 
just thought I would provide a update.

starting yesterday morning, when I booted up the laptop, I got a bad_system_config_error BSOD. after I ran (or tried to) the startup repair function (which may or may not work) I got a 0xc0000021a bsod. so I started using the command line from the recovery interface. I ran multiple passes of chkdsk, sfc, and dism. although no new repairs that I could tell were performed, everything I did appearently got windows working again. appearently one of the operations I did restored the registry to a stat of about a couple of weeks ago. this would have been when I was deep in the error 193 hole, but had yet to get started dinking around with permission and other stuff. normally this would mean I lost all the fixes and changes I had made, which is usually bad. but in this case it was actually a good thing. windows was able to successfully run the files downloaded by the media creation tool (C:\ESD\Windows\setup.exe). I knew windows setup would not crash when it past the 40% part of the setup section right before setup asks you what you want to keep. a little bit later setup was at the black setup progress screen. once setup completed, I ran windows update and started updating windows. the only issue I had here was an issue of which M$ is aware of, where the M$ C+ redist is offered and installed over and over. I followed M$'s workaround and fixed that. Windows 10 now stands at 10586.164, the same as my laptop.

as of right now, the only remaining issue is with the complus applications in component services, which apparently followed me over from windows 7. It was caused by my use of Windows 7 Easy Transfer, back when the laptop was new. Seeing as I didn't even know about the issue until about a week ago, and it has been there for a while with out windows throwing a fit or anything, I am at this point calling the laptops state as "FIXED"

Lessons taken away from this:

  • If DISM error 193 occurs a likely suspect is the lengthy named .dll's in "C:\windows\system32\downlevel". despite all my other attempts to fix the error, it wasn't until the .dll's in this location were repaired that DISM started functioning again.



  • DISM being in a working order is critical for windows setup to be able to work.


  • If there is a problem with the .dll's in the previously mentioned directory, then not even an offline repair using DISM will work. Nor will using DISM from the ADK. (deployment and imaging tools)
 
Thanks again for sharing the results of your hard work with us: quite a marathon! Kudos for sticking with it.
 
yeah, I never would have expected such an obscure directory to be so important. there doesn't appear to be anyone else who has solved issues which are probably caused by the files in that directory. usually they opt for a clean install rather than fixing what went wrong.
 
cybot said:
yeah, I never would have expected such an obscure directory to be so important. there doesn't appear to be anyone else who has solved issues which are probably caused by the files in that directory. usually they opt for a clean install rather than fixing what went wrong.
Click to expand...

I am having the exact same issue with the same symptoms. I do not have a second computer to pull the files from. Can you please post the relevant .dll's somewhere to download?
 
Status
Not open for further replies.

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

Back
Top