New
#11
Every time you run SFC /SCANNOW and find a problem you should reboot.
At times the problem or some of the problems
will be repaired on reboot.
Every time you run SFC /SCANNOW and find a problem you should reboot.
At times the problem or some of the problems
will be repaired on reboot.
Thanks for the expert suggestion.:)
Hypothetically, during a clean W7 install, how often, at what steps should one do a sfc /scan....
I run sfc from time to time as part of routine maintenance. It almost always comes up good.
However, before installing Windows updates I always do the following:
1) Run sfc/scannow to make sure all is good.
2) Make a system image
3) Install the updates
4) Run sfc/scannow again
On a few occasions Windows updates have resulted in system file corruption (or at least the sfc /scannow operation believes so). On these occasions the system files have often not been repairable. I then perform a system image restore and attempt to track down the culprit update. Recently MS have adopted a rollup update procedure which makes it difficult to identify a specific problematic update. The best strategy here is to reimage, wait a couple of weeks and try again.
This sounds burdensome and it is! You can thank MS for that.
Thanks mjf for the expert suggestion.....
1. Btw when you perform it, do you create a full backup?
2. You must be creating an image each month....?
3. If, each month and the created is fine, do you delete the old one or overwrite it, once checked?
@alexey
Just for future reference when you run sfc /scannow you can use the command below to just show relevant details from the cbs log.
Run from elevated command prompt and the file will appear on your desktop.
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
This makes it easer to see what SFC scan has done.
If there are any files it could not repair you will be able to see which files still need to be repaired.
Hi,
This is still happening, while restoring an image, despite that have none sfc errors on the new install.
Image creation is swift as always, but restoration stalls for 5-7 mins after verification process of the backup is successfully completed.
Is it cause that I/O displays a slower Write vs Read....approx 900 Mb/s (read) and 200 Mb/s (write)?
Thanks.
OR is a normal Macrium Reflect behavior?
fsutil behavior query disabledeletenotify
Results-
DisableDeleteNotify = 0 (Windows TRIM commands are enabled)
But results of trim check.exe, display....Trim appears not to be working.( or hasn't kicked in yet).
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\XPS>fsutil behavior query disabledeletenotify
DisableDeleteNotify = 0
C:\Users\XPS>
C:\Users\XPS>
TRIM check v0.7 - Written by Vladimir Panteleev
GitHub - CyberShadow/trimcheck: SSD TRIM check tool for Windows
Loading continuation data from C:\Users\XPS\Downloads\trimcheck-cont.json...
Drive path : \\.\C:
Offset : 20000452608
Random data : E4 A3 61 66 8F 1C D7 54 75 BA 35 69 81 06 28 FE...
Reading raw volume data...
Opening \\.\C:...
Seeking to position 20000452608...
Reading 16384 bytes...
First 16 bytes: E4 A3 61 66 8F 1C D7 54 75 BA 35 69 81 06 28 FE...
Data unchanged.
CONCLUSION: TRIM appears to be NOT WORKING (or has not kicked in yet).
You can re-run this program to test again with the same data block,
or delete trimcheck-cont.json to create a new test file.
Press Enter to exit...