Windows 10 2004/20H2 Not Being Offered Due to Conexant HD Audio Issue

Topic

New Reply

Since July (or perhaps even earlier), Windows update has been warning/teasing me that the May Update is on the way, and will be downloaded when it’s ready for my system.

Well … I suspect the reason I have yet to be offered the update is some combination of these blocks:

https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004#377msgdesc

https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004#417msgdesc

Both these blocks show up in the notes for both 2004 and 20H2. Looking at threads such as this > https://answers.microsoft.com/en-us/windows/forum/all/updating-to-windows-10-version-2004conexant/c98ac1c5-0ddb-4964-b50d-9b3720ac7122 … it’s pretty clear I am not alone, but there is no word on a resolution.

As I use the more advanced audio features the Dell has provided (INS 7353), I would rather not hack the block by installing generic drivers etc., but I am getting concerned I could run into a situation where my system will not be upgraded, ever … which does carry security and EOL issues. I have considered trying to force the update via the online update tool/media creation tool … but also not necessarily looking to tempt fate with a BSOD.

Does anyone here have insights as to why this block has not been resolved since May? Any thoughts on how one might proceed?

In device manager, the device is listed as ‘Conexant SmartAudio HD.’ Via device manager, Windows says I have the best drivers for my system installed. No new audio drivers are available from Dell, and talking with their support folks was sadly/predictable, not productive.

Thanks for any insights/suggestions!

Reply | Quote

Replies

It still says to hang tight as the vendor is coming up with a fix.  Let me ask around.

Susan Bradley Patch Lady

2 users thanked author for this post.

johnf, howardagoldberg

Reply | Quote

[howardagoldberg]

Susan … thank you! I have a Dell XPS system from 2011 that is fully updated, so after almost seven months, I am beginning to get a bit impatient and considering forcing the upgrade. But, if a proper fix is actually in the works, I will exert some additional patience :-).

The system in question with the Conexant driver is a Dell Inspiron 7353 2-in-1. I’m on 1909.

 

• This reply was modified 2 years, 7 months ago by howardagoldberg.

Reply | Quote

Howard’s 2nd link (MS Block announcement) shows [The affected driver will be named Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have versions 8.65.47.53, 8.65.56.51, or 8.66.0.0 through 8.66.89.00 for chdrt64.sys or chdrt32.sys.]……

My Ver does Not match their Numbering Scheme in that I have 3 #s in the 3rd group (ie) 8.65.282.54 Vs their 2 #s 8.65.47.53. Wondering if the MS “block” app is loosely blocking Any HD Audio Ver – Since my actual Ver # is NOT Named it’s either something else blocking us, the Announcement Left Out one # space in Affected Ver’s, or their Block App is blocking ALL Conexant Ver’s contrary to the Announcement data.

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / HP Envy Desk-Ethernet - SSD-HDD/ i5(8th Gen) 12GB / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU=0

Reply | Quote

HP all in one 64 bit touch screen 2020/12/2 still no sound

Reply | Quote

I have a Spectre laptop of 2017 and cant update. Connexant, Synaptics and laptop makers are unacceptable for not supporting their products… but Microsoft caused this issue. They are working on a fix from May and it is December. Seriously.. if you cant fix it maybe find another job at McDonalds and leave your positions to other more skillful programmers that MS could hire.

Reply | Quote

Current advice is not to upgrade to 2004 or 20H2.

Carpe Diem {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1778 x64 i5-9400 RAM16GB HDD Firefox115.0b2 MicrosoftDefender

1 user thanked author for this post.

RockE

Reply | Quote

Version control has been a driver problem for years, Windows 10 is now highlighting the issue. SNAFU :)/

Reply | Quote

No, this is SUSFU (Situation Unchanged, Still…).

Zig

Reply | Quote

I have a Dell 7359 with same issue. Now 2H20 is also blocked. I have the latest Conexant driver from dell, 8.65.135.0 which would seem to be outside the blocked range, but MS is blocking.

