Windows 10 Feature update (to 2004) Conexant driver Issue

So it was a bit weird for me...

First of all, I uninstalled conexant on Friday last week, and then waited 5 days for the update, but no it never showed up and the "we're getting things ready" thing stayed there. On Wednesday I gave up. But, I had to actually format (reinstall) my Windows anyways (because of my hard disk, nothing to do with here), so I did so. I had an old (I think windows 1903, definitely older than 1909) installation media, and I reinstalled Windows with that. It installed fine, then I immediately added the registry key. It first updated to 1909, then and hour or so later it offered me 20H2. Now I am using 20H2 with Conexant drivers just fine. 

The thing I don't understand is Conexant drivers seems to run, why don't Microsoft just let users to update?

Anyways, thanks to everybody who helped.

So it was a bit weird for me...

First of all, I uninstalled conexant on Friday last week, and then waited 5 days for the update, but no it never showed up and the "we're getting things ready" thing stayed there. On Wednesday I gave up. But, I had to actually format (reinstall) my Windows anyways (because of my hard disk, nothing to do with here), so I did so. I had an old (I think windows 1903, definitely older than 1909) installation media, and I reinstalled Windows with that. It installed fine, then I immediately added the registry key. It first updated to 1909, then and hour or so later it offered me 20H2. Now I am using 20H2 with Conexant drivers just fine. 

The thing I don't understand is Conexant drivers seems to run, why don't Microsoft just let users to update?

Anyways, thanks to everybody who helped.

I think I have an idea about what actually did happen here. 

When I tried installing the 2004 version back in September, after replacing Conexant drivers with Microsoft basic drivers (with the "Rollback drivers" option from device manager) and then putting the Registry Block, I had to manually search and remove all of the Conexant Drivers leftover files from Win 10 install directory including a Backup of the Conexant drivers from System 32 > DriversRepository folder. There were a lot of leftover files that I had to delete. Only after then I got the update offered to me.  

Now, this might have exactly happened to you as you didn't removed the leftover files and waited 5 days but didn't get the update offered. But when you Reinstalled WIn 10, you basically removed all traces of the drivers and promptly put in place the block. Maybe that is why this time you got the update offered without any issue.

I am assuming you didn't install the Conexant drivers after updating to 1909 from your installed 1903 prior to upgrading to 20H2.

Am I correct in my assumption? let me know.

And congratz for finally upgrading to the latest version.

I am getting confused. I have a Lenovo Yoga 13 laptop bought in 2014 with a "Conexant HD" sound device.

It started off as Win 8.1 and I then upgraded it to Win 10 years ago.  It has installed all of the updates to 1909 and continues to install updates to this. It is blocked by Microsoft from updating further.  

With any other "PC", where I could easily replace the OS SSD I would clone the OS disc, take out the "original" and play with the copied clone to try the options above.  This is risky with the yoga - strip down to take out the SSD is (for a mere mortal) not really possible.

Taking an image is risky as reinstalling from an image doesn't always seem to work for me. I don't want to be left with a laptop I have to reinstall windows from scratch as I am not sure all of the MS office and Adobe software would reinstall - its all very serviceable but dates from 2014!

SO I have tried some "gentle changes" and taken "restore points" before each one.  The first thing I did was to update from the Lenovo web site - this updated the Conexant driver from one dated 2014 to one dated 2016. Not a lot of use.

I then searched the web for later driver files for other Lenovo devices. I found several - one of which was purposely designed to allow the update to version 2004.  HOWEVER with these the laptop "blue screened" either on loading or after a few minutes. I had to use the restore point to get back to the stable 2016 sound driver.

I also tried loading generic MS drivers by uninstalling the Conexant driver - same effect - blue screened. Had to go back to the 2016 Lenovo driver.

I am not going to start deleting Conexant files from the registry if I have no idea what they do!  This process so far seems to have left me with rogue Bluetooth entries even though I haven't changed any Bluetooth drivers!

So I am really stuffed by Microsoft here. Everything I have done seems to lead to instability. Perhaps this is why Microsoft still says "Investigating" - they don't know what to do either. Am I to be stuck on Win 10 version 1909?

Mel

I  simply went to device manager and used  "UNINSTALL device"  for the Conexant SmartAudio.

1. I manually  started the Windows 10 2H20 update  assistant

2 ) windows 10  download  started, installed "something", followed by restart.  Still my "old" Windows 1909  

3)  system restart  did  re-install Conexant Smart   

4)  I did another UNINSTALL device

5)  started new Windows 10 update assistant  and new download started 

6. latest windows 20H20  (October 2021)  installed 
7. Conexant device working and no issues so far

HP SpectreX360 15-A

Thanks for this site and all the information provided