[naikrovek]

If you are arguing that Windows audio is as troublesome as Linux audio, I think you'll find a lot of people willing to debate you.

The windows troubleshooters will fix the things they are designed to fix. They're just powershell scripts with a wizard-style interface. I've had them fix many networking issues on certain computers reliably. I haven't ever had an audio problem on Windows that wasn't caused by me, so I've never needed to run an audio troubleshooter for audio.

Windows has log files too, you just need to know where to look. Usually event viewer will have what you need, but sometimes you'll need to run a diagnostic that generates logs, or you'll just need to know where the logs are.

[girvo]

I have never, not once, in two plus decades of Windows usage had the troubleshooter fix anything.

[naikrovek]

How often do you try them?

Saying "Windows troubleshooters never work" will often lead to someone never trying Windows troubleshooters, which only reinforces the idea that they never work.

None of them are perfect, of course, and none of them will fix any given problem, but I always try them first, even if I have low hopes for success. Sometimes I am surprised. Sometimes I have to find a fix for myself.

[_a1_]

Troubleshooters never worked for me as well. It's hard NOT to try a troubleshooter, because it's suggested by Windows on every occasion, but after I've discovered that "troubleshooting" in Windows terms means "first try restarting the service, then try restarting the computer, then try reinstalling windows" then indeed I've stopped trying them completely.

I mean, if the user doesn't change system settings at all and uses external drives for their cat pictures then reinstalling the system isn't such a bad advice. The problem is that if someone uses Linux, then this person isn't satisfied with this style of system usage.