Updating to Windows 10 Version 2004/Conexant Drivers

Quoting some parts of Damien Vasse's post of 11/21/20;

"...The workaround was to change the driver of the Conexant audio device with the Microsoft High Definition Audio.

<snip>

Then, I launched the Windows 10 2020 H2 update using the Windows Update downloadhttps://www.microsoft.com/en-us/software-download/windows10

It all went well, and after several reboots, I logged in and found the audio driver again being Conexant SmartAudio HD, the one previously used before this workaround.

Seems like the issue really is DURING the update not after it's done...."

That was exactly my experience with updating an HP ENVY laptop.  Are you listening MS?  Perhaps you should remove, or at least lessen the update restrictions so people can get past your roadblock.

Update:

Hmmm.  I just ran Device Manager, and something has changed.  Under the 'Audio inputs and outputs' category there had been 2 entries, one for the microphone array and one for audio.  I'm pretty sure this was true after the 2004 update, but can't say for sure after the 20H2 update.  The entry for audio is completely gone, there is only one device.  The 'Sound, video and game controllers' category had 2 and still has 2 , the 'Conexant ISST Audio' and 'Intel(R) Display Audio'.  In any case, the audio is still working fine.

Quoting some parts of Damien Vasse's post of 11/21/20;

"...The workaround was to change the driver of the Conexant audio device with the Microsoft High Definition Audio.

<snip>

Then, I launched the Windows 10 2020 H2 update using the Windows Update downloadhttps://www.microsoft.com/en-us/software-download/windows10

It all went well, and after several reboots, I logged in and found the audio driver again being Conexant SmartAudio HD, the one previously used before this workaround.

Seems like the issue really is DURING the update not after it's done...."

That was exactly my experience with updating an HP ENVY laptop.  Are you listening MS?  Perhaps you should remove, or at least lessen the update restrictions so people can get past your roadblock.

Update:

Hmmm.  I just ran Device Manager, and something has changed.  Under the 'Audio inputs and outputs' category there had been 2 entries, one for the microphone array and one for audio.  I'm pretty sure this was true after the 2004 update, but can't say for sure after the 20H2 update.  The entry for audio is completely gone, there is only one device.  The 'Sound, video and game controllers' category had 2 and still has 2 , the 'Conexant ISST Audio' and 'Intel(R) Display Audio'.  In any case, the audio is still working fine.

Actually I agree with both of you- the problem is the existence of the Conexant HD Audio Driver DURING the Windows 2004 update process; it works perfectly fine after the update! Apparently the Conexant driver doesn't play well with Microsoft together during the ACTUAL Win 2004 update (who cares who's at fault). So after many months of delays searching the web for a solution to update and finally reading here that I could get my HP Envy I9 Desktop to possibly install the Windows 2004 update, I decided today to MANUALLY  launch the Windows 10 2020 H2 update from the Microsoft Windows Update link AFTER first just simply UNINSTALLING (not "deleting") the Conexant HD Audio Driver in Device Manager and then running the Windows 2004 update from Microsoft's site. Since I was coming from Windows 1909 it took quite awhile to complete the update itself but there was absolutely no hang-ups or problems or intervention needed from me during the update. The beauty of doing it this way was that the same Conexant HD Audio driver that I uninstalled before starting the manual update simply reinstalled itself during the update's the final rebooting and when the Windows lock screen came back after it was all done, lo and behold, I had sound with nothing more to do (and Device Manager showing the HD Conexant HD Audio driver was installed and working properly)! "It's a good thing"

Confirmed! I did the same thing with my ASUS GL-552vw laptop - switched to the MS driver, ran the Windows Assistant manual install to 20H2 and everything worked perfectly. When I booted back up, the Conexant audio driver had been reinstalled and I've had no issues at all!

Seems like Microsoft could very easily fix this and remove the block!

I also tried to update using the update assistant installer and windows 20H2  ISO method, neither of them worked for me either and the installation failed. I don't have the know how to block the driver uninstall and block method. So I will be forced to wait for a driver upday from Microsoft.

 I'm trying to update an Asus K501UX, which is quite a high spec laptop, you would think the driver that windows gave you would be on the windows catalogue if it worked for another Asus machine!!

I did search for the "Conexant Media 8.66.95.70" driver on Windows update catalog but couldn't find anything there. 

Then I googled and found a site that says it has the driver with the matching driver version 8.66.95.70 (dated 16 October 2020). Although any driver downloaded from a third-party site is not recommended, but I downloaded and installed it.

Surprisingly the Windows driver update section is no longer offering me this driver update.

This means It was indeed the one that I was offered before. To be sure I looked at my device manager section and I was right. It was indeed version 8.66.95.70 that got installed.

Now If anyone wants to try this that would have to do it at their own risk. I can't and do not recommend anyone to go and install any driver from a third-party website. But if you want here are the facts. 

The link to the driver download page: https://www.drvhub.net/devices/sound-cards/synaptics/smartaudio-hd-1

also, see that RED ARROW that I have placed beside the Hardware ID names. Mine matched with the specified ones. You should match yours as well before trying it out. That way I think you'll have more chances of being successful. 

How to find your Device Specific Hardware ID: just go to this "Details tab" and choose "Hardware ID" from the dropdown list.

Look for the "Underlined serial". Only this part varies from device to device. The rest of the ones are all same.

After download follow this guide to update the drive: 

First, download the driver .zip file from the link above. 

Use the "Download Driver" option, not the Big Greenish button that says "Install Driver" option because they will try to install their own software to install the driver. So don't use the "Install Driver" option".

Then extract the content of the .zip file in a separate folder. (You will need WinRar for this purpose). Next, follow these steps.

