Updating to Windows 10 Version 2004/Conexant Drivers

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.

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. 

Did you get the update from "Windows Update" after you updated the driver, or did you force update (installed) with the Microsoft Update tool (downloading an ISO and making a bootable drive) after updating the drivers?

Also if you have updated successfully then shouldn't the Windows update block message be automatically gone by now? Or I'm misreading you?

Hi

Rezaul_K,

I wen't with MS high def driver and blocked with group policy editor 3 days ago. The block message on windows update page has been removed but I have not got a notification for the 2004 update yet. How long did it take for you to receive an update notice from windows?

Thanks in advance

Hi, 

Bigestnumpty

As you no longer see the Windows 10 Update Block Message, means you are on the right track. It took me about 3-4 days before I got the update offered. You might have to wait a bit longer, there's not really any time frame here. 

I would say for you to be Patient. You have waited this long, a few more days won't do any harm. unless you are experiencing any audio issues due to the Microsoft basic drivers. 

Just wait and manually check for updates by going to the Windows Update section. Most probably you will get the 20H2 update, not the 2004 one as 20H2 is the latest one.

Let us know when you do get the update offered. 

Cheers and Best of luck. 👍

Hi again

Rezaul_K,

Well I had waited over a week and still no sign of an update from MS. I took matters into my own hands and attempted another forced update with a 20H2 image, this was followed with a BSOD and a return to my existing windows build (1909).

Obviously there is something more than a driver issue causing this update to fail, as I had blocked the Connexant driver from reinstal via group policy restrictions and had the MS High Def driver in use.

I now intend to remove the Group Policy  driver block, reinstall the Connexant driver and await Windows for my update.

I'm sick of waiting but have now tried so many ways and times to get the update that there is no further option available to me!

Doing my twice-daily check on the MS website regarding these, I see that both the Conexant "issues" were updated 5th January 2021, and now have a status of "Confirmed"; which I think was previously "Investigating".

I do not speak Microsoft gobbledegook, and would be grateful if anyone "in the know" can explain the significance of "Confirmed"; especially as it has taken them more than 6 months to achieve this status, whatever it may mean.

Thanks,

Peter