What was the WU number? I have the same problem on Lenovo G505s. Haven't received any updates to the Conexant audio driver.
Driver updates don't have a KBID.
Updating to Windows 10 Version 2004/Conexant Drivers
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
401 answers
Sort by: Oldest
-
Sumit 44,226 Reputation points Volunteer Moderator2021-04-15T04:57:11+00:00 -
Anonymous
2021-04-15T05:20:40+00:00 I have received the update as mentioned in this post
-
Anonymous
2021-04-15T05:21:54+00:00 There is no WUID / KBID for Driver Updates... It just shows Conextant SmartAudioHD Driver - 8.xxxxxx ( I don't remember the exact number) - Driver Update
-
Anonymous
2021-04-15T18:16:16+00:00 I'm also stuck at 1909 at the moment. I received an update of the Conexant driver on March 13th which bumped the version to 8.66.95.70 but no update yet.
According to device manager the new UCI64A231.dll is out of the range that Microsoft has blocked, but I noticed that some old dll files (UCI64A134.dll and UCI64A195.dll) are still present in the system32 directory. Is it possible that these old dll files block the update to a new version? If so, would the solution be as simple as to just move these old files to a temperary location?
-
Anonymous
2021-04-15T20:59:30+00:00 I'm also stuck at 1909 at the moment. I received an update of the Conexant driver on March 13th which bumped the version to 8.66.95.70 but no update yet.
According to device manager the new UCI64A231.dll is out of the range that Microsoft has blocked, but I noticed that some old dll files (UCI64A134.dll and UCI64A195.dll) are still present in the system32 directory. Is it possible that these old dll files block the update to a new version? If so, would the solution be as simple as to just move these old files to a temperary location?
I too was stuck on 1909, I must have had a driver update and then later got an offer to upgrade.
Guess what, IT FAILED TO UPDATE!!
I again on restart was offered the same update and once more failed. I thought I'd try to use the windows hi def driver on a third attempt and once more failed. I now think microsoft, are the worst company ever to grace the planet earth.