About to update, but found an issue with Dism

AirPower4ever · 19 Aug 2019

I was about to about to the latest update when I decided to check my system. Using the powershell and the check and scan commands here:

Use DISM to Repair Windows 10 Image

My system said when I did both that both were repairable. So I proceeded to the steps below and I keep getting the "restore operation failed". I tried step 5, got the failed part so went to step 6 and tried both options; where my install.wim is at (failed) and then tried the -limitaccess one and still same.

sfc finds issues too

What to do now?

dalchina · 19 Aug 2019

Hi, first check your disk as a matter of routine.
Hard Disk Sentinel (trial) gives a great summary on its GUI. Else e.g. HD Tune (free), Health and Error scan tabs.

If ok, run
chkdsk c: /scan
from an admin command or Powershell prompt.

What is your Windows build?
Sadly it's not a forum requirement, so we often have to ask. Win key + r, winver

What is the update you are considering? Do you mean update, or an upgrade to build 1903?
If 1903, have you been offered that by Windows Update?

No one can guess what the 'latest update' is for an unknown PC, as people run different builds with different possible constraints.

If your disk and file system are ok, and you are upgrading (not updating) then I suggest you do this by
a. Creating a current disk image if you don't have one. (E.g. Macrium Reflect).
b. Download the 1903 iso
c. Attempt the upgrade by logging in and using the 1903 iso, without accepting updates.

If this succeeds, any non-user profile issues with your current build should be irrelevant.

If you wish to try to repair your current build please see the tool at post #2 here:
Windows 10 Recovery Tools - Bootable Rescue Disk

Else you could try an in-place upgrade repair install which keeps all progs and data and needs an iso of your current installed build.

MeAndMyComputer · 19 Aug 2019

AirPower4ever said:

sfc finds issues too
What to do now?

Usually I start by running SFC /SCANNOW first.
--- Please post what your SFC /SCANNOW reports.

dalchina · 19 Aug 2019

You can check whether the SFC scan is failing for this known reason:
MS Posts Support Note About Defender SFC /Scannow Errors

AirPower4ever · 20 Aug 2019

Thank all for replying
@dalchina - I have an SSD. I do have HD Sentinel, it say 100% good. Windows build is 1903 build 18362.267. I was going to update to KB4512508 when I decided to run the tools. I will wait before I do the rest of the tools you mentioned to see if the info I provided changes the course we are headed.
@MeAndMyComputer - When I run the sfc /scannow I get this:
Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

@dalchina - Checked defender and the folder is 4.18.1907.4-0 and it reads just like EdTittle posted showing the two folders. It does say shockwaveriderz installed the latest update KB4512508 to get to build .295 where they wrote it changed the defender folder to 4.18.1908.

Thank you everyone for the posts, I'll sit tight and see which way to go.

MeAndMyComputer · 20 Aug 2019

@MeAndMyComputer - When I run the sfc /scannow I get this:
Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.[/QUOTE]

When "Windows Resource Protection did not find any integrity violations." Isn’t reported, the message you received is one of the messages that is reported. You might already know this.
--- On the PC I was working on this morning the same message came up.

Then it’s time to run Dism /online /cleanup-image /RestoreHealth.
--- When you reach [===100.0%===], wait a little longer to see the final reported result.
--- So far all I’ve seen is “The restore operation completed successfully.
--- The operation completed successfully”
--- Exit out of the Administrator Command Prompt screen.
Please post what your result is if it's different.

Now it’s very important to Restart or Shut down.
--- When logged back into your account, run SFC /SCANNOW again.
--- Most of the time, I have gotten "Windows Resource Protection did not find any integrity violations."
There were a couple of times when it didn't. In those cases, I repeated the same procedure one more time and each one of those times resulted in successful outcomes. Fortunately, I didn’t have to dig deeper as that’s what I would have done.

With all of that said, although that is an oversimplified process but it has worked for me so far with a minimum amount of time.
--- If/When it doesn't I'll have to go deeper; most likely I'll ask for help.

AirPower4ever · 20 Aug 2019

@MeAndMyComputer - I ran the sfc /scannow and got the same thing. I restarted and then did the Dism commands and here is what happened, it got to 98.5% and got stuck for about 13-15 seconds then the below appeared.

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

I have not tried restarting again, I got to go back to work. Later tonight though I can sit and do these over and over again.

Thank you

dalchina · 20 Aug 2019

DISM: again, see
If you wish to try to repair your current build please see the tool at post #2 here:
Windows 10 Recovery Tools - Bootable Rescue Disk

If that doesn't help, then the last resort would be an in-place upgrade repair install...

Farvatten · 20 Aug 2019

Bree said:

One of my machines has just got the 4.18.1907.4 platform through windows update and, as expected, SFC reports defender powershell errors.

Running Dism /Online /Cleanup-Image /RestoreHealth while disconnected from the internet reports 'The source files could not be found' so yes, internet connection is required. Attached are the logs, I have only run DISM while disconnected, I've not yet connected and run DISM to perform the repairs.

There are cases where DISM needs an internet connection to complete repairs.

MeAndMyComputer · 20 Aug 2019

AirPower4ever said:

@MeAndMyComputer - I ran the sfc /scannow and got the same thing. I restarted and then did the Dism commands and here is what happened, it got to 98.5% and got stuck for about 13-15 seconds then the below appeared.

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

I have not tried restarting again, I got to go back to work. Later tonight though I can sit and do these over and over again.

Thank you

Thank you for checking that out. Now it's time to follow the advanced recommendations that have been posted

EDIT: After re-reading how it turned out for you, It appears you did the restart after running SFC /SCANNOW and before the DISM command.
--- I could have been clearer and instead of saying "Now it’s very important to Restart or Shut down." I could have said Now it’s very important to Restart or Shut down after DISM is completed.
--- You might want to try that procedure one more time as well as ensure you are online.

BTW, on the PC I was working on today, after conducting the process I mentioned, I had to do quite a tune-up the PC seriously needed. Afterward I did a follow-up SFC /SCANNOW, Dism /online /cleanup-image /RestoreHealth, Restart and SFC /SCANNOW again for verification and all turned out well.