Updating to Windows 10 Version 2004/Conexant Drivers

Hi,

I already fixed a conflict between realtek audio manager and windows audio manager.  I wen to control panel in the search field I type realtek then the realtek audio manager appeared then I open it then I realized that the audio was disabled I enable it then cortona and audio all starting working. Maybe you can do the same to see in control panel if you can find conexant audio manager like I did with realtek. Take a look at catalog windows to find the right driver that fit with your computer.

Good luck

Hi,

How did you get Microsoft driver after uninstall Conexant drivers?

Did you just uninstall thoose drivers, reboot and windows proposed "microsoft audio drivers" afterth restart?

thanks!

I am repeating my response, because I forgot to quote the question I was responding to.  Sorry!

You have asked the key question. There are a lot of different answers on this thread, many of which will work in some situations, but not for everyone. There’s no need to go searching for these drivers. The appropriate Microsoft driver is already present.

Here’s what I think WILL work for everyone (no guarantees). WHILE DISCONNECTED FROM THE INTERNET, and WITHOUT A HARDWARE ID BLOCK ON AUDIO DRIVER INSTALLATION, uninstall the Conexant Driver. (device manager > Sound, video and game controllers > Conexant SmartAudo HD > right click > uninstall device > check “Delete the driver software for the device”. Click “Uninstall”). Then wait for the prompt to “restart”. WHILE REMAINING DISCONNECTED FROM THE INTERNET, do the restart. The appropriate Microsoft driver should be installed, as you should be able to see in device manager. In my case the driver is called “High Definition Audio Device”, and the “Driver Provider” will be listed as “Microsoft”.

The purpose of being, and staying, disconnected from the internet was to keep the Conexant driver from being automatically reinstalled. BEFORE RECONNECTING TO THE INTERNET, prevent this from happening by applying a block on the hardware id of the device, as described in this link: https://www.tenforums.com/tutorials/122303-enable-disable-installation-removable-devices-windows.html

When the block is in place, you can safely reconnect to the internet.

After I upgraded to 2004, I found that I didn’t have sound, because the hardware block prevents any driver from being reinstalled. I had to temporarily disable the hardware id block. This resulted in the Conexant driver being reinstalled. While the Conexant driver seems to work, it will presumably block future feature updates if the problem is not fixed. I prefer to stay with the Microsoft driver, so I repeated the above procedure.

You have asked the key question. There are a lot of different answers on this thread, many of which will work in some situations, but not for everyone. There’s no need to go searching for these drivers. The appropriate Microsoft driver is already present.

Here’s what I think WILL work for everyone (no guarantees). WHILE DISCONNECTED FROM THE INTERNET, and WITHOUT A HARDWARE ID BLOCK ON AUDIO DRIVER INSTALLATION, uninstall the Conexant Driver. (device manager > Sound, video and game controllers > Conexant SmartAudo HD > right click > uninstall device > check “Delete the driver software for the device”. Click “Uninstall”). Then wait for the prompt to “restart”. WHILE REMAINING DISCONNECTED FROM THE INTERNET, do the restart. The appropriate Microsoft driver should be installed, as you should be able to see in device manager. In my case the driver is called “High Definition Audio Device”, and the “Driver Provider” will be listed as “Microsoft”.

The purpose of being, and staying, disconnected from the internet was to keep the Conexant driver from being automatically reinstalled. BEFORE RECONNECTING TO THE INTERNET, prevent this from happening by applying a block on the hardware id of the device, as described in this link: https://www.tenforums.com/tutorials/122303-enable-disable-installation-removable-devices-windows.html

When the block is in place, you can safely reconnect to the internet.

After I upgraded to 2004, I found that I didn’t have sound, because the hardware block prevents any driver from being reinstalled. I had to temporarily disable the hardware id block. This resulted in the Conexant driver being reinstalled. While the Conexant driver seems to work, it will presumably block future feature updates if the problem is not fixed. I prefer to stay with the Microsoft driver, so I repeated the above procedure.

The Windows update page has been updated. The info section has yesterdays date 20/10/20 against the conexant issues but still has "investigating" so maybe something will happen soon?

I don't think that Microsoft is doing something regarding this Driver issue, at least not by themselves.

I think it's only because they have started to push the October 20H2 Update, which is the next small scale Cumulative update to the previous 2004 version.

And as did I guessed, the version 20H2 update has the same issue regarding Conexant Drivers as version 2004 did. 

If you look carefully on the left-hand side menu you will see the Know Issues regarding version 20H2. The known issues of 20H2 has the same Conexant issue listed. The date is updated only because of the October 20H2 update being available.

btw i just got offered

version 20H2

The next version of Windows is available with new features and security improvements. When you're ready for the update, select "Download and install".

now what is this? lol yet another version!!!

ah

For those running Windows 10 2004, the 20H2 update will be minor and quick to install. That because the 20H2 update is meant to be a small update to 2004, activated with an "Enablement Package," which looks and feels a lot like a Cumulative Update. For anyone running a version older than 2004, the 20H2 update will feel and update like a regular Windows 10 feature update. (This is the same way Microsoft rolled out Windows 10 1909, which was a minor update to 1903.)

As Microsoft has been doing lately with Windows 10 feature updates, it will be throttling the delivery of the 20H2 update, delivering it first to devices where it is likely to have fewer issues. As has been the case recently, Microsoft will likely issue "safeguard holds," designed to prevent the feature update from installing on devices where there are known issues and incompatibilities.

Since Win 10 became available Microsoft has been pushing 2 incremental updates to the OS every year, the significant Feature Update (bigger in size and takes significant time while installing) at around May, followed by a Cumulative Update (not like the previous one in terms of download size and install time) at around October.

But this trend might get disrupted starting from 2021 because Microsoft is set to roll out Win 10X for tablet/handheld devices. So PC users might get only a single Win 10 update instead of two because they have to maintain two different OS builds. This is not official yet, rather speculation.