Windows 10: Win 10 1703; How to fix broken DISM and hence Windows Update?

If you wish, you can try to update manually.
Download WHDownloader (Windows Hotfix Downloader) 2.2
Unzip and run. You'd get a screen as shown:



To update from 1703 ->1709, You'd need KB4073290 (~600MB). This update will bring your PC up to the latest 1709.16299.192 by passing all the updates in between.

 

When the computer crashes it generates files that are useful for troubleshooting the crash.
The checked settings had files that were being cleaned.
When there is a BSOD crash there is a window that can be viewed where it displays the bugcheck.
Sometime it may display the misbehaving driver in the form *.sys
The automatically restart was un-checked so that you now have time to view this information.
Ccleaner already has the files ready to be cleaned.
So Ccleaner needs to be closed and re-opened before any cleaning is performed

 

No, I only clean manually (and cautiously).

Understood. Reminder, I've got a dysfunctional DISM, not a BSOD.

Ok. So what's the next step?

@topgundcp Thanks, I'll look into that. EDIT - those updates are for 16299. I'm still on 15063 trying to get to 16299. Tx anyway.

Thanks to you both.

 

If the KB updates leads to an upgrade the DISM problems should be fixed.
Usually in place upgrade repairs fix problems in the operating system.
So it is likely the DISM problem is a deeper problem in the registry.
See what happens with the KB updates.

Having the computer produce a dump is useful as problematic drivers prevent upgrades and if the problematic drivers produce crashes and dumps they can be identified and replaced.

If the DISM problem is not fixed the computer can be troubleshooted to improve the likely of success in an upgrade. At the same time the logs can be troubleshooted (Panther, DISM, CBS, etc.)

 

Yup, that's what I'm thinking.

From the MS Support page for the key update: "To install this update, you must have Windows 10 Version 1709 installed."

Ok, but I don't know how.

 

Download and install Whocrashed.
Resplendence Software - WhoCrashed, automatic crash dump analyzer
Above analyze click on tools > crash dump test > type: ACCEPT
Click analyze
Post the whocrashed report into the thread using a one drive or drop box share link.
Run this version of the log collector and post a new zip into the thread:
log collector v2-beta08.zip

Earlier this month the logs have information that a crash occurred but there was no BSOD mini dump file generated.
The above test is to see if the computer environment will create BSOD dumps.

Have you noticed any hangs, freezings, black, red, or blue screens, unexpected restarts or shut downs?

 

No hangups, BSOD, or unexpected start or stop. It's nice to know about the whocrashed utility, but there is no memory.dmp in my Windows directory and the minidmp subdirectory is empty (EDIT -as you suggest). I'm gonna assume that I simply have a fault in the DISM component.

As you mentioned somewhere above, I have a legacy AMD video card. From my reading, it may be contributing to the issue in the sense that the MS upgrades to the Creators' editions didn't provide for it. I think at this point I'll beg off the diagnostics. I will make a disc image, and then try an offline DISM fix, ie. from the PE environment, as suggested, for example, here: How to use DISM in WINDOW PE environment? Will report if it works. If it doesn't work, well.... 1703 can suffice til I move my butt and build my planned new system.

Thank you for the assistance and advice. -Ron

 

The memory dumps were cleaned by Ccleaner.
Post #11 displayed that the dumps if any were being cleaned along with windows error reports.
The whocrashed is to set up the dumps so that additional troubleshooting can be made.
Was whocrashed able to make a dump that it could analyze?
If so you then may be able to see if the crash that happened spontaneously reoccurs.
Once who crashed has created a crash dump please run the log collector for troubleshooting:
log collector v2-beta08.zip

 

error 193 cannot be cleared via DISM or SFC,
Its either the install/repair of the API or a clean install
The only folder that can establish the missing or corrupt entries causing it, is - System32/downlevel...API folder..
(This problem has no specific MS related fix documentation, and causes an internal corruption within DISM.)

Although the OP referenced a specific file as being missing, it may not be the relevant file.