Reply | Quote

[Alex5723]

anonymous wrote:

I have a Spectre laptop of 2017 and cant update. Connexant, Synaptics and laptop makers are unacceptable for not supporting their products… but Microsoft caused this issue. They are working on a fix from May and it is December. Seriously.. if you cant fix it maybe find another job at McDonalds and leave your positions to other more skillful programmers that MS could hire.

If you insist on updating to 2004/20H2 Microsoft has a workaround by unblocking any blocks.

Microsoft hasn’t caused the incompatibly issues. The hardware OEMs has enough beta testing time to test and update drivers. They didn’t because they don’t want to invest time and money.

• This reply was modified 2 years, 5 months ago by Alex5723.

Reply | Quote

What?  Microsoft hasn’t caused the incompatibly issues?  Well, what changed?  The drivers certainly did not.  So some gremlin inside Microsoft’s Windows development made a subtle change to some software interface because it would not affect anyone and it makes Windows “better” in some arcane and abstract way.  That is the first and most benign possibility.

The second possibility is that the change was intentional, the idea being to render obsolete yet another set of perfectly good hardware so Microsoft OEM’s and ODM’s can sell you another, adding to the piles of decent hardware making it way, best case, to an e-cycler.

These sorts of devices rendered “obsolete” by changes to Windows have gone on for many, many years.

By contrast, Linux driver interfaces and APIs are more stable and unchanging, though not without devices becoming inoperative when confronted with a new distro.

Reply | Quote

[Alex5723]

Alex5723 wrote:

anonymous wrote:

I have a Spectre laptop of 2017 and cant update. Connexant, Synaptics and laptop makers are unacceptable for not supporting their products… but Microsoft caused this issue. They are working on a fix from May and it is December. Seriously.. if you cant fix it maybe find another job at McDonalds and leave your positions to other more skillful programmers that MS could hire.

If you insist on updating to 2004/20H2 Microsoft has a workaround by unblocking any blocks.

Microsoft hasn’t caused the incompatibly issues. The hardware OEMs has enough beta testing time to test and update drivers. They didn’t because they don’t want to invest time and money.

• This reply was modified 2 years, 5 months ago by Alex5723.

Respectfully, I disagree that Microsoft is ‘innocent’ in this issue.

My Conexant drivers from Dell are dated March 2019. Not brand-spanking new, but these are not ancient drivers from 10 years ago. I have had my Inspirion notebook for about four years, and never encountered a block before – much less for something as common as a sound driver from a mainstream provider used on 100s of thousands (if not more) systems.

I have tracked down that the issue on my system is not the entire driver package, but one .dll with a revision number in the range listed for the ISST audio issues block; which is fascinating, since I don’t have ISST, I have ‘Conexant SmartAudio HD,’ which is not even stated specifically as one of the plain-English ‘IDs’ being blocked.

Based on my hardware ID for this card, these are the drivers MS has to push out to my system (beyond Dell’s driver page for my system):

https://www.catalog.update.microsoft.com/Search.aspx?q=HDAUDIO%5CFUNC_01%26VEN_14F1%26DEV_50F2%26SUBSYS_102806FE

If you look, you can see drivers were updated in 2016, and then three years later in 2019. That’s not so long ago, and there is really no excuse why MS would have changed something to muck with drivers that are less than 2 years old – or at the very least, to fix the installer so the block can be removed.

Believe me, Dell has to answer for this also as the direct vendor – but most of the blame lays at MS’s door.

Reply | Quote

[EP]

“Believe me, Dell has to answer for this also as the direct vendor – but most of the blame lays at MS’s door.”

you should bring this to Dell’s attention and post the Conexant audio driver compatibility problems with 2004/20H2 in the Dell community support forums, howardagoldberg

but I also agree – Microsoft is taking so long with the 2004/20H2 upgrade block with the outdated Conexant drivers and has not lifted the restrictions for that.

