Dism & Windows Updates with base image


Recommended Posts

I have a question out of curiosity as Google was not much help.

 

I always do a dism about once a month as it seems corruption occurs often. I then do a SFC /scannow. If I recall under UEFI there is a hidden recovery partition as part of the standard that the default base image is located in case of DISM or a full restore is needed later on.

 

When I run this command does it undo and replace all the .dll files updated with Windows update with older ones? When Windows update is run does it also update the base image? I ask too as I have to run the Windows Update repair tool as well often and I wonder if there is a correlation from myself using DISM.

 

TechNet seems to just discuss dism repairing SXS but nothing else.

 

 

Link to comment
Share on other sites

I have a question out of curiosity as Google was not much help.

 

I always do a dism about once a month as it seems corruption occurs often. I then do a SFC /scannow. If I recall under UEFI there is a hidden recovery partition as part of the standard that the default base image is located in case of DISM or a full restore is needed later on.

 

When I run this command does it undo and replace all the .dll files updated with Windows update with older ones? When Windows update is run does it also update the base image? I ask too as I have to run the Windows Update repair tool as well often and I wonder if there is a correlation from myself using DISM.

 

TechNet seems to just discuss dism repairing SXS but nothing else.

 

I think you'd be better off investigating why you're seeing corruption so often.  I run a bank of VM's for work that run Windows Update (and are also powered-off and on frequently without shutdown) and I don't see any corruption like you describe.  Did you have any issues during the initial install of Windows or is your disk dying a death?  Best way to check is give it a chkdsk or check the System event log for any errors from NTFS.

Link to comment
Share on other sites

This topic is now closed to further replies.