Same as the useless windows troubleshoot 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.
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)
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.
To be clear, it’s not that I’m saying sfc /scannow and chkdsk are altogether worthless, it’s just that they’re reflexively repeated as a solution to seemingly every issue posted on those forums. It’s more so the advice is frequently useless for the given issue, rather than the specific commands themselves.
One time I had a problem and all the suggestions were sfc /scannow and chkdsk, except one answer that said “download this extremely shady program”.
…it worked and all the replies were people embarrassed that what should’ve been an obvious virus actually fixed their ongoing tech issue.
Applies to macOS as well. These official support forums are such garbage.
Windows: did you run sfc /scannow and chkdsk? (This has never solved a single thing in my entire building PCs life, so since about 1999.)
macOS: did you reset SMC and PRAM? (This is basically a fancy restart and with Apple Silicon devices, it is literally just a restart.)
Same as the useless windows troubleshoot 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.
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)
deleted by creator
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.
To be clear, it’s not that I’m saying sfc /scannow and chkdsk are altogether worthless, it’s just that they’re reflexively repeated as a solution to seemingly every issue posted on those forums. It’s more so the advice is frequently useless for the given issue, rather than the specific commands themselves.
At least you’re able to get through to an actual human with Apple.
One time I had a problem and all the suggestions were sfc /scannow and chkdsk, except one answer that said “download this extremely shady program”.
…it worked and all the replies were people embarrassed that what should’ve been an obvious virus actually fixed their ongoing tech issue.