Windows 10 Feature update (to 2004) Conexant driver Issue

"Make it a Conexant-Happy new Year please Microsoft!!"

I don't see it happening anytime soon. If it really was the case Microsoft would have done it by now. 

A lot can happen if you install a driver that is not your manufacturer and device-specific, and BSOD is one of them.

Unless you install drivers specific to your manufacturer and device that complies with the issues listed on this doc https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004#known-issues , you won't be able to update to 2004 or 20H2 version, with the Conexant drivers installed on your device.

This all looks well and good, but I just want to turn my Lenovo Yoga laptop on and for it to say update to 2004 or 20H2 available!.

I have tried other allegedly suitable Conexant drivers and they just cause blue screens!

Make it a Conexant-Happy new Year please Microsoft!!

Mel

Hi Rezaul_K,

Thank you for all of your help and I am happy to state that my system is now at Windows 10 Pro 20H2 with the sound working!  Your help was invaluable.  Here was my experience:  I had not seen your update, but this morning upon booting up; my system appeared to have applied an experience update.  However the Windows version was still showing version 1909.  So I am not sure what that was about.  After running Windows update twice, on the second run it gave me the option to download and apply 20H2 (not 2004)!  I did it. Upon completion of the 20H2 update and a few reboots, the sound was still not working and I was still getting the policy restriction error when I tried to update the driver as mentioned.  I went in and deleted the DeviceInstall key and all subkeys I had put in as per your instructions.  Rebooted.  Went to Device Manager and ran Update Driver on the "Other Device", it discovered and installed the Conexant driver, rebooted again.... and then boom, the sound is all good now!

I think my misunderstanding was that I thought that by restricting the Conexant audio device update via the registry, Windows would have automatically installed the Generic Windows Audio Driver being talked about and I would have sound. I also thought that after applying the 20H2 update, the registry entry restricting the device update would have been automatically removed.  I must have misunderstood and made a few wrong assumptions.

I am still not sure if I skipped update 2004 or I just missed noticing it getting applied.

NOTE TO OTHERS: While I only had a day without my laptop's internal speakers working, I was able to have sound via a Bluetooth speaker and Bluetooth headphones.  So I was never completely without sound.

I immediately came here to give you the good news and I found that you had already responded with a fix as well.  Thank you for the quick response!

First of all, I am glad that I could be of help. I myself had gotten help from the Microsoft community as you did.

I want to clear up something here. 