api-ms-win-core-file-l1-2-0.dll;11;30.10.2015 07:28;30.10.2015 07:28
api-ms-win-core-file-l1-2-1.dll;0;30.10.2015 07:28;30.10.2015 07:28

in the above, although 2 different files, the error is identified by the 0 it should be greater than 10

see
[SOLVED] [10ProV1511b10586 x64] Can't upgrade, DISM Error 193, sfc finds nothing
in the thread a number of files needed to be corrected

If the API is missing them it will have to be imported- note the dates MUST be the same

Roy

 

I'm the OP. Thank you! After a week of searching, that's the most definitive statement I've seen on this error! Sounds like you are familiar with it.

Yes, in desperation I put a copy of the "missing file" that I got from a healthy 1709 laptop into the downlevel directory on this 1703 desktop. Made no difference. (I have removed it.)

I had seen ref to the downlevel directory in other threads dealing with the same problem, but didn't (and still don't) know how to proceed. I did try a 1703 repair in place with no success. (IIRC, the installer errored out after about 85% completion of the file installation phase.)

Don't understand. Are you saying the files are misnamed? You mean the "0" in the file name? The "0" vs. the "11" between the two semicolons? They are not part of the file name - what are they? My downlevel directory does contain those two files, but with dates corresponding to Win 10, 1703, 15063.850.

As I say I'm not missing two files with those precise names.

I have a fresh, mounted 1703 iso, but I don't see a downlevel directory in it. (There are directories with many manifest folders, but I don't know how to extract and install files from them.) I will study that thread more carefully, but it looks like the solution - the SFCFix script - was prepared specifically for that user. If someone could instruct me on how to do that, I'd most appreciate it (as will future searchers LOL).

Many thanks, -Ron

EDIT - Looks like the program SFCFix.exe can be used without a script, and is purported to fix errors that sfc /scannow cannot. https://www.ghacks.net/2015/11/06/sfcfix-comes-to-the-rescue-when-sfc-scannow-cannot-repair-windows-file-corruption/ But it's no longer supported. Anyone been successful with it in Win10?

 

Hi Ron,

That downlevel folder is a bit of a mystery, there is a basic set of API's but its added too depending upon what you have installed, my W10IP is much larger than yours even tho i've only got 4 programs on it!!!

Must admit been looking at that error code for a while, and quite a lot over the last few days.

Did you actually view the ouput post#18, you will need to register.
I tried to recreate the output in the same format, with the extra detail, but couldn't can you??
If you can then we can replace the corrupt entry
As for "0" id have to guess its some kind of version number

One more thing
Those entries should be about 7kb got any with 0

Im still hunting

Roy

 

Hi Roy,

No. DOH!! Now that I have, your post of course makes more sense. Thank you for pointing me to that forum! Looks like they can identify and do surgery on just the responsible registry corruptions. I think I'll try their protocol.

Many thanks. -Ron

 

Hi Ron,

see its sorted*Biggrin,

Suspect it waited for your active times to pass before it downloaded and installed the upgrade, after those downlevel fixes.

Roy

 

Hi Roy,

What happened was a window came up saying "Got a major upgrade ready, you wanna do it now or later?" (paraphrasing), so I said do it now.*Smile Took about 90 minutes. Win Update had apparently recognized that my configuration was now sufficiently stable.

Wish I knew more about what those files do. And how this happened. So I guess a DISM 193 error associated with a failed WU doesn't necessarily require a clean install.

These forums are great! Thanks to all the volunteers. For searchers, the thread Hawkman refers to is: https://www.sysnative.com/forums/windows-update/24668-10v1703b15063-x64-wu-0x800700c1-dism-error-193-a.html

-Ron

 

I don't understand what you are saying here. The program will allow you to download all available updates for MS Office, Windows 7/8/10. So it depends on what you need to download.

If you want the update for 10563 then put a check mark on those. You can also download all 16299 to update from 10563, skipping all the updates in between.