guess that’s why I run Win10 LTSC 2019 instead of the normal Win10 OS on my family’s Dell Inspiron 620 desktop PC which does use Conexant CX20641 audio hardware (the driver version I have there is 8.50.14.50 which is several years old)

edit – btw, I found this topic in the Dell forums

• This reply was modified 2 years, 5 months ago by EP.
• This reply was modified 2 years, 5 months ago by EP.

Reply | Quote

[EP]

EP wrote:

“Believe me, Dell has to answer for this also as the direct vendor – but most of the blame lays at MS’s door.”

you should bring this to Dell’s attention and post the Conexant audio driver compatibility problems with 2004/20H2 in the Dell community support forums, howardagoldberg

but I also agree – Microsoft is taking so long with the 2004/20H2 upgrade block with the outdated Conexant drivers and has not lifted the restrictions for that.

guess that’s why I run Win10 LTSC 2019 instead of the normal Win10 OS on my family’s Dell Inspiron 620 desktop PC which does use Conexant CX20641 audio hardware (the driver version I have there is 8.50.14.50 which is several years old)

edit – btw, I found this topic in the Dell forums

• This reply was modified 2 years, 5 months ago by EP.
• This reply was modified 2 years, 5 months ago by EP.

I have reported this to Dell on several occasions. I actually got through directly at one point to the driver engineering team. Their response was basically, ‘it says on the MS 2004/20H2 status page that MS is working on a resolution, so it’s not our problem.’

My guess is, an updated driver may show up on the drivers page for mine (and other) systems at some point … as new BIOS, WiFi, etc. updates are still posted. But I am not holding my breath, or wasting any more time trying to convince them they need to act on this, lol.

Reply | Quote

howardagoldberg wrote:

Respectfully, I disagree that Microsoft is ‘innocent’ in this issue.

Microsoft can change what ever they want when they want. Microsoft is not obliged to any hardware OEM, software devs, who have ample of time testing their hardware/software running previews/insider/beta.. versions of Windows.

Conexant should have found out months ago that there are compatibility issues with 2004/20H2.

Dell isn’t responsible for Conexant drivers or any other driver.
Dell just assemble of-the-shelf parts into a PC.

Reply | Quote

Alex5723 wrote:

howardagoldberg wrote:

Respectfully, I disagree that Microsoft is ‘innocent’ in this issue.

Microsoft can change what ever they want when they want. Microsoft is not obliged to any hardware OEM, software devs, who have ample of time testing their hardware/software running previews/insider/beta.. versions of Windows.

Conexant should have found out months ago that there are compatibility issues with 2004/20H2.

Dell isn’t responsible for Conexant drivers or any other driver.
Dell just assemble of-the-shelf parts into a PC.

Um, no.

First, MS markets ‘Windows as a service’ and touts the fact that updates will be provided for the life of your system (assuming it was W10 compatible from the get-go).

Second, while Conexant provided drivers to Dell … Dell (and I presume other vendors) customize the drivers to work with such enhancements as ‘Wave Audio,’ etc. So, Dell *is* absolutely responsible here: Conexant does not provide me with the drivers, Dell does. As stated, Dell most certainly customizes the drivers they license from Conexant, et. al., I cannot download generic Conexant drivers (now owned by Synaptic, btw), so they are going to come from Dell or Microsoft.

While MS *can* do whatever they want (since they technically own the OS, users are licensed to use it), it is damaging to the ecosystem when OS updates don’t play well with relatively new drivers. As stated above, at least in my case, the drivers in question are dated 03/15/2019. So, we’re not talking about drivers from 7+ years ago. These were released to work with 1903/1909, in fact.

Third, while hardware vendors/driver engineers, etc. may have access to dev builds … they are not going to test every previous version of a driver, especially if it worked with previous Windows builds and MS did not provide guidance as to what they changed that might cause such a widespread, if not esoteric, issue.

