Performance :: SFC / ScanNow Corrupt Files And DISM Fails
Aug 26, 2015
Recently updated to windows 10 I've tried a scannow to resolve another issue and I get a failure message with files being corrupted. I've tried a reset keeping my files but where to look next. Attached is my log file from the SFC and the DISM log really stuck currently.
DISM
Error: 0x800f081f
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 Configure a Windows Repair Source.
The DISM log file can be found at C:WINDOWSLogsDISMdism.log
Scannow
Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windirLogsCBSCBS.log. For example C:WindowsLogsCBSCBS.log.
Note that logging is currently not supported in offline servicing scenarios.
I ran sfc/scannow (trying to diagnose a sleep problem) and it found irreparable files, and I ran it again in safe mode, and again, irreparable.
I ran dism and it couldn't access the source files. (Afterwards, I checked windows update, and it says that the computer is up to date, and the last check was at the time I ran dism!)
After scannow, i have : Windows resource protection found corrupt files but was unable to fix some of them. Details are included in the CBS.log windirlogsCBSCBS.log.....
I ran "SFC /scannow" and got an error saying the System File Checker found errors but couldn't fix them. Afterwards I ran "DISM /Online /Cleanup-Image /RestoreHealth" and DISM threw the error 0x800f081f saying that the source files could not be found.
I then ran "DISM /Online /Cleanup-Image /RestoreHealth /Source:H:Sourcesinstall.wim" to direct DISM to my windows 10 disk, but this also didn't work.
I don't know what to do short of reinstalling Windows, I've attached my CBS and DISM logs in a .zip file below (the CBS log was too big).
I have been trying to fix my windows 10 corrupted files but I have been unabled to recover it. I tried every possible way of recovering using DISM commands, but to no avail. I tried also the sfc /scannow but as usual this command hardly ever fixes issues regarding corrupted files. I have tried using dism in several ways by specifying the location and the install.esd file from my usb flashdrive windows copy and even tried the health commands on powershell..still wont work. The first command I tried and for all of them I get the same error message, which looks like this:
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 [URL] .....
The DISM log file can be found at C:WINDOWSLogsDISMdism.log
I have heard people saying that I need to refresh my pc as a last solution and I don't want that since I have all my settings and programs migrated from the upgrade...
I have been reading on the web that there is a way of specifying the packages missing via command and then download them manually..
So I've done a sfc /scannow for maintenance and noticed that there were some files that could not be repaired. And instead of writing this on a old topic I made my own.
I found a batch file created by "kronckew" . The code is:
@echo off rem delete old files del /q %windir%logscbscbs.log del /q c:sfcdetails.txt rem run sfc sfc /scannow
[Code] ....
I will upload the CBS file and the file created by this batch. I really don't want to reinstall my Windows.
I ran sfc /scannow in an admin command prompt, however when it completes I receive this message:
"Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windirLogsCBSCBS.log. For
example C:WindowsLogsCBSCBS.log. Note that logging is currently not
supported in offline servicing scenarios."
I think that it may be somehow related to a few errors happening on my laptop--such as live tiles not working, and the inability to use some apps without crashes.
can some of you do an sfc /scannow and check your results with the November update installed? I always do this when i finish installations, and on 3 computers and 4 installations on them, 2 on one computer just to be sure i am getting corrupt files and struggling with my anger to not go back to windows 7 and get rid of all win 10 problems and MS ignorance. here is my results, many corrupted files in the log.. but is long so i don't post it...
Microsoft Windows [Version 10.0.10586](c) 2016 Microsoft Corporation. All rights reserved.
C:WINDOWSsystem32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan. Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windirLogsCBSCBS.log. For example C:WindowsLogsCBSCBS.log. Note that logging is currently not supported in offline servicing scenarios.
My Windows 10 computer has been freezing/crashing frequently recently (HP Pavilion 500-123ea). I got some good advice to try running the sfc/scannow diagnostic process to try to resolve the problem. However it gets up to about 56% and I get an error message: 'Windows Resource Protection could not perform the requested operation'. And there's no elaboration beyond that, so I don't really know what's going on.
The computer is continuing to freeze/crash in Word alone (no Web) and while browsing eg on Yahoo, Yahoo Mail etc. I've run PC Health Advisor software which suggests it's not fragmentation, nor RAM, nor registry issues, and the monitor looks OK.
This might seem like an obscure problem, but I think if it could be resolved it might stop my system from crashing, so I don't know. I should add that I tried 'Dism' and that's OK.
I have a very old laptop, but despite the age it has worked relatively fine for my needs with just an HDD change. I bought this at the very end of Vista lifespan with an almost immediate Win7 upgrade offered. I then skipped Win 8 totally, but rolled a Win 10 when it came, and it has been working well. But you get the picture. This machine is old.
Onto the point: I'm getting an occasional fan rev up, with the CPU at 100%. The process is Service Host: Local System (Network Restricted). Recently, I also lost all sound on the computer, which chkdsk /f /r was able to salvage. I have a feeling these might relate to a same problem.
I researched, and found out that sfc /scannow will work. OK. It starts the verification process, but fails at 18% saying corrupt files exist. When I export the sfcdetails.txt from the log, it does not really report which files are corrupt so as to replace them. 00000e22 [SR] Beginning Verify and Repair transaction and then the logfile ends.
Because I cannot complete SFC, I'm told to run DISM, and that is how I ended up here. When I run Dism /Online /Cleanup-Image /RestoreHealth
Image version 10.0.10240.16384 At 20% an error 1726 with remote procedure call failed.
So I go to dowload the ISO and mount it. It will then give me the .esd
So I'm having my fingers crossed while running Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:F:SourcesInstall.esd:1 /limitaccess
I have a Lenovo W530 laptop, that started with Windows 7 Pro, then got upgraded to Windows 8, then 8.1, and now 10 Pro.
I have the factory setup disks for only 7 and 8.
I ran DISM and it says the source files could not be found. From a similar problem several months ago, I sort of know how to work with DISM, but if it is looking for Windows 10 files, where would I point DISM ?
My next step is to use the log files, and attempt to find which files are corrupted.
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 Configure a Windows Repair Source.
The DISM log file can be found at C:WINDOWSLogsDISMdism.log
So I run the check again with an ISO image of Windows mounted in E, but I got the same error message.
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 Configure a Windows Repair Source.
The DISM log file can be found at C:WINDOWSLogsDISMdism.log
I've been trying to use DISM /Online /Cleanup-Image /Restorehealth on my Windows 10 Home, but it keeps telling me that it does not support servicing Windows PE with the /Online option. Of course I'm not running WinPE 10.
Experienced plenty of issues with win 10 installations after upgrades from say WIN 7. The issues are just about all related to the disappearance of MS Edge and the Start Menu.
One should run the SFC /scannow command , followed by the more complicated DISM command and then finally the very complicated powershell command.
Almost no replies are made after one runs the SFC command and even the DISM command and no errors are found.
What should one conclude if the SFC command and the DSIM command report no errors? Secondly what is the best next step in trying to recover from the issue at hand?
W10 (64 bit Home) has been working OK on this laptop but recently I have been able to open the settings screen for only a micro-second. Having found people having the same problem I have tried running SFC several times, as suggested, but it says it found an issue it could not resolve.
Again following instructions on the forum I tried running DISM with an iso loaded and this hung at 40% for hours (overnight).
I do not understand what to look for in the log file, but there are several lines that mention an error. I attach the log file (zipped)....
I just completed a clean install of Windows 10 Pro...all was going fine, but I wanted to run both scf and DISM...
If SFC was not able to repair some or all of the files there are a few options including a repair install from the OS dvd, and DISM (win 8 & UP)
DISM
If you are on win 8 and up you can (and should) run DISM if SFC found errors it could not fix
From an DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:elevated command prompt*
Type DISM /Online /Cleanup-Image /RestoreHealth . (please note the space after "dism", & "online" & "image")
If the repair is successful you may want to re-run SFC just to check.
[URL]
Have never had this issue before...but I can't seem to be able to direct DISM elevated command to a .iso file:
To run a system file check (SFC)
Go to start
Type CMD
Right click and run as Administrator
(called an elevated command prompt)
If you want to verify and repair the OS type sfc /scannow (note the space between sfc and "/")
If you just want to check (verify only) the OS type sfc /verifyonly (no changes will be made using verify only)
If you get the error message "cannot find source files"you need to have an ISO file mounted and need to specify where it is located with the below command
DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:* Where "X" is the drive letter where the ISO is located.* SourcesInstall.wim:1 /LimitAccessSimply change the "X" to the correct drive letter
If you do not have an ISO you can make one.* The instructions are here
*You may have to run this up to 3 times to fix all the problems
When you have finished it will say one of three things
Windows did not find any integrity violations (a good thing)
Windows Resource Protection found corrupt files and repaired them (a good thing)
Windows Resource Protection found corrupt files but was unable to fix some (or all) of them (not a good thing)* If you get this message run DISM as described below..
I also have the DISM log file which I would be more then happy to upload:
Earlier today while playing Dying Light, my PC randomly blue-screened with the error "page fault in nonpaged area cpuz136_x64.sys" - After running a malware scan, nothing was found. After that I cleaned my registry with CCleaner. I haven't played Dying Light since then, but a few minutes ago I decided to run sfc /scannow - and It came up with a few files that were corrupt.
CBS.log: Spoiler 2015-10-25 17:05:02, Info CBS Session: 30478193_851218210 initialized by client WindowsUpdateAgent, external staging directory: (null) 2015-10-25 17:05:02, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] 2015-10-25 17:05:02, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805] 2015-10-25 17:05:02, Info CBS Session: 30478193_851228178 initialized by client WindowsUpdateAgent, external staging directory: (null)
I get Error 0x800f081f when run DISM.exe and it states the source file can't be found. When I run SFC scannow I get nine files that can't be repaired.
I have run SFC /SCANNOW and a large number of files have been found to be corrupted in Windows 10, and cannot be repaired by SFC. The CBS log is too large to attach, but I have extracted a list of all corrupt files attached.
After looking at similar posts, I downloaded SFCFIX.exe by Sysnative and ran that in an elevated command prompt, but the message I got was that source file could not be found. I have also run SFC in safe mode and also run DISM, but neither solves my problem, and the corrupt files persist.
Does SFC /Scannow really work? It always finds corrupt files in all of my systems regardless of the age of the OS install. Out of curiosity, I installed a pristine Windows 10 Pro on a clean, formatted, erased and empty(?) hard drive with no apps installed on a spare laptop . Ran SFC /Scannow and it reported corrupt files.
I've received 5 files from 5 sources, both Excel and Word. Every time I try to open one I get an error message "File is corrupt and can't be opened." I can work on my own files, but not downloads.
I tried the Windows 10 "workarounds" but these didn't work. I've tried to download using both Firefox and Edge, no difference.
