Updating to Windows 10 Version 2004/Conexant Drivers

funny you said Vintage, guess my Asus from Dec 2017 is also vintage now..... and the best part is that it runs so well, i dont really need/want to upgrade it.

HP ProBook 450 G3, vintage 2017, here, also with Conexant audio and no drivers.  Runs Ubuntu Linux just fine (I dual-boot), but the audio chipset seems to be an orphan as far as Windows is concerned.

I have a Dell Inspiron 13  2-in-1 laptop (only 4 years old) and in GREAT shape. I am a bit surprised other Dell owners are not complaining too. I dont think this is the only Dell that used the Conexant Driver.

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!