Updating to Windows 10 Version 2004/Conexant Drivers

I have an ASUS X510UQ (circa 2017) and wanted to share what finally worked for me. I installed the generic MS HD drivers instead of Conexant as recommended, which stayed in place for at least a week without any blocking. I wasn't offered the update to 2004, though, until I actually pulled two .dll files in the offending range (uci64a96.dll through uci64a231.dll -- for me, it was UCI64A134.dll & UCI64A231.dll) out of the System32 folder. The update appeared within 24 hours and installed no problem. Conexant drivers were reinstalled automatically after install.

I do now have an issue, however, where if I manually check for updates, I receive the error "A current driver on your PC may be better than the driver we're trying to install. We'll keep trying to install." regarding some Intel driver.

What is the Intel driver that you are trying to update? 

How are you "Manually" checking update to the said intel drivers; through "Optional Windows Update" or from within "Device manager"?

What is the Intel driver that you are trying to update? 

How are you "Manually" checking update to the said intel drivers; through "Optional Windows Update" or from within "Device manager"? 

Following my upgrade to 2004, whenever I ran "Check for Updates" from Windows Update (in Settings), it would attempt to install Intel display driver 26.20.100.7325 and I would receive the "Your current driver is better" error; no additional updates could be retrieved.

I was able to find more info and a fix (RememberFlight19's answer) here, however, in case anyone has the same issue following their update to 2004:

Intel Display Driver 26.20.100.7325 Update Error

What is the Intel driver that you are trying to update? 

How are you "Manually" checking update to the said intel drivers; through "Optional Windows Update" or from within "Device manager"? 

Following my upgrade to 2004, whenever I ran "Check for Updates" from Windows Update (in Settings), it would attempt to install Intel display driver 26.20.100.7325 and I would receive the "Your current driver is better" error; no additional updates could be retrieved.

I was able to find more info and a fix (RememberFlight19's answer) here, however, in case anyone has the same issue following their update to 2004:

Intel Display Driver 26.20.100.7325 Update Error

As per your previous reply, I take it that you are on version 2004. I would suggest you first upgrade to the 20H2 version, which is the latest Windows build, and then try updating the Intel Display drivers and see if it does solve the issue.

Also, I would suggest you use the "Intel Driver & Support Assistant" Tool to try to update the said drivers. It's an Intel supplied software that will search for the best drivers update for your specific pc/laptop.

Download the Intel® Driver & Support Assistant.

I have an ASUS X510UQ (circa 2017) and wanted to share what finally worked for me. I installed the generic MS HD drivers instead of Conexant as recommended, which stayed in place for at least a week without any blocking. I wasn't offered the update to 2004, though, until I actually pulled two .dll files in the offending range (uci64a96.dll through uci64a231.dll -- for me, it was UCI64A134.dll & UCI64A231.dll) out of the System32 folder. The update appeared within 24 hours and installed no problem. Conexant drivers were reinstalled automatically after install.

I do now have an issue, however, where if I manually check for updates, I receive the error "A current driver on your PC may be better than the driver we're trying to install. We'll keep trying to install." regarding some Intel driver.

What is the Intel driver that you are trying to update? 

How are you "Manually" checking update to the said intel drivers; through "Optional Windows Update" or from within "Device manager"? 

@Rezaul_K

That's a very helpful update. I have a couple of questions.

First, when you say you "pulled" the .dll files in System32, did you rename them, delete them or move them somewhere else?

Second, when you updated and the Conexant drivers were reinstalled, were the .dll files reinstated in the Sys32 folder?

I'm guessing that you updated straight to 20H2, and that MS only offer the very latest version through WU. I suppose that if the update is firstly from 1909 to 2004 , with measures as described to overcome the driver problem and enable the update, but then there is an update to 20H2, the same procedures would need to be gone through again. This concerns me, as until there is a satisfactory resolution by way of compatible drivers being supplied from MS so that these steps are not necessary and a straight WU update can be done, this appears to remain a permanent problem in future updates beyond 20H2, for anybody running a machine with this Conexant audio/driver configuration. In other words, an empirical workaround will have to be found and used every time.

I have an ASUS X510UQ (circa 2017) and wanted to share what finally worked for me. I installed the generic MS HD drivers instead of Conexant as recommended, which stayed in place for at least a week without any blocking. I wasn't offered the update to 2004, though, until I actually pulled two .dll files in the offending range (uci64a96.dll through uci64a231.dll -- for me, it was UCI64A134.dll & UCI64A231.dll) out of the System32 folder. The update appeared within 24 hours and installed no problem. Conexant drivers were reinstalled automatically after install.

I do now have an issue, however, where if I manually check for updates, I receive the error "A current driver on your PC may be better than the driver we're trying to install. We'll keep trying to install." regarding some Intel driver.

What is the Intel driver that you are trying to update? 

How are you "Manually" checking update to the said intel drivers; through "Optional Windows Update" or from within "Device manager"? 

@Rezaul_K

That's a very helpful update. I have a couple of questions.

First, when you say you "pulled" the .dll files in System32, did you rename them, delete them or move them somewhere else?

Second, when you updated and the Conexant drivers were reinstalled, were the .dll files reinstated in the Sys32 folder?

I'm guessing that you updated straight to 20H2, and that MS only offer the very latest version through WU. I suppose that if the update is firstly from 1909 to 2004 , with measures as described to overcome the driver problem and enable the update, but then there is an update to 20H2, the same procedures would need to be gone through again. This concerns me, as until there is a satisfactory resolution by way of compatible drivers being supplied from MS so that these steps are not necessary and a straight WU update can be done, this appears to remain a permanent problem in future updates beyond 20H2, for anybody running a machine with this Conexant audio/driver configuration. In other words, an empirical workaround will have to be found and used every time.

As you all know I've tried everything to get the update! I've gone back to the latest Conexant drivers version 8.66.95.70 provided by Microsoft and still have this in use.

I had waited almost 2 weeks using the MS high Defination driver and no offer of an update. I still have no offer! I have in the past tried to force an update after blocking device updates, using both drivers and always, failing to complete the update.

I have checked my windows system and found several of the offending .dll files, (see screenshot below). Should I delete these files and hope for an update or delete them and force an update or yet again delete them, go back to MS high def drivers and hope for the best?

Looking for advice.