|
Post by Admin_Vistamike on Jul 4, 2016 13:41:14 GMT
The SFC /scannow facility in Windows 10 The command looks for disk errors and attempts to repair errors found. SFC /scannow has been around for quite a while in Windows. However, you might get the ' sfc found corrupt files but "was unable to fix" sometimes (or even often!!) The trick, if it is a trick, is to reboot every time this error appears. If you get 3 repeated responses then personally I'd be doing a complete reinstall of the OS or recovering from an image. System File Checker should be looking for errors on the hard drive an then attempt to correct those errors. In Windows 7 it did work pretty well, in Windows 8.1 was a bit 'iffy' about the results found, in Windows 10 it just a repetition SFC found corrupt files but "was unable to fix' Microsoft have really got to work harder on Windows 10, there are so many hardware and software problems to deal with, as I have found thus far. READ MORE on this>>>>>
|
|
|
Post by GuiltySpark on Jul 28, 2016 11:16:06 GMT
I think in Win 10 because it's WaaS (Windows as a Service) the DISM command is often more favourable just remember to be connected at the time.
|
|
|
Post by Admin_Vistamike on Aug 1, 2016 12:26:32 GMT
I have run DISM in Windows 7 Pro / Ultimate and 8.1 Pro with online success. ( CMD or PowerShell will run DISM ). Running WinX Pro: Version 1511 (OS Build 10586.494) FYI, DISM / CMD commands are descrbed from this excellent site Windows Central>>>>> And the M$ offering>>>>> In 10, with PowerShell, here are the results. Never had this in any previous OS!
|
|
|
Post by GuiltySpark on Aug 1, 2016 13:12:11 GMT
You have no source! Strange.
|
|