How to repair your system files using DISM and SFC /Scannow (Build: 10041)

I've managed to repair my system files on Windows 10 TP build 10041. This is how to do it for those interested in it. Note: you will need the ISO for build 10041. If you don't know how to get it, see Andre's thread: Instructions: Create a bootable ISO file using ESD Image for Windows 10 Build 10041

Now follow the next steps:

1. Mount the .ISO file by double clicking on it.

2. Open 'Windows Powershell' or 'Command Prompt' with Admin privileges (right click -> Run as Administrator)

3. Let's check the System Health first, by running these commands:

  3.1 dism /online /cleanup-image /scanhealth

  3.2 dism /online /cleanup-image /checkhealth

  3.3 dism /online /cleanup-image /restorehealth

4. I'm sure that 3.3 will give you an error stating that it could not perform the task. And now it's when the mounted ISO comes into play. Let's specify the file from the ISO so that we can fix it. Run the following command: (Notice that X must be the drive letter on which your system has mounted the ISO)

  4.1 DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess

5. Now let's repair any damage in the system files, shall we?

  5.1 sfc /scannow

Now it should work for you, guys! I hope this will help. My system seems more responsive since then. Please report if you encounter any problems following these instructions.

Regards,

Luis.

 

Discussion Info


Last updated December 17, 2018 Views 162,795 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

If this is verified to work, could it be made into a sticky or put in the wiki?

If this is verified to work, could it be made into a sticky or put in the wiki?

At least it works for me. I've just run 'sfc/scannow' again in Windows Powershell with administrator privileges and it's gone through the process at the first run. Since it'd already fixed the integrity violations, it did not find anything to repair :)

Edit: I attach an image to show what I've just stated:

In space no one can hear you scream.

Fantastic!

It would be great to have feedback from more users in order to know whether this is an ultimate solution for SFC or not.

Please, if you try this, share your experiences and let us know so as to keep us posted.

Regards,

Luis.

In space no one can hear you scream.

Since this method has been around for a long time, what does one do if /scanhealth fail, even tho

/scanhealth fails,  you see /checkhealth was say repairable and /restorehealth will say complete

your /sfc can an does fail at many different %.   and it get very very old to fix with a RESTORE or REFRESH or a complete Clean Install ...  this has been a problem long standing.

Nice when it works, but when any part fails... check your CBS log

I know this is an old issue, but the whole thing about it is precisely because you're bound to find problems with the DISM /restorehealth command. That's why the following step is so important:
(Notice that X must be the drive letter on which your system has mounted the ISO)

  4.1 DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess

You are using the source files from the ISO to restore it, instead of the ones in your Windows system. I don't know why, but it seems they get corrupted upon the installation process.

After doing this, it should work again and once you have sorted that out, SFC /scannow should work again as intended. Have you given this a go?

Thanks!


In space no one can hear you scream.

To read more you can go to msdn for a full understanding on this. Been doing this except I create a wim and mount that then link to the mount.

https://msdn.microsoft.com/en-us/library/jj980032%28v=winembedded.81%29.aspx

Create wim from my tutoral in technet

These are the commands to service your winre.wim the parts you will need to manually complete are the bold underlined text

Prepare/Create and register an recovery partition, so the option Copy the Recovery Partition becomes available in the recovery drive UI  application.

In elevated command run> RECIMG -CREATEIMAGE C:\REFRESHIMAGE< 

This will create a new custom.wim in a folder Refreshimage.

Now lets get ready to register the path of the image, so our create recovery drive option(COPY THE RECOVERY PARTITION FROM THE PC TO THE RECOVERY DRIVE) becomes available.

>  In the folder you created there will be a> custom.wim< change it to>INSTALL.wim<
> Create a folder In Cd/directory using Elevated command> mkdir c:\Win8.1-Recovery,> Win81-Recovery<.
> Copy the  INSTALL.WIM. Put in the Win81-recovery folder created.
> Run in elevated commad>REAGENTC /SetOSImage /Path C:\Win81-Recovery\INSTALL.WIM /Index 1<

Do not copy the arrows if using copy and paste, that is my way of pointing out lines of code

_______________________________________________________________________________

▼Checking if path is correct

Dism /Get-ImageInfo /ImageFile:C:\Recovery\windowsRE\winre.wim

 

▼Created path in C:Mount, Mounted my winre.wim to the created directory

Dism /Mount-Image /ImageFile:C:\Recovery\windowsRE\winre.wim /Index:1 /MountDir:C:\mount

▼Checking packages from the mount

Dism /Image:C:\mount /Add-Package /PackagePath:C:\mount\windows\servicing\packages

▼Confirming packages can be called with the get command

Dism /Image:C:\mount /Get-Packages

▼Comfirming if remove packages work

Dism /Image:C:\mount\ /Remove-Package /PackageName:Microsoft.Windows.Calc.Demo~6595b6144ccf1df~x86~en~1.0.0.0

▼completing the mount by unmouting with a commit command

Dism /Unmount-Image /MountDir:C:\mount /Commit

This saved my newly serviced winre package and used on a different computer using a 64 bit OS.

http://technet.microsoft.com/en-us/library/dd744382(v=ws.10).aspx


Edit tested the image with

Dism /Online /Cleanup-Image /RestoreHealth /Source:c:\Recovery\windowsRE/winre.wim /LimitAccess

confirmed working on build 10041 pro 64

kudos to you!

confirmed working on build 10041 pro 64

kudos to you!

Thanks for the confirmation. I'm glad you were able to do it successfully!

Question: did it also find corrupted files in your system?

Regards,

Luis.

In space no one can hear you scream.
Thanks for that. Really useful and insightful information there! :D
In space no one can hear you scream.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.