1. Click the Update Driver.

2. Click the Browse my computer for driver software option.

3. Select the main folder with the downloaded driver content you have extracted earlier. 

Don't forget to check the Include subfolders option.

4. Click the Next.

Windows will search the folder and will install the drivers. After installation, you will be told to Restart. and then it's done.

At the time I'm writing this there are 22 pages to the thread.  That's pretty long to read.  I'll try to summarize, but this is my outlook.  Others probably have a different outlook;

1. I do not expect an update to the conexant driver software.  Another company (Synaptics) now owns that IP.  My career was in software development, but not of this type.  Still, when someone buys someone else's IP, the support for it can become non-existent.  IMHO, the only hope is that at some point, for some future Windows release, they will come up with a brand new driver.
2. Somewhere in this thread there is a post by someone that posted a formal request to MS to update Windows to handle the driver issue.  The poster has requested that his/her request be given a thumbs up by as many people as possible in order to let MS know that people want it done.  I discovered that in order to give it a thumbs up, you need to be a part of the 'Microsoft Insider' program.  I don't think joining it is actually a big deal.  I haven't seen where you get a bunch of emails from that program.
3. Some people have gone to great lengths to remove the offending conexant device driver so that the block on windows update is removed, thereby giving you the ability to install the 2004 and 20H2 updates.  In its place they installed the default MS driver for the audio.  Some of those attempts, IIRC, were unsuccessful and others took quite some effort to ensure that the old conexant driver didn't get reinstalled.  I didn't really follow those instructions, but many people have reported success.  You'll have to search the thread for the instructions.
4. I just brute forced the 2004 update.  I have a 5+ year old HP Envy laptop I love, so before I did that I did a full backup.  Actually, HP no longer supports the laptop either.  Anyway, after forcibly applying the update I did not have any problems.  From what I can tell, the conexant driver (10.0.19041.1 dated 12/6/2019) is still the same.  I am running Win10ProX64 with the 20H2 update.  A disclaimer is that I use it mainly for MS Office stuff, web surfing, and a Zoom meeting now and then.  I do not use it for gaming or even streaming videos, so YMMV.

Numbers 3 & 4 may be highly dependent on the hardware running Win10.

Good luck.

I managed to "win" with my ThinkPad Yoga

First I tried to disable the driver (I have two other sounds systems so actually don't need it)

But Windows update kept re-adding it.

Then I tried downloading some other Conexant drivers - but windows update replaced them.

I tried (as someone suggested) the option in control panel system to stop windows updating other devices - but that didn't work for me as the driver was coming from HCL sources. (Control panel, System, Advanced system settings, hardware, Device Installation settings,)

In the end, I downloaded the driver below and used a local policy to block the device from windows update (steps following) 

It didn't appear to work - even after 24 hours (which I read was the check time)

But then the next day, I was offered the updated.

ASUS X543BA Conexant Audio Driver 8.66.75.67 for Windows 10 64-bit"

from Softpedia (I don't think MS allow links but it is here)  (in their sound cards. connexant).

https://drivers.softpedia.com/get/SOUND-CARD/Conexant/ASUS-X543BA-Conexant-Audio-Driver-8-66-75-67-for-Windows-10-64-bit.shtml

When it has run, device manager should show the Micrsoft High Defintion Audio.

The Microsoft High Definition Audio Device I am told reduces functions - but I didn't care

Don't let Windows update run as it will "correct" the driver for you!

To apply the block policy to stop Windows update putting the conexant driver back (or set the related registry setting directly)  you need know the hardware ID for your Conexant card.

This can be obtained from device manager

load device manager (windows key & X will offer it)

Find the card (under sound).

Double-click on it, or Right-click and select Properties from the context menu.

Choose the Detailstab.

From the list of properties (pull donw) choose tHardware Ids.

You will see a lsit of hardware IDs (usually several). The first one is the specificHardware Id of your device but most articles advise using the 2nd one (shorter) which is more generic [stops a similar driver appearing]

Copy the string (right click) and paste it somewhere like notepad a notepad

In effect, you need to to add an entry to the registry.

The easiest way for Pro users is to create a lcoal group policy 

Run  typing gpedit.msc(either windows &R or type it in search). [you need to be admin -  I believe Windows home users have to edit the regsitry]

You need to naviagate down the policy tree

Computer Configuration > Administrative Templates > System > Device Installation > Device Installation R estrictions

and then open the policy Prevent installation of devices that match any of these device IDsYou need to enable it and then use the Show... button to bring up the lsit of hardware IDs that are blocked. On here you need to paste in the hardware ID you got from device manager.

You can force a policy from the CMD prompt (or Powershell) by runing GPUDATE/force

For home users (or those who can;t be bothered witha policy on Pro) The registry key is 

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceInstall\Restrictions

searching for this will give instructions on what a home user needs to do

With luck this should stop windows update helpfully updating the your driver to the one Windows doesn't like.

(Note that you need to apply the softpewdia driver update first - otherwise yoru policy blocks this!)

Remember, I then had to wait a couple of days for MS to "clear me" but I now have Windows 2004.

[If it turns out that MS just relented for my device in the interval by chance - apologies - but I think it was my efforts that let me do this).

Of course, my card is not working uder windows ver 2004 as Windws is complaining that it can't update the driver because it is forbiden by system policy! If I am feeling brave I might let it go to see what happens but as I don't actually need the card....

The problem is that I guess that update will not "honour" the HD Audio device but will try to replace it with a (the?) conexant driver - which may cause issues. It is not clear to me with if the probelms only occur during update . The MS post says "Windows 10 devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen during or after updating to Windows 10, version 2004."

So a "solution" perhaps for those who don;t need their sound card!