[nsvd2]

I usually find the exact opposite, where for Windows I can sometimes find a few SEO optimized pages with vague instructions, but for Linux I'm much more likely to hit a wiki or forum with in-depth technical information to solve my problem.

[wormius]

"Hi I'm Mohinder from MS MSP, MSVP, SUPERSTAR ASSIST, Can I have you restart your computer... once you do that, please report back if that fixes the problem"

ms.com "support" pages.

Meanwhile, Archi Wiki? That is like... the best thing and should be a national treasure.

[Telaneo]

> I usually find the exact opposite, where for Windows I can sometimes find a few SEO optimized pages with vague instructions,

It's been a while since I've had to look up Windows problems to be fair, so my experience on that front is a year and a bit out of date (and probably more, since most permanent issues would have been solved on my desktop install years earlier).

> but for Linux I'm much more likely to hit a wiki or forum with in-depth technical information to solve my problem.

That's part of the problem, at least in my experience. When I ran Windows, I'd find someone's article called 'Solution for $Error in $Program when doing $Thing', or a forum thread or whatever else along those lines, and it would in the best case be accurate and fix my problem, and in the worst case help me figure it out from there.

On Linux, that wiki page or forum won't have a solution for my exact problem, but it will help me figure it out. Linux's default case has often been equivalent to Windows's worst case when looking for solutions, but both of them very rarely ended in a true worst case (not finding a solution at all). Linux's solution will more often than not be transferable to other situations, so the knowledge gained is useful, while on Windows, the equivalent solution is bespoke and won't be useful in any other case.

[vrighter]

"run sfc /scannow"

"that didn't work. That has never done or found anything"

"I'm just going to close this issue as solved"

Most support posts