Updating to Windows 10 Version 2004/Conexant Drivers

Having lost patience with Synaptics/Microsoft to pull their finger out, I took ideas from this thread proceeded with the following:

1. I Googled using the Hardware ID listed in Device Manager\Sound, Video and game Controllers\Conexant SmartAudioHD\Details, under Property, Hardware Ids Tab. 

Google found a driver listed under a different computer to mine - dated 07-Sep-20, Ver No': 8.65.316.70. I then searched HPs support site for that computer model, and downloaded its driver.

2. After Downloading the driver (sp109031.exe), unpacked it and searched inside file chdrt.inf (setup information file) to make sure my Connexant Hardware Id is listed. Once confirmed, I installed the driver without issues or error messages. After reboot all worked.
3. Two days later, Windows Update offered 20H2 update. I then installed it, but installation ended with a BSD. 
4. I then changed the driver to High Definition Audio Device and reran the update. This time 20H2 update ran uninterrupted and completed cleanly. After update completed I checked which driver was installed under Device Manager\Sound, Video and game Controllers, only to find driver dated 07-Sep-20, Ver No': 8.65.316.70 reinstalled.

While the logic of BSD occurrence during first installation of 20H2 alludes me, my computer has been working without issues for the past 10 days.

This reminds me of a problem that Office (both 2019 and 365) had starting in 9/19.  There was an annoying message about 'Restart Office to apply changes to your privacy settings'.  It came up almost anytime you started Outlook or even Excel.  I'll post a link to that discussion at the end.  Anyway, it wasn't really clear what that meant, and nothing that could be done by mere mortals could get that message to go away.  Some things got it to go away for a couple of days, but then it came back again.  MSFT never addressed that issue in the discussion, and no solution was ever given.  Then, 6 months later, the message simply disappeared.  We guessed it was some update to either Office or Windows that fixed it, but MSFT never said anything.  Perhaps this issue with the Conexant driver is the same, it was fixed and they just went back to whatever else they're working on.

Anyway, the discussion for the Office problem is here.

Hi again all, I finally tried the "blocking method" after changing my driver to High Definition Audio Device. I have tried so many ways to get the update and nothing seems to work for me, every time I try it gets to almost the end of the update and then fails! It reverts to my original setup after rolling back the update.

Having tried to update over eight times I'm at a loss now and fear I will have to wait for MS to provide the update.

The driver is:  Conexant , Dated  8/9/2015,  Version 8.66.16.59

My device hardware ID is : HDAUDIO\FUNC_01&VEN_14F1&DEV_510F&SUBSYS_1043157F&REV_1001

                                           HDAUDIO\FUNC_01&VEN_14F1&DEV_510F&SUBSYS_1043157F

I have googled for another suitable newer driver but can find nothing for my device ID.

I'm still waiting for the fix on this, and I haven't tried any workarounds. This is because I've already had a full share of trouble with the HP KMODE  BSOD Lockout in the summer. My Conexant driver is 8.65.282.54, which is not one of the affected versions.

However, in the ISST Audio Driver problem description, my UCI*.dll file is uci64a189.dll, and the version is 7.189.0.0, which puts it squarely in the "affected" list.

It's therefore in the typical HP/Microsoft position; namely half-right (or half-wrong), but definitely half-cock.

Anyone else similarly affected, and if so, have you updated? If you have, how, and what happened?

You have to get rid of any of your conexant drivers by installing the latest "high-definition-audio-device" by MS manually as described earlier in this threat and thereafter blocking the driver update as also described above.

Be sure, you have safely blocked your device by waiting a few days and restarts and check, that the conexant drivers are not installed again!

Then try as also described above.

I did so with success, however did not dare to remove the block until now. MS drivers are working fine enough for me.

PS: Are you sure, your conexant-drivers are the only problem? As you did not get a BSOD but "only" a rollback, you might have another problem on top? Thats why I updated with media creation tool and all austostarts and non-MS services deactivated...