My most pointless fight was Me vs Realtek in December 2019.
For 4 months this new PC was fine, then suddenly everyone complains that they can barely hear me.
I start investigating, and my Headset has been replaced with a "default microphone" with 0 settings. Can't control gain, can't toggle noise suppression etcet. all greyed out.
This lead to a weekend of rolling back audio drivers, including one rollback that completely bricked my windows install. Every time, the second I connect the the internet, the windows update installed the new driver. I spent hours trying to prevent this update process. Windows just lies and does it anyway. It was somehow flagged as a critical security update to the best of my knowledge.
I could only have a microphone not on 1% gain if I restarted in safe mode without the internet, used third party software to completely remove audio drivers, manually install the audio drivers, restart into windows and only then connect to the internet, and never turn the machine off or reboot. I did this for two weeks.
In the end I gave up and bought a USB headset instead of a 3.5mm one, because it had its own drivers.
Then covid came and too many headphones were messing up my ears, so now I have an midlevel dynamic mic with its own drivers from the Amp, so I can talk without it picking up my speakers (though it does pick up my keyboard)
The blame is probably shared between Realtek, MSI (the mobo) and Win10, but it is an amazing example of how "It just works" explodes on you when you try to protect users from too many settings and mistakes, and then leave them with no avenue to fix something that you broke.
I had a Realtek update a week ago, suddenly I have a settings screen. I plugged in my first headset and it works again. So that's..... 11 months. Great.
My current minor gripe is that somewhere in the chain (IDK if this is Win10, Nvidia or AOC) my monitor will screw up its *sync settings in Dramatic Ways. Like dropping half of the frames bad. It only triggers when I launch a fullscreen application, then I have about a 1 in 20 chance of being in N64 land. Restarting the monitor fixed it.
Log in to comment