Updating to Windows 10 Version 2004/Conexant Drivers

I received a "Conexant - MEDIA - 8.66.95.70" driver update today via Windows Update. Maybe it will release the lock after the new state was detected by the compatibility assistant job.

I wonder if you could please say, from Device Manager, what the version of the UCIA64???.dll file is? The ??? will be a number, hopefully great than 231.

I'm asking this because my Conexant driver version is 8.65 etc, which is NOT in the affected range for that problem, whereas my ISST problem driver is 7.189.0.0, which is a much lower version than 7.231.3.0 for the UCI*.dll and IS affected. In other words, is the version of your UCI*.dll file NOW greater than 7.231.3.0?

In case you haven't seen it, the details of the Conexant drivers and problems are on the MS Updates list here:-

https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-2004#417msgdesc

Although I am on 20H2, it would certainly be useful for me to know this, to check whether I also receive a new Conexant driver version. This would, I suppose, be an answer to potential future problems in Feature releases.

Thanks.

Peter

Hi,

I have an ASUS UX310UQK, I've been stuck on 1909 for some time too.

I noticed my driver was updated to 8.66.95.70 (chdrt64.sys has version 8.66.95.0) some time ago, though I don't how when

However, last week I just tried a windows update on UCI64A231 and got version 7.231.4.0, which is above update requirements (231.3)

Theoretically, I should be able to upgrade to 2004 or 20H2, I've been checking daily but it's not been proposed to me yet, but there is definitely something in the work.

I received a "Conexant - MEDIA - 8.66.95.70" driver update today via Windows Update. Maybe it will release the lock after the new state was detected by the compatibility assistant job.

I wonder if you could please say, from Device Manager, what the version of the UCIA64???.dll file is? The ??? will be a number, hopefully great than 231.

I'm asking this because my Conexant driver version is 8.65 etc, which is NOT in the affected range for that problem, whereas my ISST problem driver is 7.189.0.0, which is a much lower version than 7.231.3.0 for the UCI*.dll and IS affected. In other words, is the version of your UCI*.dll file NOW greater than 7.231.3.0?

In case you haven't seen it, the details of the Conexant drivers and problems are on the MS Updates list here:-

https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-2004#417msgdesc

Although I am on 20H2, it would certainly be useful for me to know this, to check whether I also receive a new Conexant driver version. This would, I suppose, be an answer to potential future problems in Feature releases.

Thanks.

Peter

I received the same Update and applied it this morning. This is the result:

However the Microsoft's web site says " uci64a231.dll and a file version of 7.231.3.0 or lower" and stupidly 7.231.4 is strictly greater then the specified version so there is a litthe hope

I received a "Conexant - MEDIA - 8.66.95.70" driver update today via Windows Update. Maybe it will release the lock after the new state was detected by the compatibility assistant job.

I wonder if you could please say, from Device Manager, what the version of the UCIA64???.dll file is? The ??? will be a number, hopefully great than 231.

I'm asking this because my Conexant driver version is 8.65 etc, which is NOT in the affected range for that problem, whereas my ISST problem driver is 7.189.0.0, which is a much lower version than 7.231.3.0 for the UCI*.dll and IS affected. In other words, is the version of your UCI*.dll file NOW greater than 7.231.3.0?

In case you haven't seen it, the details of the Conexant drivers and problems are on the MS Updates list here:-

https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-2004#417msgdesc

Although I am on 20H2, it would certainly be useful for me to know this, to check whether I also receive a new Conexant driver version. This would, I suppose, be an answer to potential future problems in Feature releases.

Thanks.

Peter

I received the same Update and applied it this morning. This is the result:

However the Microsoft's web site says " uci64a231.dll and a file version of 7.231.3.0 or lower" and stupidly 7.231.4 is strictly greater then the specified version so there is a litthe hope

Thanks, and also to @Arkhee for the updates. 7.231.4.0 looks like a step in the right direction, and, all being well, the 20H2 updates should be coming through.

Hi, 

If the driver is above the recommended version, I think it would be okay to try updating manually if you want.