harrystein
New member
- Jul 27, 2019
- 1
For us technical folks, would be nice if sfcfix would explain in great detail what exactly it does. Normally, I (1) run sfc /scannow and if corruption detected, I (2) copy the cbs.log file (it may have rolled over), (3) and look at the cbs.log file certain strings such as "Cannot repair" and "Repairing" to indicating corruption.
If I see "Cannot repair" items, I next run:
DISM.exe /Online /Cleanup-image /Restorehealth
When that is done, I run another sfc /scannow. Unfortunately, the DISM does not always fix the issue. It would be nice if the "white paper" on sfcfix.exe would explain what causes such failures and how it proposes to do a better job than DISM.
Related to this (keep in mind I have not yet run sfcfix), many times sfc /scannow shows the OneDrive.lnk as "Cannot repair" and I wonder if this is a known Microsoft bug -- you would think it would always show up, but I only see it 10% of the time and I can never be sure what it means -- Microsoft is mum about it (I reported it 6 months ago and it still shows up from time to time). It's corrupted state could be an intentional flag to Microsoft that someone has clicked or never clicked on the OneDrive shortcut. Just a dumb guess.
I also wonder about prncacla.inf reported as "Cannot repair". [Win8/8.1] GUIDE: CNBJ2530.DPB and prncacla.inf Corruptions mentions it and suggests running sfcfix.exe but I would like to know what it does to fix this -- the above page was posted 2013 and merely says it is still being investigated. No closure. Issue still happens on some systems.
All of these, perhaps, could be harboring hidden malware.
Finally, and far less important, I don't want it to mess with windows updates. system integirty checking by sfc /scannow and windows updates are two separate issues that should be separateable by sfcfix.exe and I wonder if that is the case.
Thanks,
Harry
If I see "Cannot repair" items, I next run:
DISM.exe /Online /Cleanup-image /Restorehealth
When that is done, I run another sfc /scannow. Unfortunately, the DISM does not always fix the issue. It would be nice if the "white paper" on sfcfix.exe would explain what causes such failures and how it proposes to do a better job than DISM.
Related to this (keep in mind I have not yet run sfcfix), many times sfc /scannow shows the OneDrive.lnk as "Cannot repair" and I wonder if this is a known Microsoft bug -- you would think it would always show up, but I only see it 10% of the time and I can never be sure what it means -- Microsoft is mum about it (I reported it 6 months ago and it still shows up from time to time). It's corrupted state could be an intentional flag to Microsoft that someone has clicked or never clicked on the OneDrive shortcut. Just a dumb guess.
I also wonder about prncacla.inf reported as "Cannot repair". [Win8/8.1] GUIDE: CNBJ2530.DPB and prncacla.inf Corruptions mentions it and suggests running sfcfix.exe but I would like to know what it does to fix this -- the above page was posted 2013 and merely says it is still being investigated. No closure. Issue still happens on some systems.
All of these, perhaps, could be harboring hidden malware.
Finally, and far less important, I don't want it to mess with windows updates. system integirty checking by sfc /scannow and windows updates are two separate issues that should be separateable by sfcfix.exe and I wonder if that is the case.
Thanks,
Harry
