Tech Support Forum banner
1 - 6 of 6 Posts

·
Registered
Joined
·
204 Posts
Discussion Starter · #1 ·
Even on a brand new NVMe SSD with a clean install of windows, after windows updates and updating drivers doing sfc /scannow seems to complete saying "Windows Resource Protection found corrupt files and successfully repaired them."

Upon checking for anymore corrupt files on another sfc /scannow the system seems to be fine. I believe this is because of some leftover files that were likely deleted but I'm not sure.

I haven't done any unsafe shutdowns and take standard procedures when updating windows and installing applications. Everything is running fine.

I ran sfc /verifyonly and found integrity violations, in some cases does sfc give false reports when the system is fine?

In the case that I do think files are corrupted even without crashing and obvious issues that should be checked how bad is it on SSD write life/how many GB are written for DISM and sfc? Is it pretty much unnecessary to run either one if you might irregular stutters and don't get blatant issues?

Does anyone also know the difference between
DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\ESD\Windows\sources\install.esd

and

DISM /Online /Cleanup-Image /RestoreHealth?

The first one seems to have always worked for me in the past since it uses a direct source that is from your installation of windows.

How come websites always refer to DISM /Online /Cleanup-Image /RestoreHealth when
DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\ESD\Windows\sources\install.esd is almost always guaranteed to work without the source errors?
 

·
Global Moderator
Joined
·
51,596 Posts
I think you spend WAY too much time worrying about your SSD health, I've used SSD's since they first came on the scene many years ago. I never spent any time agonizing about if I was wearing the SSD out, and the oldest 128GB SSD I have still functions fine. My current system has three SSD drives, 512GB, 1TB, and 2TB. I just use them, and I suspect they'll probably outlast hard drives of a similar age and usage pattern.
Even on a brand new NVMe SSD with a clean install of windows, after windows updates and updating drivers doing sfc /scannow seems to complete saying "Windows Resource Protection found corrupt files and successfully repaired them."
I believe this happens primarily when the driver installation replaces windows files and the windows resource protection didn't recognize the versions. I'd had drivers attempt to install version older files, and even newer version files sometimes get flagged.
 
  • Like
Reactions: ShangWang

·
Registered
Joined
·
204 Posts
Discussion Starter · #3 ·
I believe this happens primarily when the driver installation replaces windows files and the windows resource protection didn't recognize the versions. I'd had drivers attempt to install version older files, and even newer version files sometimes get flagged.
Even so, would you run sfc /scannow anyway? It will just verify and "fix" necessary system files not including power configurations? I'm trying to change it using powercfg /setacvalueindex and am worried doing the scan will revert my intentional adjustment.
I think you spend WAY too much time worrying about your SSD
Yeah, sorry I can't help knowing if something might be wrong or I don't know about it very well I try to find answers. I will appreciate any help I can get.
 

·
Moderator , Security Team
Joined
·
1,568 Posts
There's an old adage, which goes ..... "if it ain't broke don't fix it" ...... which I think you would do well to observe.

You have started a number of topics in this forum now, and all of them are generally you worrying about something that really doesn't need worrying about.

When your computer malfunctions, then that is the time to start worrying, otherwise leave it alone. More damage is done to computers by people messing about with them, than for any other cause.
 
1 - 6 of 6 Posts
Top