Updating to Windows 10 Version 2004/Conexant Drivers

Anonymous
2020-06-12T18:05:40+00:00

So what do people with computers with Conexant drivers do? Windows Update says update drivers but there are none acceptable, it also says Microsoft is working on a fix ? So what do we do? If there are compatible drivers for devices using Conexant Audio where are they, how do we get them and install or replace them (I have tried everything to no avail). When does MS expect a fix ? Are persons with Conexant audio drivers computers at end of life ? Does anybody care ?

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

401 answers

Sort by: Newest
  1. Anonymous
    2021-01-04T13:41:04+00:00

    I have an HP Envy Desktop (new October 2018).

    The Conexant driver main number is 8.65.282.54, and this is also the version of chdrt64.sys. 8.65.282.54 is NOT one of the 8.65 affected versions, NOR is it in the 8.66.0.0 to 8.66.89.0 affected range.

    In other words, it is apparently OK.

    HOWEVER, the ISST Audio Driver file is uci64a189.dll i.e. in the AFFECTED range uci64a96 to uci64a232. Furthermore, the .dll file version is 7.189.0.0, which is  a lower version than 7.231.3.0, and thus also NO GOOD.

    It seems therefore that BOTH these have to be OK, for the update to be offered.

    Another mess, coming on top of last summer's KMODE BSOD lockouts.

    As usual, there is no evidence that HP have taken this seriously and tried to do anything about it, in the same way as KMODE.

    Yeah, having either one of the incompatibilities will result in the update being blocked. I had both of the incompatibilities before I upgraded to 2004. 

    I didn't have to face the KMODE BSOD issue. Fortunately, I didn't face any issues of any kind after upgrading to 2004. Maybe because I removed every last bit of Conexant driver traces from my system before placing the Registry Block and then upgrading to 2004. 

    HP is not the only one to do nothing, my device manufacturer ASUS also didn't provide any driver update for this issue. Even after all this time, I don't have any driver update from ASUS (I got a driver update from Microsoft only after upgrading to 2004). At some point, I contacted ASUS customer service directly. They have got some incompetent imbecile as Customer Service Reps. (Indian region) that didn't even understand what I was talking about! They emailed me a solution thinking I was asking about how to obtain drivers for my device. A joke of a Customer Service.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-01-03T13:49:34+00:00

    I successfully updated it yesterday after first updating the driver. The condition wasn't removed from windows update and I didn't want to wait for two days to get the update. I haven't had any problems. The driver was from HP and my laptop is HP 450 G5.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-01-03T11:38:39+00:00

    I have an HP Envy Desktop (new October 2018).

    The Conexant driver main number is 8.65.282.54, and this is also the version of chdrt64.sys. 8.65.282.54 is NOT one of the 8.65 affected versions, NOR is it in the 8.66.0.0 to 8.66.89.0 affected range.

    In other words, it is apparently OK.

    HOWEVER, the ISST Audio Driver file is uci64a189.dll i.e. in the AFFECTED range uci64a96 to uci64a232. Furthermore, the .dll file version is 7.189.0.0, which is  a lower version than 7.231.3.0, and thus also NO GOOD.

    It seems therefore that BOTH these have to be OK, for the update to be offered.

    Another mess, coming on top of last summer's KMODE BSOD lockouts.

    As usual, there is no evidence that HP have taken this seriously and tried to do anything about it, in the same way as KMODE.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-01-03T07:18:07+00:00

    I have the driver version 9.0.278.120 as I just updated today. I am not sure whether I should force update Windows 2H20 Update or not. I cannot find this version mentioned in the issue but despite this update, I haven't got the option to update windows version. Still reads we are preparing for your system blah blah. 

    And my driver is also on Microsoft Catalog update which I don't really know means anything or not. 

    Would appreciate help. 

    Microsoft explicitly listed the Conexant drivers that are incompatible with the 2004/20H2 version:

    "Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant or Synaptics audio devices and Windows 10, version 2004 (the Windows 10 May 2020 Update). 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. The affected driver will be named Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and haveversions 8.65.47.53, 8.65.56.51, or 8.66.0.0 through 8.66.89.00 for chdrt64.sys or chdrt32.sys."

    Simply, if your Conexant driver version is Older (read Lower) than 8.66.89.00, then your's is not compatible. 

    Your driver version seems newer than what they have listed as incompatible, yet you have got the same old "Update Blocked" message. 

    What is your laptop manufacturer? HP? 

    If so you can take a look at this HP forum post: https://h30434.www3.hp.com/t5/Notebook-Operating-System-and-Recovery/Cannot-update-to-windows-10-feature-update-2004/td-p/7839414

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-01-02T19:14:05+00:00

    I have the driver version 9.0.278.120 as I just updated today. I am not sure whether I should force update Windows 2H20 Update or not. I cannot find this version mentioned in the issue but despite this update, I haven't got the option to update windows version. Still reads we are preparing for your system blah blah. 

    And my driver is also on Microsoft Catalog update which I don't really know means anything or not. 

    Would appreciate help.

    Was this answer helpful?

    0 comments No comments