Bottom line – this is impacting systems that are relatively young (I’ve seen some folks with systems less than 2 years old who have been hit with this) and MS has had 8 months now to rectify this – especially since this seems to be an issue during the upgrade, not with the drivers actually behaving well if you can get 2004/20H2 installed through some hackery. They hold significant responsibility in not letting all these systems become security risks to themselves when 1909 goes out of support in the near future – most folks are not going to know how or bother with workarounds to getting 2004/20H2 and beyond installed.

Reply | Quote

[EP]

don’t know why Microsoft recently wrote this:

https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-20h2#377msgdesc

Resolution: This issue was resolved for safeguard IDs 25702662 and 25702673. The safeguard hold has been removed for these safeguard IDs as of December 11, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 or Windows 10, version 20H2 is offered.

the issue is not fully resolved despite what MS has recently posted

edit – some users mentioned here just did a manual 20H2 update and decided to remove existing Conexant audio drivers and just use the generic MS audio drivers before updating to 20H2 as some people don’t see any advantages of using Conexant drivers.

• This reply was modified 2 years, 5 months ago by EP.

Reply | Quote

I have a Lenovo 310 Ideapad running Windows 10 version 1909.
Some have reported replacing the Conexant audio driver with the Microsoft
HD audio driver and then waiting several days for the regular Windows Update
process to install version 2004. Does this actually solve the problem?
For example, when I start to install the Microsoft HD audio driver, it
gives a warning that the driver may not be compatible. Elsewhere I’ve
read that the chip set for the Conexant implementation could be the
problem when going to the Microsoft HD audio driver. Any advice from
other Lenovo users would be most welcome.

Reply | Quote

Have you tried this advice from the link EP posted?

UNINSTALLING (not “deleting”) the Conexant HD Audio Driver in Device Manager and then running the Windows 2004 update

cheers, Paul

Reply | Quote

I am really looking for Lenovo users with Conexant audio drivers who have been successful at updating from 1909 to 2004.  I don’t want to experiment if I can help it.

Reply | Quote

I’m afraid you don’t have much of a choice but to experiment as Paul T mentioned, mr anonymous
Lenovo is no longer providing any new drivers for your ideapad 310 model (because it’s more than 3 years old) so you will have to currently uninstall/remove your existing Conexant audio driver from the Add/Remove programs control panel before trying to update from 1909 to 2004/20H2 and then re-installing the Conexant driver after completing the feature update.

Reply | Quote

Where do you get the driver after updating to 2004? Lenovo does not offer it.

Reply | Quote

Windows will install it, either on its own or from update in Device Manager – right click the device with a yellow exclamation mark.

cheers, Paul

1 user thanked author for this post.

Ken

Reply | Quote

Nothing has exclamation mark, but one is version 8.66.76.61 which is within the range mentioned. Should I just “update the driver” and see what the new version is?

Reply | Quote

Pre-update to V2004 you uninstall the driver and then run the upgrade – do not reboot before the upgrade.

Post-upgrade, if the audio isn’t working, update the driver. If it is working, do nothing, except backup.

cheers, Paul

Reply | Quote

OK. 2004 has not been offered yet.

Reply | Quote

If you want to move to 2004 you will need to do it manually.
If so, start a new thread and we’ll walk you through the process.

cheers, Paul

1 user thanked author for this post.

Ken

Reply | Quote

Thanks, I’ll wait until it’s offered.

Reply | Quote

I removed Conexant drivers yesterday, though was not able to delete Conexant folder  completely as ¨some files in use by another program¨. Device manager does not show any Conexant drivers.

wumgr detected 2004 feature now available, but it has not yet appeared in WU. Can I install it from wumgr or should I wait until it appears in WU?

Reply | Quote

Ken wrote:

Can I install it from wumgr or should I wait until it appears in WU?

You may install from WuMgr. I often do so.

Carpe Diem {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1778 x64 i5-9400 RAM16GB HDD Firefox115.0b2 MicrosoftDefender

1 user thanked author for this post.

Ken

Reply | Quote

I tried twice, this is what the log shows at the bottom of wimgr:

“Found 1 pending updates

Error: No Download url’s found for update Feature update to Windows 10, version 2004

Downloaded 0 out of 0 to…..( etc)

Updates (Un)installed successfully”

I guess I have to wait for WU to show it.

 

Reply | Quote

My WuMgr doesn’t seem to have those message options. Can you post a screenshot?

cheers, Paul

Reply | Quote

Here are three screen shots so you can see the whole log notes at the bottom.

wumgr3 shows 204 update available.

wumgr1 shows window after trying to install, with first part of log notes at bottom.

wumgr2 show the rest of the log notes at bottom.

WU has not yet received the 2004 update.

Reply | Quote

now 2004 showed up in WU. Will update from there.

Reply | Quote

Installed 2004 without any problems.  ow I see following updates pending:

4023057 (I had installed this in version 1909. Susan’s latest spreadsheet does not show this KB)

4598242 (Susan’s latest spreadsheet says defer)

Reply | Quote

Ken wrote:

4598242 (Susan’s latest spreadsheet says defer)

Latest (January 31 links) says install.

Windows 11 Pro version 22H2 build 22621.1778 + Microsoft 365 + Edge

1 user thanked author for this post.

Ken

Reply | Quote

But no mention of 4023057?

 

Reply | Quote

I installed KB4023057 with no ill effects.

1 user thanked author for this post.

Ken

Reply | Quote

[Bob99]

KB4023057 is simply MS’s attempt to restore your update settings to what MS thinks they should be in order to get you to update to the latest version of Windows 10. In this case, the latest version is 20H2, not 2004, so MS really wants you to get 20H2 installed, and they’re willing to change your update settings to ensure you get it.

That’s why you’re being offered the update. When I was on 2004 back in mid-January, I was offered that update, which I promptly hid because I was going to 20H2 in a short time anyway. Although @Alex5723 installed it with no ill effects as he says, you can feel free to use wumgr to hide the update if you wish.

If you do install the patch (or have already installed the patch), be sure to check ALL of your update settings in gpedit to make sure they haven’t been tampered with. If they have, simply return them to your preferred settings. If you have the Home edition of Windows 10, you’ll have to check your registry settings (described in AKB2000016) to see if they’ve been modified from what you had them set to. As above: If they’ve been modified, return them to your own preferences.

• This reply was modified 2 years, 4 months ago by Bob99.

Reply | Quote

This patch was installed on my Home pc as well as my Pro pc: neither one suffered what you relate. Do you have any evidence to support your argument?

Reply | Quote

GHacks agrees it’s not required.
https://www.ghacks.net/2020/08/29/microsoft-pushes-out-kb4023057-again-to-enforce-windows-10-upgrades/

cheers, Paul

Reply | Quote

On my W10Pro pc, after installing 2004, wumgr showed KB4023057 as installed. I checked again this morning, wumgr now shows it as pending, together with all previously hidden updates, mostly drivers. I hid them all.

On my W10Home pc, now updated also to 2004, KB4023057 has been installed, and am unable to uninstall it.

Reply | Quote

Ken wrote:

I checked again this morning, wumgr now shows it as pending, together with all previously hidden updates, mostly drivers. I hid them all. On my W10Home pc, now updated also to 2004, KB4023057 has been installed, and am unable to uninstall it.

KB4023057 is offered again and again. It either needs to be reinstalled or hidden each time, depending on your preference.

If KB4023057 has been installed and gives no problems, don’t try to uninstall it. Leave it in place.

Carpe Diem {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1778 x64 i5-9400 RAM16GB HDD Firefox115.0b2 MicrosoftDefender

Reply | Quote

So far 2004 has not been offered. Is the Conexant driver blocking this? Should I uninstall the driver and then wait for 2004 to be offered?

Reply | Quote

[Paul T]

It’s not blocked by the driver. You can do the 2004 update manually if you really want it, otherwise wait a day or two – there really is no rush.

cheers, Paul

• This reply was modified 2 years, 4 months ago by Paul T.

Reply | Quote

Paul T wrote:

Have you tried this advice from the link EP posted? UNINSTALLING (not “deleting”) the Conexant HD Audio Driver in Device Manager and then running the Windows 2004 update cheers, Paul

That worked for me.

I also saw a note somewhere that said Microsoft released something on Dec 11th which would get around the block. I’m sorry I don’t remember what.

Reply | Quote

Experimenting is the way others have found out.

Make an image backup to your external USB HDD, then test. Restore is simple – as long as you have created a rescue USB.

cheers, Paul

Reply | Quote

the anonymous person who has the lenovo ideapad 310 laptop can try to ask in the Lenovo community forums to see if others who have similar issues updating to 2004 because of old or outdated Conexant audio drivers

Reply | Quote

Yes, I’ve made a system image and posted to Lenovo forum.  So far, crickets.  Thanks for thinking about it.

Reply | Quote

I updated the audio driver from Conexant to “High Definition Audio Device” which works just fine.  Note, I did an update rather than an uninstall.  That was a week ago and am still waiting to have Windows Update provide the next version of the operating system — either 2004 or 20H2 — but, so far Windows Update has done nothing except offer January patches for 1909.   I wonder if a total uninstall is necessary to get rid of the Conexant problem so that Windows Update will offer the next available version?

Reply | Quote

See #2326241 above. That is what you need to do.

Reply | Quote

Is there some way to uninstall/remove the Conexant driver without having to install it again?  The MS driver works fine.

Reply | Quote

Yes, there is!  Use the open-source DriverStoreExplorer and check the box B4 the driver, then check the Force Deletion box, and then click Delete Driver.  Use wushowhide and hide the Conexant driver so it won’t install.  So, once again, I’m waiting for Windows Update to offer the next OS version.

Reply | Quote

The next day WU offered version 20H2.  It took 1.25 hours to download and install and an additional 1.5 hours for the restart procedure to finish.  Once again you must execute  wushowhide to hide the Conexant driver so it won’t install — this is because all the wushowhide info is lost during the installation of the new operating system.

Reply | Quote

[CraigS26]

With NO 2004 Ever offered per presumed Conexant issue & With multi-Macrium images ready …  I just went — from 1909 to 20H2 (19042.746) — AFTER Uninstalling my (Sound-Video-Game) Conexant driver 8.65.282.54 (NOT in the affected list, but who knows). I used the 20H2 Dnload page url at bottom, Clk’d Update Now button, the EXE file went to desktop, and it was just waiting on the process.

No one mentioned ref Uninstall Conexant Driver (You are about to uninstall this device from your system) AND a BOX “Delete software from this driver“. I did NOT Chk that box. As with others, the Same Driver shows in DevMgr now. AUDIO is working and I PRINTED a test Word Doc..

Almost forgot … I had to Re-Do GP setting Defining 2004 as my Target Release Ver. Couldn’t remember Correct Label for 20H2 so I chk’d Not Configured and No issues. So Re-visit your GP, etc. Blocks setup B4 proceeding..

Just found that Settings Update History is Blank and a little Nirsoft WU History Viewer App is Blank. Control Panel Update History has 8 entries incl’ing 20H2. Maybe Settings will evolve per some clock refresh.

It took about an hour & half.

https://www.microsoft.com/en-gb/software-download/windows10

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / HP Envy Desk-Ethernet - SSD-HDD/ i5(8th Gen) 12GB / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU=0

• This reply was modified 2 years, 4 months ago by CraigS26.
• This reply was modified 2 years, 4 months ago by CraigS26.

Reply | Quote

I would like report that I was successful in upgrading a Lenovo TP 420s from 1909 to 20H2 after a long wait due to the Conexant Driver issue. I uninstalled the driver in Device Manager (not deleted) before forcing the update. After the update the Conexant driver was back in play. Thanks for posting Craig.

1 user thanked author for this post.

CraigS26

Reply | Quote

On another topic, I have Microsoft 365, click-to-run version 2012, build 13530.20440. I never see this version in the update listings in the patch watch files nor in Susan´s list here.  How come?

Reply | Quote

Click to Run is never included in Susan’s list. It’s updated every time you run it.

cheers, Paul

Reply | Quote

It’s in the office section of the spreadsheets, first tab.  It’s also so much in the background that we often forget about it.

Susan Bradley Patch Lady

1 user thanked author for this post.

Ken

Reply | Quote

Oops! My bad.

cheers, Paul

Reply | Quote

As mentoned, my version Microsoft 365, click-to-run version 2012, build 13530.20440 is not there, I have never seen it even when the version number was different.

Reply | Quote

That version/build was released five days ago, nine days after the current Master Patch List was published:

Update history for Microsoft 365 Apps (listed by date)

Windows 11 Pro version 22H2 build 22621.1778 + Microsoft 365 + Edge

Reply | Quote

Paul T wrote:

Click to Run is never included in Susan’s list.

Click-to-run versions have been included right at the top of Susan’s Office Master Patch Lists for more than 18 months:

Office/Exchange Master Patch List

Windows 11 Pro version 22H2 build 22621.1778 + Microsoft 365 + Edge

Reply | Quote

Finally, last night, my Lenovo E420 with Conexant audio drivers offered the update from Win 10 Home 1909 to 20H2 Build 19042.746. I did it, and it went without a hitch. Audio is working fine.

Reply | Quote

Dear All

Just a couple of points from my side:

1. Thanks to all the good people here for sharing their experience – I was just able to update to Windows 10 20H2. I uninstalled and deleted the conexant audio driver and am now using the MS standard HD audio driver. So far, the conexant driver has  not reappeared.  I am using a Lenovo Yoga 12.
2. This seems to be the total normal situation of nobody being in charge at Lenovo or Microsoft or Synaptics, who bought conexant in 2017. So MS is blaming it on Lenovo who is blaming it on MS, both are blaming conexant/Synaptics and nothing happens. “Honi soit qui mal y pense” – just buy a new device …
3. Conexant was blamed for having installed a keylogger in their audio drivers, especially for HP computers. So this might be another good reason for getting rid of this old audio driver.
4. The driver / update situation at Lenovo is very bad with android devices. I love my thinkpads and will try to use them as long as possible. But stay away from Lenovo´s android stuff, you will most probably not get a lot of updates or none at all …

Cheers

Reply | Quote

We are still not being offered Windows 10 2004/20H2 due to the Conexant HD Audio Issue on a number of our HP workstations.

Under Device Manager – Sound, video and game controllers we see:

• Andrea Comm USB-SA Headset,
• Conexant HD Audio, and
• NVIDIA High Definition Audio

The only audio we use with the systems are the Andrea Comm USB-SA Headsets.

Should we consider uninstalling the Conexant HD Audio driver?

And if we do, what impact will it have on workstations?

Reply | Quote

The standard process is to remove the conexant driver and wait for WU to do it’s thing.
That isn’t an option in the office.

I would try downloading the 2004/H2 ISO, remove Conexant, disconnect from the internet, mount the ISO and run setup.exe.

cheers, Paul

Reply | Quote

Dell isn’t going to release updated drivers for their older computers. Inspiron computers seems to receive updates for around 3 years and Latitude computers will get 5 or 7. So sometimes you will need to find the corresponding Latitude of that generation and get your drivers from there. You need to be creative.

Reply | Quote