Updating to Windows 10 Version 2004/Conexant Drivers

Yes, that is a kick in the face to all users who still do not have their blocking update. I got the same push to update which I would gladly do it MS had it together! Obviously, the right hand is unaware of what the left is doing.

MS has a terrible workflow of how to develop, test, beta, and then push out updates. BSOD last week on a print spooler security update. What a colossal screw-up that was and they still haven't pulled the update even though they said they would. People at Microsoft really need to start losing their jobs because it is apparent there are many not doing their jobs. Heck, they even had issues with 2004 and their devices, the Surfaces. I could go through the total mess of updating with all the hacks and workarounds. Why should I waste my time doing what someone is supposed to be getting paid to solve? 

If Microsoft doesn't care about its users then why should I care about Microsoft. Time to start shopping for a Macbook and finish tweaking Linux flavor on my older laptop for use on this one.

I have a Lenovo Thinkpad T420 with Conexant audio drivers, stuck at 1909. I've decided to just wait to see what MS does. Funny thing today when I booted the PC. Windows message area has a message: "Your version of Windows 10 will reach end of  service soon. Click here to download a newer version of windows 10 to stay supported".  Click puts me in "Windows Update". Ha Ha! As if I haven't already been checking every time I power up the PC for the last 6 months. MS has a cruel sense of humor.

Conexant audio drivers - Microsoft Community

I finally managed to get back to the standard MS HD audio driver, which works fine for me. The only odd thing that does seem to happen is the audio gets muted random. But I guess I can live with that.

I really don't understand why MS does not remove the Conexant driver from their auto update policy. 

On a sidenote... when working on a Zbook 15 G3, the Conexant drivers caused no issue at all..

I just wanted to shout out a huge thank you to all members here which "solved" this issues.

Just yesterday I noticed that my Laptop (a Lenovo Ideapad from 2017) was missing the two newest builds (May 2020 and October 2020). It was just by coincidence since I upraded an almost 8 year old Dell laptop to make it usable for home office due to pandemic. There I noticed that this old laptop got without any problems the October update...

So I found this thread here.

The way to do update is quite easy, this have been my steps:

• Delete the complete Conenxant device in the device manager
• Delete the UCIxxx.dll (mine was UCI64A132) - not sure if necessary, see later step
• Let the device manger check for new hardware - it will find the audio-device and install at first the generic Microsoft-Driver. Just afterwards (only moments later) it will install the Conenxant driver.
• Open up the properties of the audie-device and roll back the driver to the previous driver (clicking on "previous driver/vorheriger Treiber" in the properties. To make things sure I deleted again the UCIxxx.dll. Maybe this is not necessary in the first step?
• then you will have the generic Microsoft driver. Mine although stayed in place even after restart. Sound worked find with it.
• Wait for the update to come oder use the Windows Updater Software

I added the driver update block as well to the registry but I think this is not necessary. 

After the update the Conexant Driver (or at least what ever this is?!?) is back - splitted in loudspeaker and microfon (before the update is was just one device). 

The provider of this driver is Microsoft but my volume adjust bar states Conenxant Smart Audio HD (which it did not when the generic Microsoft driver was installed before the update.)

Everything is working fine since.

thanks again to everyone!

br

Sokrates

Thanks. More insights by you. I don’t know why Microsoft doesn’t fix these issues.

I think that, as a joint effort, we've found a way around this problem, which should not still exist, and which Microsoft really must address and FIX as soon as possible, given it is now 10 months since it was first identified.

The next Feature update is 21H1, due in the first half of 2021, and I presume that 20H2 will get the usual 18 month cycle. We might hope that this is solved for 21H1, but given that it hasn't been for 2004 and 20H2, the omens are not good.

As I have said before in this forum, it is one thing for end-users to solve, or more properly, circumvent this problem once around, with apparently zero assistance from either Microsoft or the hardware vendors.

However, unless the issue is solved and sorted at source by MS, I cannot see that it will magically disappear as a recurrent problem in future W10 updates i.e. it will always be there, as long as the machines have hardware dependent on Conexant/Synaptics drivers and their correct functioning in Windows. If that be so, there is no guarantee that the methods above will work, or that a whole slew of new problems will not arise.

I'm not sure how anyone can apply more extreme pressure to Microsoft (and perhaps the hardware vendors also) to fix this, but it needs to be done.