I have had to type equally obvious strings into the windows command line. Or rather, corporate IT support has typed stuff like that while i watched. If i had this kind of problem with a windows machine of my own, I’d contact warranty support or throw it away and buy a new one, depending on the age of the device. And i have had problems like this on corporate windows machines. Just last week i spent an hour trying to get Teams to work on my employer’s laptop, finally gave up and called the help desk, and it took the help desk guy 40 minutes, which included typing a bunch of stuff into the command line.
I’ve also had several instances of not being able to get the sound to work on Windows devices. Like, it will work fine for system sounds, but not for a zoom call. And i have to go digging because there are three separate utilities to control the sound and i can’t find the right one.
I want to say that so far, EVERYTHING EXCEPT AUDACITY JUST WORKED. The screen worked, the touchscreen worked, the touchpad worked, the keyboard worked, the screen even flipped upside down when i turned the laptop into “tent” mode. And my headphones connected over Bluetooth without any issues, and i happily watched YouTube and Netflix on the thing, all without touching the command line.
Audacity is weird and fussy about its audio feeds, both in and out. I’ve had to fiddle with it on both my Mac and my Windows computers, too. I assumed that I’d need to find someone who uses Audacity in Ubuntu to help me, and I’m delighted that Linux users here have suggestions.
But I think there’s a valid and objective point to be made that Linux by its very nature and heritage requires a lot more techie-type tinkering than Windows typically does, and if you have no experience with it, this can be quite a challenge.
That’s actually not been my experience, despite my looking for help here. My experience is that modern computers just work until they don’t. And then you are kinda screwed. And if you are lucky, you can find other people who use the same software and have had the same issues who can help you. That’s why, when my husband asked if i believed in the wisdom of crowds, i said “yes”, and installed a popular package. Because the more popular the package, the less screwed you are. But at least there are techie people in the Linux community who might help, and i know a lot who might help just to be helpful. You generally need to pay someone for help with Windows. And it still might not work.
By the way, because i was having this issue, and i wanted to use Audacity on my flight, i updated the Windows partition’s copy of audacity and copied all my source files there. And i booted into Windows on the airplane, and failed to connect my headphones at all. I was able to debug that and get them to work again on the ground, but i wasn’t going to debug a Bluetooth problem when there were 15+ Bluetooth devices within range of my laptop all saying, “I’m here, pick me!”.
So i gave up and watched YouTube on the Ubuntu partition, with my wireless headphones.