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

401 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-02-01T05:38:07+00:00

    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"?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-02-01T02:29:36+00:00

    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.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-01-22T15:21:25+00:00

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-01-22T12:11:44+00:00

    Try Disabling the Conexant driver and block it from installing by using the local group policy editor then Run the media creation tool, and after the update completes unblock the Conexant drivers and install them again..

    This Method worked for me and I didn't face any Issues after updating

    How to " block it from installing by using the local group policy editor " referenser or web adress for information on this.

    Regards Bertil B

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2021-01-21T19:51:47+00:00

    Try Disabling the Conexant driver and block it from installing by using the local group policy editor then Run the media creation tool, and after the update completes unblock the Conexant drivers and install them again..

    This Method worked for me and I didn't face any Issues after updating

    Was this answer helpful?

    0 comments