I can’t believe they are getting away with so many bullshit non-solutions to the point where you wonder if they even know how to read.
I wonder if they trained AI on this. Might explain some things
Yup, spot on.
Somewhere in the not so distant future…
Google Search: “Install printer driver windows 11”
Result from random blog:
“My first experience with printer drivers was 35 years ago. My grandma had an IBM PS2 that ran MS DOS and an HP Deskjet printer.
It connected to the computer via a parallel port and printed a whopping 1 page per minute. Every year at Christmas, Grandma would print off her famous pecan pie recipe and we would all gather around the printer, eagerly listening to the sound of the print head slowly whooshing back and forth in anticipation of the tasty goodness to come. Blah blah blah. Five more pages of meaningless stories that have nothing to do with installing print drivers followed by a solution that only works for Epson printers.”
the funniest part of the story is the idea that anyone’s grandma in the 90s had a computer and printed recipes, instead of a handmade old growth hardwood box full of 100 year old recipes handwritten with a quill pen
edit: nvm, my brain didn’t register the “in the future” bit
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.
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.
For me, someone who uses a Mac for work but still has to use the office environment, it goes something like this:
Google the issue
Google the issue + office for Mac
Find a forum about the exact issue I’m having
Loads of people commenting having the same issue
Expert answers and says “That feature is not available for Macs at this time. How about you post it as a suggestion for the devs at this link here>>>”
Post is minimum 3 years old and there’s still no solution.
Gee thanks.
