Windows 10 Update breaks mic input

Since the following windows feature update (please see attached image). Any mic I plug into my computer no longer pics up sound. I use this PC to capture interviews I conduct. I do nothing else with it. Everything worked before the update. Now I can not record audio. My sound board is the monoprice 8-Channel Audio Mixer with USB https://www.monoprice.com/product?c_...seq=1&format=2

My webcam is the logitech c920.

The system is a windows 10 home
The cpu is the pentium G4400
It has 4 Gb of RAM
The OS version is 1803
The OS build is 17134.81

You need to allow mic input in windows settings under settings > privacy > microphone

image

1 Like

I did a support session with a Microsoft support tech. We rolled back the install to an earlier build and this resolved the issue.

Well… that was possibly poor advice from them. In either case when you upgrade again, that’s where you need to enable your computer to allow mic input. you might need to restart whatever was wanting mic input or allow the mic specifically in the app if its a new windows app. 1803 changed how win32 apps are handled, and they now also go through the privacy settings if they didn’t already.

2 Likes

Pretty sad that MS doesn’t know how their own OS works. Just another tribute to Windows 10 being an utter failure.

Support tends to be like that. Microsoft aren’t the only ones who suffer that problem, that’s almost universal. (Windows 10 is actually a huge success when you look into it.)

Their support was dog crap with ME, 2000, XP, Vista, and 7 too.

Same with Apple. Same with Cisco. Same with System76. Same with Dell. Same with Lenovo. Same with VMware. Same with Geek Squad. Same with internal IT.

Sometimes people don’t know something, or they’re scripted, or they’re meeting a quota, or they’re told not to escalate. Hardly attributed to the millions of people using Windows 10 without issue daily to accomplish their research, build and design products, build software, and the billions of other tasks Windows does well.

I’ve had it where it’s simply that support don’t have updated documentation for newer issues yet, or they were missed or unknown until reported.

1 Like

Yeah, that’s definitely common.

On the other hand, I’ve had a catastrophic issue with routing and Exchange, and Microsoft support jumped on and in 10 minutes walked us through fixing the DNS server.

My point was, bad support has been a thing since support existed. It’s not indicative of how good or bad an operating system is.

2 Likes