Windows 10 Feature update (to 2004) Conexant driver Issue

It´s very disapointing to not be able to update our windows because compatibility issues so old.

I hope Microsoft and Synaptics find a solution soon so we could have our systems updated with latest features.

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..

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.

Feels a bit like Windows Phone times. Are we really not getting an intermediate status on how things will continue here? Since May they have been looking for a solution to the problem and now it looks like the October update won't work either. How does it go on here? In the end we are also talking about a loss of value of our hardware.

It's unfortunate indeed. 

I have got some good news. After trying for a few days, I myself have successfully got the 2004 update offer by windows update. Although I had to do some tinkering with my Conexant driver situation. But eventually, I got the update offered through Microsoft windows update. 

I had to uninstall my Conexant audio driver and replace it with a generic Microsoft audio driver (that usually will get install if there is no audio driver present) but Windows will try to install the appropriate OEM driver; in this case the Conexant audio driver through Windows update. For that to prevent I had to place a registry block which did prevent windows to install the Conexant driver.

After that, I had to wait 02 days before Windows update offered me the 2004 update. 

The update install was smooth. Interestingly right after the update windows did install back the Conexant driver that was deemed incompatible for the 2004 version.

How windows could install the Conexant drivers despite having a Registry blocker? Well, version 2004 install reset any change made prior to the install.

Even being incompatible with the 2004 version, the Conexant drivers did not result in any BSOD (Blue Screen of Death), crash, or any issue what so ever. 

But I did uninstall the Conexant driver again, placed the same Registry blocker to prevent further attempts to install the driver again by windows update.

The reason for this is that Microsoft is set to release the next Cumulative Update to 2004 which is called "Version 20H2" this October, and unsurprisingly Conexant drivers are also incompatible with Version 20H2. And I don't want to be blocked from upgrading once again. 

Now for over a week, I'm using version 2004 with Microsoft Audio drivers and the experience is the same as it was with Conexant drivers.

I don't fee any difference with Microsoft drivers in terms of sound quality. Plus it's an added benefit that I won't be blocked when the next release becomes available.

Feels a bit like Windows Phone times. Are we really not getting an intermediate status on how things will continue here? Since May they have been looking for a solution to the problem and now it looks like the October update won't work either. How does it go on here? In the end we are also talking about a loss of value of our hardware.