Windows 10: DISM restorehealth fails to run after latest CU

This link may be useful:
Use DISM to Repair Windows 10 Image Performance Maintenance Tutorials

 

Thank for the link. I will try this after work tonight.

 

@gcwizard
I just used the Edge method ( How to get the Windows 10 Fall Creators Update - Page 51 - Windows 10 Forums ) and got 16199.15. If you are getting 16199.19 from your download, that may be a problem. .15 is the "BASE" FCU, .19 is after a cumulative update.

 

Hello F14tomcat and zbook,


Unfortunately your suggestions using another source for DISM will not work. I could be wrong, and maybe it will work for GCwizard but I wouldn't bet on this. The only option here concerning this DISM issue is a clean install in my view.

This was mentioned also in the Microsoft forum thread I posted. There is supposingly a way to fix by finding someone who has a working 100% copy of 16299.15 and copying the Windows System32 downlevel folder from their copy to the affected system. Apparently has something to do with .dll files.

Your postings on this is appreciated just so you both know, and thanks for that.

Regards,

EG

 

You're welcome, sorry it didn't work for you.

 

You are welcome.
For the 16299 versions, in use on my pc now are .98 and .64.
Sorry that they don't match for the dll.
This information may be useful for the clean install:
Clean Install Windows 10 Installation Upgrade Tutorials

 

You are correct. I incorrectly wrote down 16299.19 instead of .15. Just confirmed this with Get-WimInfo command. Sorry.

 

zbook: Microsoft's MCT is not working so I used the Edge workaround changing the string to Safari and downloaded .16299.15 as a wim. I could not get an esd copy. I ran the dism / online /cleanup-image /restorehealth with the wim source and limitaccess and got the same error 193 meassage as before. Turned off metered connection and got the same result again. Downloaded KB4016871 but it is not for 1709 and would not install. A clean install may be in the works. Looking and my file structure I have a SAVE folder in the first level of my C drive(OS drive) and it contains 100 GB of files and some folders that are in the first level also. PerfLogs, ProgramFiles, Programfiles(x86). PtrogramData, and Windows. The Windows folder has 38 GB where the windows folder on the first level has 32GB. My laptop is also 1709 latest CU up to date and it does not have the folder. My PC works fine other than the dism cleanup-image failures. Scanhealth and checkhealth yield the same error code. I will be doing a clean install in Jan.

 

Were you not able to create a bootable windows 10 iso from this website? : Download Windows 10

 

I found a couple of cases of DISM error 193 problems being resolved at the link below so it may be worth joining and requesting some help. It looks like it's definitely not a simple and straight forward fix and from what I can see the only other alternative is a clean install.

https://www.sysnative.com/forums/windows-update/

 

I have a bootable usb drive I made from the copy I downloaded using Heidoc to downloads and then used Rufus to create the usb thumb drive. I did download from the same site you referenced with edge/safari option to downloads but did not use Rufus as I was out of usb drives. I mounted that and ran the dism strings with the same error. The bootable usb drive also yielded the same results. I did not look at the dism logs to see if anything was different. I also burned a dvd from the MS 1709 download using image burn and it also yielded the same error message. I can use Rufus to create another usb drive tonight after work using the MS download. Both the Heidoc ISO and the MS ISO were the same size and same version/edition.

 

I made a bootable usb thumb drive from the ISO I downloaded from your link and ran the DISM commands using it as the source last night with metered connections on and off and it resulted in the same error 193 messages.

 

According to this answers.microsoft.com forum thread (see the March 25 post from Cybot for details) this problem is demonstrably caused by missing dlls in the DISM runtime environment. The post details the forensics used to fix the problem, but it sounds pretty time consuming. If you decide to go down this road, start with a complete image backup that you know you can restore if things go south.
HTH,
--Ed--

 

Since this PC is used for a home based business I back it up frequently and also have auto backup for any new files. It is backed up in multiple ways, Macrium reflect, external hard drive, and also to flash thumb drives. I will be doing a clean install next month after I finish my taxes. I had uninstalled the last updates to roll back to 16299.15 to match the current MS and techbench 1709 downloads and to see it that would fix the issue and it did not. Since I also have a SAVE folder in the C: directory that has 4 folders that are in the windows folder I will be doing a clean install to fix the mess that the 1709 update created. Thanks for the link, I had read the thread and had considered updating to 16299.98 and then comparing my laptops downlevel directory to the affected PC's but I think I will re-install windows at a more convenient time. Just curious, is there a way to check and see what my onboard recovery OS is? Is it 1709 or a previous OS. I have never understood why MS does not put mirror OS's in place on separate partitions to auto repair itself. Thanks!