Updating to Windows 10 Version 2004/Conexant Drivers

I too decided to be patient and wait for the Windows Update block to be removed and have 20H2 offered to my system without performing any gymnastics.

Well, last Friday (April 9) … 20H2 was offered to me (no driver updated was ever offered or installed by Windows Update or my computer manufacturer, Dell). However:

1. During the last stage of the update process while within the Windows Update window - *before* the first reboot (from Windows into the upgrade environment), the progress stalled out at 61%. After waiting for more than an hour …
2. I went into Event Viewer and saw an error message that the upgrade to 20H2 had failed. However, no such warning was presented within the WU interface, as a notification, or in any other way! Had I not scanned Event Viewer, I would not have known the process failed!
3. I rebooted (as per MS advice that some systems may fail, and rebooting can resolve), went back to WU and again, process stalled at 61%
4. Did some research, and the stall at 61% seems to have been a common issue with systems having Conexant drivers during the insider phase of the 20H2 release, and for some during the general release
5. Rebooted again, disabled the driver (but did NOT delete or change to a generic), rebooted, launched WU … still stuck at 61%
6. Rebooted again, deleted the driver and its files (from within device manager), did *not* reboot, and then ran WU update again
7. This time, 1909 successfully was upgraded to 20H2 (and pretty quickly too)
8. After logging into Windows post-update … the *same* Conexant driver was downloaded and installed by Windows (which is something others have also reported).

So the good news is – I am on 20H2 and all seems well.

The very bad news, which seems to have impacted you as well – MS *offered* the update via Windows Update, which one would assume means they lifted the block and resolved the issue. I would probably have been stuck at 61% indefinitely (in my quick research, some reported being stuck at 61% for days and never completing the upgrade), had I not known where to look/what to research.

Let me know if you want any more details. Hope this is helpful to someone!

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.

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?

There is no WUID / KBID for Driver Updates... It just shows Conextant SmartAudioHD Driver - 8.xxxxxx ( I don't remember the exact number) - Driver Update

I have received the update as mentioned in this post