Hi
I'm new to the forum
When running SFC / SCANNOW I get an error message - Can someone help in fixing the issues that it refers to?
"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"
See and try running Dism /Online /Cleanup-Image /RestoreHealth to see if this solves your problem. Then run SFC /SCANNOW again - you may need to do this times with a full restart between each time SFC is run.
Done this and no progress. I downloaded the Windows Image File onto my F drive and run:
"DISM /Online /Cleanup-Image /RestoreHealth /WIM:F:SourcesInstall.wim:1 /LimitAccess"
and get the following notification.
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:WINDOWSsystem32>DISM /Online /Cleanup-Image /RestoreHealth /WIM:F:SourcesInstall.wim:1 /LimitAccess
Deployment Image Servicing and Management tool
Version: 10.0.10240.16384
Image Version: 10.0.10240.16384
[=========== 20.0% ]
Error: 1726
The remote procedure call failed.
The DISM log file can be found at C:WINDOWSLogsDISMdism.log
What next ?
I've never had to use the /source flag only the basic Dism /Online /Cleanup-Image /RestoreHealth command. Have you tried this basic command first?
See also the specific Windows 10 tutorial on this DISM - Repair Windows 10 Image
Done this and no progress. I downloaded the Windows Image File onto my F drive and run:
"DISM /Online /Cleanup-Image /RestoreHealth /WIM:F:SourcesInstall.wim:1 /LimitAccess"
and get the following notification.
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:WINDOWSsystem32>DISM /Online /Cleanup-Image /RestoreHealth /WIM:F:SourcesInstall.wim:1 /LimitAccess
Deployment Image Servicing and Management tool
Version: 10.0.10240.16384
Image Version: 10.0.10240.16384
[=========== 20.0% ]
Error: 1726
The remote procedure call failed.
The DISM log file can be found at C:WINDOWSLogsDISMdism.log
What next ?
I Tried the above but receive the following error when running:
C:Windowssystem32>call Dism.exe /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
[===========================80.0%============== ]
Error: 1726
The remote procedure call failed.
I suspect that a high percentage of those that upgraded from Windows 7 to Windows 10 will get this message about corrupt files. I am OCD about my PC - had a perfectly running Win 7 and after upgrading, scf gave the same errors. Same problem running a USB ISO clean install.
It's not being reported much on the blog yet as not many people will actually bother to run this command. It drove me nuts and I installed Win 10 from a MS DVD in the end (as I said, I am OCD) and the errors are no more.
If your issue is like mine, then it is an issue with the initial install - the sfc errors were reported after running the command immediately after the clean install - even before loading any drivers.
I agree... the problem only manifested itself after Windows 10 upgrade from Windows 8
I used to run SFC / SCANNOW every 3 / 4 months without problem.
Problems only started after upgrade to Windows 10 - The first issue was Outlook failing to send emails - SFC fixed that... from thereon-in errors have been popping up.
Microsoft do not accept that the Windows 10 install could have caused the problem saying that the problems 'MUST' have been on my system prior to upgrade!! - However for a one-off fee or annual support payment they will be able to remote into my system and fix all the issues... But they will not tell me how to do it myself
Hmmm.... I would be skeptical allowing MS to dig around in my PC remotely. No guarantee that they will be able to fix it either. They might still end up telling you to re-install.
I don't know if this will work but you have a legal license for your Windows 10 - try obtain a MS DVD matching your version and install that. Just make sure you do not enter any license key from the DVD packaging during the install unless you have actually purchased it. Theoretically this should still activate using your already assigned license key that is registered with MS. I suspect that your troubles will be gone then.
A clean install using a MS DVD is what sorted me. I must have reinstalled Win 10 pro about 6 times using different USB's and different ISO's (re downloaded 3 times) and could not get away from the issue.
