It’s suggested more than it helps, especially on MS support pages, but for sure sfc fixes a particular set of problems. Out of about 16 times I’ve used it professionally it’s solved the issue about 12 or so times. (In 20 years, so damn you for making me feel old) And when it didn’t it’s usually because the file is also corrupt in dllcache.
Chkdsk is/was useful, imho, if you run it with the /r parameter. In my experience it became irrelevant for user systems with ssd’s.
Both are tools. Don’t blame the tool for being used for something they’re not meant for. You could technically use a power drill to hit nails in a wall, sometimes, but someone suggesting a power drill in place of a hammer doesn’t mean it’s a bad tool.
Wild_Mastic@lemmy.world 4 days ago
Same as the windows troubleshoot useless program that pop off every time a program crashes “Looking for the problem that caused the crash. Oh i found nothing”.
I’m convinced it’s just those 2 pop ups and are placed just for giving the impression of doing something, but actually doing nothing.
LwL@lemmy.world 3 days ago
I have very positive experience with that thing actually. It fixed many a wifi issue for me (interestingly, while also saying it couldn’t find the issue. It just fixed it. Probably ran something as part of its diagnostics that happened to also fix the problem)
Irelephant@lemm.ee 3 days ago
Every time a test a shitty app i made i will try to close it when it stops responding, and windows will “report the problem to microsoft”.