Windows 10 Feature update (to 2004) Conexant driver Issue

Thanks a lot, I'll try it once it is weekend so that I have 2 days without video conferencing. Hope it goes smooth

Thanks for that quick reply. Both bluetooth and the internal mic when headset disconnected work fine. Though I don’t have a bluetooth headset that I can rely on for video conferencing, and I couldnt figure out a way to ıse the built in mic when I connect the headset. I can wait a few days to get the update without a mic, but after I get the update and download Conexant drivers, won’t it cause problems like crashes, since that is the reason that Microsoft blocks the update in the first place. My initial plan was to never go back to Conexant drivers.

Anyways, I don’t think I need the update too desperatly, so i can wait, i think they will sort this out when the 1909 end of support date comes.

Nowadays all the laptops have what is called a 3.5mm combo-jack. If you take a closer look you will see  3 black round strip that divides the entire 3.5mm headphone jack into 4 different sections: 2 of them are for stereo playback (left and right channel of the speaker), 1 for the Microphone input and 1 is for the (GND) Ground connection. So whenever you plug in the headphone jack the laptop detects all the connections and disables onboard Speakers (output) and Microphones (input). There are ways to use the built-in Microphones but it's not worth it, esp with the Conexant drivers or Microsoft basic drivers. Realtek does provide a convenient way to do so, but talking about Realtek in this thread is like talking about the kind (!) of Girlfriend we wish we had (sigh)! 

Answering your question regarding the aftermath is, Absolutely Smooth as Butter !

After upgrading to 2004, I installed the old Conexant drivers, and it's been around 3 months, and I have never ever faced any incompatibility issues, any crash or BSOD (Blue Screen of Death). In that time I have gotten all the updates including 20H2 and subsequent Cumulative updates. Also, Microsoft offered me a newer Conexant driver (version 8.66.95.70) update through "Optional Windows Update".

This is so bizarre! Why would they flag this as Incompatible when they don't cause any issue after the upgrade? No one knows why is this but it is what it is, and Microsoft does not feel the need to explain this. 

Simply put: No, you won't face any issue after the upgrade due to the Conexant drivers, as I have not faced any issue so far.

Thanks for that quick reply. Both bluetooth and the internal mic when headset disconnected work fine. Though I don’t have a bluetooth headset that I can rely on for video conferencing, and I couldnt figure out a way to ıse the built in mic when I connect the headset. I can wait a few days to get the update without a mic, but after I get the update and download Conexant drivers, won’t it cause problems like crashes, since that is the reason that Microsoft blocks the update in the first place. My initial plan was to never go back to Conexant drivers.

Anyways, I don’t think I need the update too desperatly, so i can wait, i think they will sort this out when the 1909 end of support date comes.

Still no fixes. About the registry block fix: I followed the steps, added registry key and uninstalled Conexant drivers. Now my Computer only has Windows generic sound drivers, and the Conexant driver doesn't gets automatically installed, as expected, BUT now I have a different problem. Now the microphone part of my 3,5 mm combo jack does not work. When I plug my headset in, sound comes perfectly fine, but the mic of the headset does not work. No voice input detected by any program (tried with the windows voice recorder, discord and zoom, and yes the mic of the headset does work on other devices). I just removed the registry key to get the Conexant drivers back to have a working mic, which worked, and now as you may have guessed no win 2004 update for me. I think I have to wait till the issue gets resolved completely and properly, but it has been 1 year since the 2004 update, and no fixes, like are you even trying?

That is unfortunate! 

Have you tried using a bluetooth headset? You might gotten the microphone working with a Bluetooth headset with built-in mc. 

If a working mic is essential for your daily work then I can understand the inconvenience. I guess living with the inconveniences for just a fee days to get the update might have been worthwhile. I don't see microsoft fixing the issue anytime soon or maybe ever.

Still no fixes. About the registry block fix: I followed the steps, added registry key and uninstalled Conexant drivers. Now my Computer only has Windows generic sound drivers, and the Conexant driver doesn't gets automatically installed, as expected, BUT now I have a different problem. Now the microphone part of my 3,5 mm combo jack does not work. When I plug my headset in, sound comes perfectly fine, but the mic of the headset does not work. No voice input detected by any program (tried with the windows voice recorder, discord and zoom, and yes the mic of the headset does work on other devices). I just removed the registry key to get the Conexant drivers back to have a working mic, which worked, and now as you may have guessed no win 2004 update for me. I think I have to wait till the issue gets resolved completely and properly, but it has been 1 year since the 2004 update, and no fixes, like are you even trying?