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.

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..

You may put back the original drivers of conexant from your installation CD or the your model PC drivers from the website. It installs fine and you will get back the original sound quality.

I have two HP Envy 17" laptops that have Conexant hardware and are stuck on Windows 1909:  "The Windows 10 May 2020 Update is on its way. Once it’s ready for your device, you’ll see the update available on this page."

Windows 10 Pro, version 1909, reaches the end of servicing on May 11, 2021 - less than two months from now.  Unless a fix shows up in the next two months, how can I use the HP laptops, given any security vulnerabilities will go unpatched?  I'm not going to uninstall the Conexant drivers, force an update, and let the drivers reinstall, because I can't rely on the stability of the resulting setup.  I will just junk the PCs and remember not ever to buy HP again.

Hello,

My daughter’s Lenovo G50-80 has the same issue. Blocked on version 1909 it says that version 2004 will be available soon. It’s a pity that a year has passed since the first warning!

Now, Conexant (/Symantec) don’t care, Lenovo (even though I think that they are responsible for what installed as OEM) too. Microsoft says that they are working to find a solution.

The point is that there is now an alert on the notebook that Win 10 1909 will soon no longer supported.

Isn’t really possible to publish a semi-official workaround, write a patch or something?

As somebody else pointed out before, if the issue was not present on previous version of Win 10, why it jumped out with versions 2004 and 20H2?

It would be enough to give the possibility to uninstall Conexant audio and prevent it from reinstalling automatically, so that to switch to a generic MS audio while updating to 20H2.

Hello,

My daughter’s Lenovo G50-80 has the same issue. Blocked on version 1909 it says that version 2004 will be available soon. It’s a pity that a year has passed since the first warning!

Now, Conexant (/Symantec) don’t care, Lenovo (even though I think that they are responsible for what installed as OEM) too. Microsoft says that they are working to find a solution.

The point is that there is now an alert on the notebook that Win 10 1909 will soon no longer supported.

Isn’t really possible to publish a semi-official workaround, write a patch or something?

As somebody else pointed out before, if the issue was not present on previous version of Win 10, why it jumped out with versions 2004 and 20H2?

It would be enough to give the possibility to uninstall Conexant audio and prevent it from reinstalling automatically, so that to switch to a generic MS audio while updating to 20H2.

I have updated my HP Envy 795 desktop using the workaround I described earlier in this thread, and it is running OK, with several Quality Updates since. However, I am in touch with another user of this particular HP model, and who, like me, wasn't seeing the 2004/20H2 update being offered, but who decided not to use the workaround but to wait for the update to be presented to him via WU.

I had a message from him on Saturday 13th March 2021, which I will quote:-

"As of yesterday, the 2004  Feature Update for this machine was still "on its way" and I was beginning to get more than a little concerned that support for 1909 is due to expire this September. And this morning I got a Notification from Windows update to this effect. Checking, Windows update now showed 20H2 as being available, so I've applied the update, and the inevitable updates to the update and now am running happily on 20H2."

It therefore seems that "something" is happening to enable affected Conexant machines to receive an update via WU, although, as usual, there is zero explanation or information from MS or HP to assist end-users. In the absence of any said information, it's impossible to say if other affected users will receive an update as per my correspondent's experience, or indeed, at all.

In this thread, I have previously said that this situation is totally unacceptable; either because people haven't been offered the updates at all, or because of potential problems with future Feature updates for those of us who have used the workaround to get to 20H2. Hopefully the experience of my correspondent means that some form of override or fix has been applied for 1909 users, and that this will apply to updates beyond 2004/20H2 as well. I cannot believe that Microsoft and the major hardware vendors (HP, Lenovo and perhaps others) can leave this unsolved.