You suspecting whether you skipped upgrading to the 2004 version is; Yes, you did. As 20H2 is out now, and it being the latest update available (in reality it's an extended version of the 2004 version with some features added) Microsoft will offer it to anyone trying to upgrade from 1909 or any older build version of Windows 10.

About you getting an Experience update; Yes it's kind of a newer thing starting from the 2004 version (I believe before it was exclusively available only in the Developer Preview Build, not on Public Stable Builds. We are on Public Stable Builds). If you go to Settings (Win 10 new Settings panel) > System > About; down at the bottom within "Windows Specification" you will see the Feature Experience version. I myself have searched for this but couldn't find anything explaining what it is. Even Microsoft is vague about explaining it. But I think we don't have to be worried about this. 

The whole point of the Registry Blocking method was to prevent Windows Update from automatically Updating/Re-installing the Conexant Device Drivers that we have chosen to Uninstall; the only incompatibility that prevented us from getting the new 2004/20H2 upgrade. 

About you without a working internal/built-in audio; It was only because there was no driver to route any audio output via the audio combo 3.5mm headphone port.

Finally, I am glad that you have managed to solve the issue by urself. 

Cheers 👍

Hi Rezaul_K,

Thank you for all of your help and I am happy to state that my system is now at Windows 10 Pro 20H2 with the sound working!  Your help was invaluable.  Here was my experience:  I had not seen your update, but this morning upon booting up; my system appeared to have applied an experience update.  However the Windows version was still showing version 1909.  So I am not sure what that was about.  After running Windows update twice, on the second run it gave me the option to download and apply 20H2 (not 2004)!  I did it. Upon completion of the 20H2 update and a few reboots, the sound was still not working and I was still getting the policy restriction error when I tried to update the driver as mentioned.  I went in and deleted the DeviceInstall key and all subkeys I had put in as per your instructions.  Rebooted.  Went to Device Manager and ran Update Driver on the "Other Device", it discovered and installed the Conexant driver, rebooted again.... and then boom, the sound is all good now!

I think my misunderstanding was that I thought that by restricting the Conexant audio device update via the registry, Windows would have automatically installed the Generic Windows Audio Driver being talked about and I would have sound. I also thought that after applying the 20H2 update, the registry entry restricting the device update would have been automatically removed.  I must have misunderstood and made a few wrong assumptions.

I am still not sure if I skipped update 2004 or I just missed noticing it getting applied.

NOTE TO OTHERS: While I only had a day without my laptop's internal speakers working, I was able to have sound via a Bluetooth speaker and Bluetooth headphones.  So I was never completely without sound.

I immediately came here to give you the good news and I found that you had already responded with a fix as well.  Thank you for the quick response!

I have a question, where did u find the info about the registry to block the automatic installing of Conexant drivers?

I want to do it, too.

As I happened to be on Win 10 Home version, I had to use the Registry block method.

There are two different method to get the job done:

    1. Group Policy Editor Method (requires Win 10 Pro, because only Win 10 pro have access to group Policy Editor): Much easier. This method basically does the necessary Registry Modifications for the user. Because modifying any Registry values without knowing, will result in unstable Windows and will eventually CRASH and led to Re-installation of Windows.   

     2. Registry Method (both Pro and Home users can use because both have access to Windows Registry): a bit complex compared to GPEDIT method. But if followed carefully, is nothing to be worried about.

Group Policy Editor Method (only Win 10 Pro) : Follow this link. How to Disable Automatic Driver Updates in Windows 10? | Windows OS Hub (woshub.com)

Registry Method (Win 10 Pro and Home): Follow this link: Prevent Windows Update from Updating Specific Device Driver | Tutorials (tenforums.com) 

 Now there's some issue when following Registry Method that some might encounter, that I think I need to explain.

WARNING: Be extra careful when MODIFYING/EDITING Windows Registry. DO NOT TOUCH ANY REGISTRY ENTRY VALUE OTHERWISE KNOWING FULLY WHAT THAT ENTRY DOES. ANY IMPROPER AND UNNECESSARY MODIFICATION WILL RESULT IN CRASHING OF WINDOWS. 

ALSO I HIGHLY RECOMMEND TAKING A FULL SYSTEM DISK (C DRIVE) BACKUP BEFORE FOLLOWING THROUGH THE MODIFICATIONS FOR ANY POTENTIAL FUTURE ISSUE BECAUSE OF IMPROPER REGISTRY MODIFICATIONS.

Before following through Any of the method, You have to Copy the Specific Drivers Hardware Id names from Device Manager's Specific Drivers properties panel.

1. Open the Device Manager.
2. Locate the device
3. Double-click on it, or Right-click and select Properties from the context menu.
4. Switch to the Detailstab.
5. Under the Property menu at the top, select Hardware Ids.
6. For most devices there are more than one Hardware Ids. Usually the first two are the ones you need. The first one is the actual Hardware Id of your device and is specific to your device. For proper prevention, it is recommended to select the second one, which is more generic.
7. Right-click on the ID you want, and select Copy from the context menu to copy it to and save in a notepad txt document, for later use. Its best to copy and save all the ID name from the list.

(FOR EXAMPLE PURPOSE ONLY)

Now let's get going. 

Step 01: Search for Registry Editor and open as Administrator. 

Step 02: Go to this Registry Value either by pasting it on the above address bar or just expand it through the tree view (on left hand side).

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceInstall

The folder "DeviceInstall" under "Windows" folder was not present on my registry tree view. So I had to create the folder. Just right click on "Windows" folder and select "New > Key " and name it as "DeviceInstall"

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

Create the folder "Restrictions **"**as like you did before. Right click on "DeviceInstall" and select New > Key and name it "Restrictions".

Step 03: Left click to select "Restrictions" key and on the right hand side panel, right click and select, New > DWORD (32-bit) Valueand create the following 02 values: 

DenyDeviceIDs 

DenyDeviceIDsRetroactive 

Double-Click on each newly created DWORD values and change the Value Data to 1 ( 1 = Enabled and 0 = Disabled)

Step 04: Now create " DenyDeviceIDs " Folder/Key under " Restrictions " folder as like before by Right click and select New > Key. 

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

Step 05: Left click to select newly created folder/Key  DenyDeviceIDs, on the right hand panel, Right Click and Select New > String Value and Create and name the individual String Values 1, 2, 3 .. depending on how many Hardware ID name you have copied from Device Manager properties panel.  

I have 2 different Hardware Id name/values divided into two separate lines as like this: 

HDAUDIO\FUNC_01&VEN_14F1&DEV_1F72&SUBSYS_10431A40&REV_1000

HDAUDIO\FUNC_01&VEN_14F1&DEV_1F72&SUBSYS_10431A40

these are specific to my machine and device hardware Id. I had to enter these two different Hardware id's on two different String Values

Now double click on each String Value you just created for your device and fill the Value Data with a single line of Hardware Id values Copied from Device Manager.

HDAUDIO\FUNC_01&VEN_14F1&DEV_1F72&SUBSYS_10431A40&REV_1000

HDAUDIO\FUNC_01&VEN_14F1&DEV_1F72&SUBSYS_10431A40

each line goes onto each separate String Value > Value data. 

Repeat this step for every Single Hardware Id name from your Device Manager's Specific Driver Properties panel, the specific driver that you want to prevent automatic update by windows update.

I had to create two (02) String Value for that I had two Hardware ID values/name from my Device Manager Driver Properties.

At this point you are all set. Just Close The Registry Editor and Restart the PC.

If you already haven't uninstalled your Device from windows, now you can and It wouldn't get installed automatically by Windows given that you have followed through the steps properly..  

Rezaul_K:

Thank you for the information.  I tried following the registry method but ran in to a problem in which the generic Windows Audio Driver does not install.  After following the steps you provided and rebooting, I went to device manager and uninstalled the Conexant Audio Driver.  Rebooted again and got an error as the troubleshooter came up.  It says that the speakers are not plugged in.  I then went to device manager, Other Devices, I found a device with an error entitled "Intel High Definition Audio".  I selected "update driver" and it stated that the policy is set to not install devices from Conexant.  What are your throughts?  Additional Information: Windows 10 Pro & I did not set the hardware denial policy nor remove the Conexant Microphone driver.  When uninstalling the Conexant ISST Audio Driver, I selected to delete all driver files.  Any help is appreciated.

When you tried to 'Update driver" from Device Manager, the policy prevented you from installing any driver update from Conexant, Which is exactly what you did with the Registry edit. You explicitly placed a Registry Policy to block any update from Conexant device drivers. 

First of all, If you are on Win 10 Pro, you should have used the Group Policy editor, which is available for only Win 10 Pro and is a little bit easier. But you did it with the Registry Edit so that is fine also. 

Second of all, I think you can try the following steps:

1. Temporarily disable the Registry policies (don't remove them entirely, because later we will need them to be Re-enabled). Just change the values to 0 from 1. That will disable the policies for now.
2. Then Re-install the Conexant drivers. This means just do the update from the Device Manager, which you tried but was being blocked due to the Registry policies which are now disabled. After install reboot your PC. 
3. After reboot go to Device Manager again and open up the Conexant Device Property panel. Go to the tab from within which you Uninstalled the drivers. DONT UNINSTALL THEM AGAIN.
4. You should see a button labeled as Roll Back Driver. (It's an old Screenshot, I have the newer update to this driver since I upgraded to 2004 and 20H2) 

5. After you have selected the Roll Back Driver, you will get asked why do you want to Roll Back, I selected the one that said something like, "My previous driver did work fine".
6. It'll take some time for the Roll Back Process. After that, You will be asked to Reboot. DONT REBOOT NOW.
7. Go to Registry and Re-enable the policies again. **AND NOW YOU CAN REBOOT.**8. After reboot, Now you have successfully uninstalled the Conexant drivers and have placed Registry Policy to prevent any Win Auto Driver Update. 
8. Sit tight and wait for WIn Update to offer the 2004 or 20H2 update. Most probable you will get the 20H2 update as it is the latest major update.

It might take 3-4 days. I got it within 2-3 days. **BE PATIENT.**Let us know when you do get the update.

Cheers and Best of Luck. 👍