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 No comments

401 answers

Sort by: Newest
  1. Anonymous
    2021-04-18T09:06:21+00:00

    Yes. In device manager, right click on the conexant driver under sound devices, then click 'uninstall' and choose the option to delete driver files.

    In addition I also went into programme files and deleted the Conexant folder - not certain if that was necessary but wanted rid of all trace. Thanks for the advice, great to have the latest version at last!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-04-18T03:50:07+00:00

    After hearing about more people being successful in updating to the 20H2 level, I tried again. First uninstalled the Conexant audio driver and software and then once again tried to update using Windows Update Assistant already installed on my system. Update took about 1 hour and installed to 20H2 with no problems. It reinstalled the Conexant audio driver back to 8.66.16.50 level as it previously had. I believe that Microsoft finally fixed what got broken when going from 1909 to 2004. The audio driver has never changed. Finally my Lenovo G505s is up to date.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-04-18T02:13:25+00:00

    I'm glad sharing my experience helped someone!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-04-18T02:11:56+00:00

    An update should not take 12+ hours. Full stop. Especially on the system I was updating - only four years old and with a SSD (I would have been more patient if the hardware was older and/or I was using a 'traditional' hard drive)*. I'm glad it finally resolved for you, but stalling out at 61% for an hour or more is not an acceptable update/upgrade experience.

    Also, as I noted in my post ... in Event Viewer, it was logged that the update to 20H2 failed (without any obvious notification provided). So, it is not likely it would have resolved for me regardless of how long I waited. Waiting for an hour at 61% is more than enough time to ascertain something is amiss.

    * I will also note, I have another *10* year old laptop (XPS15) that got updated from 1909 to 2004 and then 20H2 within days of each release. Even the major update from 1909 to 2004 only took a total of 2.5 hours on this antiquated systems, and never did it get 'stuck' at a particular point for more than 15-20 minutes. Can you imagine if an Android or iOS update meant you could not use your device for a 12+ hour block of time? No one would tolerate that.

    The real issue here is though - I did not try to force the update. The update was offered. That implies the upgrade block for the Conexant driver issue was resolved (at least for my system's configuration), and I should expect a smooth upgrade without having to go through the steps I went to to resolve. This is Microsoft bug, and they need to get this sorted out before mainstream support for 1909 ends in less than a month! Clearly, I was not the only one for whom the block was lifted only to find the update failed (without user intervention).

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2021-04-18T02:08:08+00:00

    Unfortunately, unless Microsoft actually resolves the update process - it is going to fail unless you uninstall the driver and its files. I too was trying to avoid doing so, but I will tell you that once 20H2 was up and running, MS then downloads and installs the exact same drivers you had (at least that was my experience, and the experience of others).

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments