This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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)
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 ?
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.
I still feel that you can uninstall the drivers and manually install the 20H2 without a restart. The drivers get automatically gets installed at the end and the sound works perfectly. If it doesn't you can install/ update the drivers through windows update again or through trouble shooting.
I don't think Microsoft Will do anything more.
Same with Asus GL752VW
Further to this - fortunately I have a later HP Envy without Conexant hardware. I installed a clean near-out-of-box image of that on that, upgraded it to 20H2, then imaged its system drive, then restored that on each of the two older HP Envy PCs with Conexant hardware. Oddly, the display on each went a bit nuts as to font sizes until I disabled the two Conexant drivers in msconfig in each PC, and so far each is behaving perfectly, just in time for me to miss the expiration of Microsoft's servicing of 1909 in May.
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.
Yes, exactly my thoughts when I mentioned the update I received. Now we just have to wait until the compatibility job recognized the new driver. If I remember correctly this could take up to 3 days. I'll just wait now until I see the upgrade available in windows update. After waiting so long, a few days more is not a problem at all, having the advantage of using the usual way of the upgrade.
I receive the latest driver update at least one week ago and I've been checking for an available update regularly.
I suspect they are waiting for enough computers to have their drivers updated before pushing the 2004/20H2 update.
Well, like you said, waiting a few more days now is not a problem, also if you're not waiting for a specific feature there is no particular reason to be in a hurry IMHO, my windows 1909 is running just fine (although I'd like the WSL2 and docker ... I'm just doing fine without now).
I'm pretty sure MS is planning to have everyone updated before 1909 end of support, that's what matters most for me.
Actually you can officially use WSL2 on 1909, I discovered it months ago. It was the only feature I was waiting with 2004 but when I discovered it I forgot about 2004
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.
Yes, exactly my thoughts when I mentioned the update I received. Now we just have to wait until the compatibility job recognized the new driver. If I remember correctly this could take up to 3 days. I'll just wait now until I see the upgrade available in windows update. After waiting so long, a few days more is not a problem at all, having the advantage of using the usual way of the upgrade.
