• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Are you having HotKey issues? Click here for tips and tricks.
HP Recommended

You, sir, are a genius! Deleting the "HP Dock Audio" driver and running installation off of the dock did the trick. My ZBook G5 has successfully updated to Windows 10 v2004. Thank you!!!

 

HP Recommended

Envy 17 Laptop

HP Recommended

I have a similar problem, but with an Envy 795 desktop.   

However, I don't have a dock that I can disconnect.   No matter what I do, it keeps reinstalling the Conexant driver.

A post somewhere else recommended Drive Store Explorer, and using wushowhide from Microsoft (to disable the update that reinstalls the Conexant driver).   But, I can't find a version of wushowhide that is compatible with my version of Windows 10.

Any ideas?

 

HP Recommended

Unfortunately, none of the solutions posted earlier pertain to the last poster's issues or mine (which appear to be identical), both Envy laptops - no Dock, exhibiting the same Conexant auto-reinstallation issues, although I'm not positive that is the real issue -- what do I know.

HP Recommended

I am also seeing a Conextant driver repeatedly being installed/updated by Windows Update, a "Conexant - MEDIA - 7/3/2018 12:00:00 AM - 8.65.262.0".

BUT that didn't cause my stalled updates at 61%.

I am guessing it is another faulty packaging of a driver, were either version information is wrong, and/or it isn't applicable for my machine.

 

To really verify if that is the culprit of your problems with the Envy laptops, take at look at the log file generated during the stalled update (instructions provided in an earlier post, but I'll copy it here as well):

To examine the logs of the stuck Feature Update, I ran a tool called SetupDiag with the /Verbose parameter (https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag#setupdiag-in-windows-10-versio...

In the generated zip-file I then looked at the last rows in the "setupact.log" file, which mentioned "HP Dock Audio".

HP Recommended

Both Windows 20H1 and 21Hi fail at 61%

HP Recommended

I'm going to assume that this applies to 21H1 and not the earlier release; the results of SetupDiag Log analysis:

 

System Information:
Machine Name = HP-ENVY-17T-2
Manufacturer = HP
Model = HP ENVY Notebook
HostOSArchitecture = x64
FirmwareType = UEFI
BiosReleaseDate = 20180612000000.000000+000
BiosVendor = F.56
BiosVersion = F.56
HostOSVersion = 10.0.18363
HostOSBuildString = 18362.1.amd64fre.19h1_release.190318-1202
TargetOSBuildString = 10.0.19041.899 (vb_release_svc_prod2.210305-1721)
HostOSLanguageId =
HostOSEdition = Professional
RegisteredAV = Windows Defender
FilterDrivers =
UpgradeStartTime = 3/25/2021 9:30:03 AM
UpgradeEndTime = 3/25/2021 9:56:25 AM
UpgradeElapsedTime = 00:26:22
CV = ffvBpsLaZEWkOMjo
ReportId = CD1E50B5-E130-4D98-9B6E-A9922DC35D45

 

Unfortunately, I don't know how to decipher this. Anyone?

 

 

HP Recommended

And to add, the last files of the Logs.zip file, the attachment of the file being non-intuitive to me:

 

2021-03-25 09:56:25, Info MIG AddDriverFiles: Processing device: 4d36e96c-e325-11ce-bfc1-08002be10318
2021-03-25 09:56:25, Info MIG AddDriverFiles: Processing driver: Conexant ISST Audio, Conexant, Conexant
2021-03-25 09:56:25, Info MIG AddInfAndCatalog: Adding catalog file: C:\WINDOWS\system32\catroot\{f750e6c3-38ee-11d1-85e5-00c04fc295ee}\oem65.cat

HP Recommended

If that is the last lines of your log, then that is the last thing it tried to do before it stalled.

That means, you are still having problems with the "Conexant ISST Audio" driver.

Only advise I can give, is to try and find a newer version of it, than what you have installed. And don't rely on Windows Update to find a newer version of it, since that obviously doesn't work. First place to look

HP Recommended

Thanks Marcus! That was most helpful, leading me through what diagnostic to use and how to operationally use it, finally analyzing the result. Now comes that next step, finding a newer version of the driver.

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.