Windows 10 Windows 10 Update 20H2 Stuck Failing at 61%, 100%, 99% Conversation

  • Thread starter Thread starter ACDeene
  • Start date Start date
A

ACDeene

Hi,


I'm just a novice however, I managed to successfully update to 20H2 from 1909 after facing some problems. (Stuck at 61%).


Seems like a lot of people are having the same issues and are finding that they are related to Conexant/Synaptics Audio Drivers.


I attempted to update the normal way via settings and updates however it was stuck at 61% Installation.


What I did was uninstall all audio driver related programs (Bose App, Sennheiser App etc.) and then uninstalled the Conexant HD Audio drivers and Intel Display Audio drivers from Device Manager.


Then I turned Wifi off. And made sure that the computer would not connect to the internet after a restart.


Then I went back to settings (with wifi off and drivers uninstalled). The update went past 61% and completed. It then asked me to restart then completed the update.


Good Luck!


P.S. I used this for help:


"I finally managed to crack it! I am now running 20H2 on my HP ZBook Studio G3!



The problem are those pesky Synaptics/Conexant audio driver(s). But lets start from the beginning:



Running HP Support Assistant yielded no updates.

Running HP Image Assistant only reported those faulty update packages I mentioned earlier (which doesn't update anything when run):

· HP Support Assistant

· Synaptics WBF Fingerprint Driver

· Intel NIC Driver

So no real updates there.



BUT when I manually compared the driver version of "Conexant ISST Audio" in device manager compared with the version sitting on the drivers download page for my computer, they were different. The drivers download page says that SP109031 (https://support.hp.com/us-en/drivers/selfservice/swdetails/hp-zbook-studio-g3-mobile-workstation/893... contains version 10.0.3690.0.

So I manually downloaded and installed it, but property page in Device Manager now reports 9.0.232.70, not 10.0.3690.0, but still it was different from before. Feels like the quality of drivers and their versioning is far from great .

So tried running Windows Update again but still got stuck at 61%.



So I dug deeper into the logs of Windows Update and saw the last thing it mentioned before getting stuck was "HP Dock Audio". I use the "HP ZBook Dock with ThunderBolt 3" and it turns out that it also uses a Synaptics/Conexant audio driver, only device is rebranded as HP Dock Audio. I had driver version 1.31.36.37 installed (seen on Property Page in Device Manager), and it's from 2019-11-21 and I've had that for a long time, and a newer version can't be found at the HP drivers download page for that product. Neither could it find an update when trying to run "Update driver" on the property page in Device Manager.



So in device manager, I instead right-clicked "HP Dock Audio" and clicked "Uninstall device", and made sure to select the "Uninstall drivers" option that is presented next. Then before rebooting, unplugged the dock connector (in my case the multi-cable with both charging and the USB-C connector), and instead connected only the charger/power supply.

After a reboot I ran the Windows Update again, and now it got passed 61% and after more than 1 hour it finished the feature upgrade to 20H2 (I had 1909 before upgrade).



When I then plugged in the dock, after the finished upgrade, Windows suddenly decides to install another driver for the HP Dock audio device, a Microsoft driver which seems to be a generic USB Audio driver. But it works. Looks like HP+Synaptics didn't do their part so Microsoft stepped up and did the work for them.



So problem was probably the two Conexant drivers - Both the Conexant ISST Audio device for built-in audio, and the HP Dock Audio device for the HP Thunderbolt dock.



Hope this can help someone else as well!



And if someone at HP is reading this - shame on you for not providing a fix for this!

And if someone at Microsoft is reading this - why haven't you provided a workaround for this or published information on how to do it. And publicly shamed HP+Synaptics for this mess. This problem has been with us for about a year since it also faulted the 2004 feature update (already insider builds)."

Continue reading...
 
Back
Top