Windows 10: Windows 10 Creators update and DISM

Hi there -

Using Win 10 Anniversary Update I had no problem fixing the installation using DISM.

Having done a clean install of the Creator Update and using DISM I get the message: The component store is repairable - The operation completed successfully,
What does this actually mean?
Has the component store being repaired or not? Or does it mean the DISM option has completed the scan?

However, I am unable to repair the installation simple because that the source file cannot be found - or similar, even though I am using the same code as I used before with either an ISO file on DVD or flash drive.

The code I am using is: DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:G:\Sources\Install.wim:1 /LimitAccess

Your help in this matter greatly appreciated.

:)

 

fault with fall creators update

Folks

I put on the Fall Creators Update 2 days ago and have reverted it to standard Creators Update and replaced it again with the Fall Creators Update.

Problem is the same on both systems (i.e. both Fall Creators Update systems). Whereas DISM with its various switches worked perfectly well with the Creators Update, (and before that) - with the Fall Creators Update using the string

Dism /Online /Cleanup-Image /Restorehealth

DISM returns an error code 193 and will not clean up the Windows files. Any ideas folks or is this a known bug with a fix in the pipeline ?

Thanks

 

Dism /Online /Cleanup-Image /RestoreHealth

Hello,

If you're on Creators Update, the DISM is broken. See if this fix help you:

[FIX] DISM Error 0x800f0906 On Windows 10 V1703

Hope this helps, Good luck

 

It looks, that Online DISM and SFC scan is broken in CU, but offline should work.

Use DISM to Repair Windows 10 Image - Page 41 - Windows 10 Performance Maintenance Tutorials

 

Both DISM and SFC are fine with the CU. I have the CU and have used both.

The DISM command you referenced is correct. But you must reference the correct drive where the ISO is mounted. So first of all, mount the ISO on your PC and substituted it for the "G" in your command if the mounted volume is different.

Secondly, the ISO and the Windows version you are running must match. To check the version of your downloaded ISO, you can use the command:

dism /Get-WimInfo /WimFile:H:\sources\install.esd /index:1

If you are still having problems, try leaving off "LimitAccess". This will allow a search of Windows Update for the corrupted components.

 

Thanks for the suggestions, but unfortunately, nothing has worked. I have tried having the ISO file on DVD, flash drive and even on several of the SSDs.
Still getting the message that the source file cannot be found.
Either I am missing something in the code or because of the slight difference of the version of the files - ISO is version 15065.0 and the installed version of the OS is 15063.138.
Which must be the result of an update.

 

DISM has very poor error messages that can make it very difficult to troubleshoot. In your case, the versions are different, and it absolutely will not work with that. The versions must be the same. DISM can be tricky to say the least. If you can't get DISM to work, my suggestion would be to try and repair Windows.

 

@esbkk11000, DISM is known to be broken in Creators Update. We await a fix from Microsoft.
Creators update component store shows corruption but unable to repair

 

DISM is also now accessible through a whole series of PowerShell cmdlets, to wit:
PS C:\WINDOWS\system32> get-help *-WindowsImage #output edited for compactness
Name Synopsis
------- ----------
Add-WindowsImage Adds an additional image to an existing image (.wim) file.
Dismount-WindowsImage Dismounts a Windows image from the directory it is mapped to.
Expand-WindowsImage Applies an image to a specified location.
Export-WindowsImage Exports a copy of the specified image to another image file.
Get-WindowsImage Gets information about a Windows image in a WIM or VHD file.
Mount-WindowsImage Mounts a Windows image in a WIM or VHD file to a directory on the local computer.
New-WindowsImage Captures an image of a drive to a new WIM file.
Optimize-WindowsImage Configures a Windows image with specified optimizations.
Remove-WindowsImage Deletes the specified volume image from a WIM file that has multiple volume images.
Repair-WindowsImage Repairs a Windows image in a WIM or VHD file.
Save-WindowsImage Applies changes made to a mounted image to its WIM or VHD file.
Split-WindowsImage Splits an existing .wim file into multiple read-only split .wim files.
#To get help on any individual *-WindowsImage PowerShell cmdlet, type this
#string inside PowerShell: get-help <cmdlet name>, e.g. get-help Add-WindowsImage
#To see representative examples, type: "get-help Get-WindowsImage -examples".
#For more information, type: "get-help Get-WindowsImage -detailed".
#For complete technical information, type: "get-help Get-WindowsImage -full".
#For online help, type: "get-help Get-WindowsImage -online"

Check it out! For most forum members the Repair-WindowsImage and Get-WindowsImage cmdlets will be of greatest interest. I'm also going to be digging into the Optimize-WindowsImage stuff, too.
--Ed--

 

If true, this update is a poor software engineering effort from MS.

 

It seems the testing effort by MS prior to releasing an update is sorely lacking these days. I didn't get the AU because of the many issues associated with it. I did install the CU without any major issues so far. MS really needs to enhance their pre-release testing procedures. A major software outfit like MS should not be releasing products with so many issues.

 

I agree. I started a thread here but most people seem content with Micosoft's efforts Many Creators Upgrade Problems?

 

Update to my statement that SFC and DISM are working on my PC with CU ... at first both appeared to work. However, later although SFC /Scannow reports no corruption, the DISM command checkhealth reports a repairable component store. This is a glaring error for the CU and should have been corrected prior to release IMO.

 

Yes, it's a poor software engineering effort from MS.

 

Apparently on my pc, Cortana caused the problem with DISM. I tried to get Cortana to work and suddenly DISM was not able to complete properly. So, I used Macrium Reflect backup image and restored to 2 days ago before I was stupid enough to think Cortana was important - and now all is well with DISM. Lesson learned here!