Little_Micky_Fingers
Member
- Apr 2, 2014
- 8
Good day to you all!
The SFC utility indicated that there were corrupted files which could not be fixed. Using an Elevated Command Prompt the following command was run:
Dism /Online /Cleanup-Image /RestoreHealth
The output from the above command reads as follows:
C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
[==========================100.0%==========================]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
Configure a Windows Repair Source.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
This is the first time that DISM has finished with this error. I would be most grateful if someone could help me to find a solution to this problem. As an additional note I must say that I am surprised to find that the SFC utility finds corrupted files on an almost weekly occurrence and that DISM has proved to be a most useful utility.
Many thanks in advance for your attention in this matter.
Regards to you all.
LMF
The SFC utility indicated that there were corrupted files which could not be fixed. Using an Elevated Command Prompt the following command was run:
Dism /Online /Cleanup-Image /RestoreHealth
The output from the above command reads as follows:
C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
[==========================100.0%==========================]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
Configure a Windows Repair Source.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
This is the first time that DISM has finished with this error. I would be most grateful if someone could help me to find a solution to this problem. As an additional note I must say that I am surprised to find that the SFC utility finds corrupted files on an almost weekly occurrence and that DISM has proved to be a most useful utility.
Many thanks in advance for your attention in this matter.
Regards to you all.
LMF