Updating to Windows 10 Version 2004/Conexant Drivers

I'm also stuck at 1909 at the moment. I received an update of the Conexant driver on March 13th which bumped the version to 8.66.95.70 but no update yet.

According to device manager the new UCI64A231.dll is out of the range that Microsoft has blocked, but I noticed that some old dll files (UCI64A134.dll and UCI64A195.dll) are still present in the system32 directory. Is it possible that these old dll files block the update to a new version? If so, would the solution be as simple as to just move these old files to a temperary location?

I too was stuck on 1909, I must have had a driver update and then later got an offer to upgrade.

Guess what, IT FAILED TO UPDATE!!

I again on restart was offered the same update and once more failed. I thought I'd try to use the windows hi def driver on a third attempt and once more failed. I now think microsoft, are the worst company ever to grace the planet earth.

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.

Put your computer off line. Find the Conexant driver in the device manager, double click it to bring up the properties box and choose disable.

Tried but no successs with updating using Iso!

After rollback windows gives this message:

Yes, that is exactly what can happen with a lot of devices. I myself just tried to brute force the Win 10 2004 update with an ISO. but the installation was interrupted at a letter stage. You just can't tell when the installation will get interrupted at which stage, let alone having success in installing the 2004 update. 

I have successfully installed the update a while back by replacing the Conexant drivers with generic Microsoft drivers and then waited for 2-3 days for the Win Update notification. 

A lot of people have experienced a lot of different situations regarding this update hack. but to me getting the 2004 update through Windows Update is by far the best way that will ensure nothing will go wrong while the update process. 

The most frustrating part is to update to the 2004 version, coz after that Microsoft just seems to ignore the Conexant driver situation and will offer the next 20H2 and all subsequent cumulative 20H2 updates.

The best part is that, after the 2004 upgrade prior to getting the 20H2 update, Optional Windows Update offered me the long-awaited Conexant driver update that is according to Microsoft compatible with 2004 and the later versions.

That is what my experience is so far.

If your question has been resolved or you don’t require any further help with your problem please feel free to mark one of the replies as answering your question so other users with the same/similar problem can easily find the answer.

Also feel free to leave a rating to the user who helped you the most.

If you still require help then please continue the thread.

Thank you & have a great day/evening.

Thanks Time Lady.  At least I have some hope and can quit searching the web for "non-existent" drivers !!!