issues running DISM.exe

I have a series of servers with corrupt Windows updates..  It was due to my patch management agent getting quarantined by my AV during updates...  It's suggest that I run DISM.exe /Online /Cleanup-image /Restorehealth and then sfc /scannow, however, I get errors..  The first error is expected for windows updates are corrupt.  The others don't run also.. I matched up my ISO that I extracted to d:\temp\Windows .  I'm currently running Windows 2012 R2 and the iso matches.  I downloaded another version of the ISO thinking there was a newer version, however, the file name and size matches.  Any ideas what I can try?

DISM.exe /Online /Cleanup-image /Restorehealth (gets an Error: 0x800f0906)

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:d:\temp\windows /LimitAccess (get an Error: 0x800f081f)

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:wim:d:\temp\windows\sources\install.wim:1 /LimitAccess (get an Error: 0x800f081f)
gopher_49Asked:
Who is Participating?
 
Travis MartinezConnect With a Mentor Smoke JumperCommented:
My experience with DISM was me fighting corruption on an 8.1 laptop system but the concepts are the same.  My issue ended up being I could never get the right version of install.wim the system was looking for.  In my case it was an OEM install of 8 with an 8.1 upgrade.  Because of the OEM install I don't think I would have every found the right build version of install.wim it was looking for.

There is also the possibility it is looking for something in the wim that doesn't exist.  The CBS log should tell you this information but yes it is a lot to sift through.

It's very cool you have Veeam but you are correct in that recovering the system from backup is likely to continue the corruption unless you know the specific date that it started.

I think you have a few options being VMware.  The one is using the recovery partition as you stated.  The other is building a new VM without pulling updates then trying DISM again with the network option using C:\Windows from a system you repaired or fresh one being built.  You may have better luck with doing the system refresh as the assumption is all the VM's in question would have the same build version.

Theoretically if you recovered one system then used the C:\Windows from that to recover the other 5 systems.
0
 
Travis MartinezSmoke JumperCommented:
The errors you're getting are about missing file locations.  There can also be an issue with the version; however, you've stated you have the ISO but is it the original?  Have you tried mounting the ISO as a drive path as well?
0
 
gopher_49Author Commented:
Yes.  I mounted as a DVD and still no luck.  I tried 2 x different ISO images.  They are Windows 2012 R2 images and the server is that version.  The path is correct for I can browse to it.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Travis MartinezSmoke JumperCommented:
Try "DISM /online /Get-CurrentEdition" and validate your build numbers.  That's the only thing I can think of.
0
 
gopher_49Author Commented:
Below is the output of the version command..

DISM /online /Get-CurrentEdition

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

Current edition is:

Current Edition : ServerStandard

The operation completed successfully.

I've now ran now ran the below commands...  All get errors

dism.exe /online /Cleanup-Image /StartComponentCleanup

DISM.exe /Online /Cleanup-image /Restorehealth

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:d:\temp\windows /LimitAccess

DISM.exe /Online /Cleanup-Image /RestoreHealth /source:d:\temp\windows\sources /LimitAccess

DISM.exe /Online /Cleanup-Image /RestoreHealth /source:d:\temp\windows\sources\install.wim /LimitAccess

DISM.exe /Online /Cleanup-Image /RestoreHealth /source:WIM:d:\temp\windows\sources\install.wim:1 /LimitAccess
0
 
gopher_49Author Commented:
Correction.  The below command did work...  But.. Not sure if this will fix my issue.  My issue pertains to pushing updates to the server and it fails..  Maybe it will.. I can try again...

dism.exe /online /Cleanup-Image /StartComponentCleanup
0
 
gopher_49Author Commented:
I'm trying to push updates from ManageEngine DesktopCentral now...
0
 
gopher_49Author Commented:
We have progress..  I THINK was fixed it (or at least allows one of the updates) was the command below..  This is the only command that succeeded and pertains to fixing updates / rebuilding the SXS folder...  Maybe that's all I have to do to fix my other servers that messed up.. See..  My ManageEngine DesktopCentral agent got quarantined by my AV in the middle of an update.  It corrupted the Windows Update component of Windows..  I think mainly the data store of it?  Not sure..  But..  One of the failed updates installed just fine and the only thing that seemed to run is the command below.

dism.exe /online /Cleanup-Image /StartComponentCleanup
0
 
gopher_49Author Commented:
it seemed to install a few of the update but still getting "the component store has been corrupted" on 2 of the 5 updates pushed to it...
0
 
Travis MartinezSmoke JumperCommented:
Okay.  I think it's the index on the path you're using.  The install.wim has the images for the differing versions of deployment.  Index 1 is "standard core" but 2 is "server standard".

Try this command:  DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:wim:d:\temp\windows\sources\install.wim:2 /LimitAccess

If you want to check for sure:

Dism /get-wiminfo /wimfile:d\temp\windows\sources\install.wim

I found it here:

https://support.microsoft.com/en-us/help/2913316/you-can-t-install-features-in-windows-server-2012-r2
0
 
gopher_49Author Commented:
Awesome.  Let me try ..  brb
0
 
gopher_49Author Commented:
I got the same error when changing to index 2
0
 
gopher_49Author Commented:
Ok..  I'm thinking I might have to do a repair install of Windows 2012 on about 6 x servers..  All of the commands I ran failed.  I attached commands I ran and the errors that occurred..  I have VEEAM VMWare backups and Windows System Backups for all servers...  But..  That includes the corrupt OS.  It seems I'm better off running a system repair?  right?  The OS' I'm concerned with right now are Windows 2012 R2.  I'm also considering calling Microsoft and opening a ticket.
sharepoint-log.txt
0
 
gopher_49Author Commented:
I have a ticket open with Microsoft...  I have VEEAM / VM level snapshots, storage level snapshots, and app level backups...  At this point any update that fails with "The component store has been corrupted" error will never install again, however, new updates will... The thing is..  These are the Spectre and Meltdown updates..  And some are IE 11 updates.  I have to either fix the corruption for these particular updates  or restore the whole server to 1/19 and then refresh the app data... These could be pre-prerequisites to future updates and/or leave potential vulnerabilities.  I can power down the current production VM as a simple roll back plan...   But.. One of my DC's is getting the error too..  So.. Ill spin up another, decommission the messed up one, and move it's IP to the new one for remote host DNS resolution.  I just have to make a decision before Saturday for I only have so much retention on my VEEAM jobs...
0
 
Travis MartinezSmoke JumperCommented:
Then you do have systems that do not have the corruption.  Use the network option for Windows and see if that works from another side by side.

dism /online /cleanup-image /restorehealth /source:\\Server_Name\c$\Windows /limitaccess
0
 
gopher_49Author Commented:
I tried that First and it says invalid source
0
 
gopher_49Author Commented:
Microsoft says my only option at this point is an in place upgrade or manually fix 25+ corrupt files.  Some are critical OS files..
0
 
gopher_49Author Commented:
We ended up doing restores for luckily these servers had close to now actual data changing..  For the DCs.. We'll be doing in place upgrades.. Prior to that transferring FSMO roles...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.