Windows 10 version 20H2 update stalls at 61% when updating from 1909

Topic

New Reply

This is a client’s computer and I have tried all the recipes, including all of them together, renaming the SoftwareDistribution folder, disabling the dreaded Conexant audio driver and stripping out a lot of the startup stuff with MSCONFIG.  This is a common problem with citations all over the internet, but the solution is certainly uncommon.  Of course, Microsoft offers no solution and a lame installation troubleshooter.

I attempted installation both ways, via Windows Update and with a Win 10 20H2 USB stick.  Same result.

What next, other than installing 20H2 from scratch after saving all the clients data, desktop, favorites, etc?  Would 2004 offer more chance of success?  21H1?

While awaiting a response, I guess I’ll try 20H2 from USB, disabling internet connection to prevent 20H2 updates.  After all, it’s only electricity that’s wasted after a few minutes of my time.

Reply | Quote

Replies

Try the Update Assistant?

*SOLVED* Windows 10 update 20H2 freezes, stuck, blocked at 61%

Reply | Quote

https://www.askwoody.com/forums/topic/ms-defcon-4-patching-is-approved/#post-2361686

Can you see if that helps?

Conexant folks are still stuck

Well, I have good news and bad news. The good news is that resident AskWoody subscriber and Windows 10 guinea pig Howard, whose 1909 Windows 10 machine suffered from the Conexant audio driver bug, was finally offered the 20H2 release. He had purposely held back to see whether Microsoft would automatically fix the issue with the audio driver. The bad news is that the Microsoft updating experience was less than ideal. From his notes:

• During the last stage of the update process, *before* the first reboot (from Windows into the upgrade environment), the progress stalled out at 61%.
• After waiting for more than an hour, he went into Event Viewer and saw an error message that the upgrade to 20H2 had failed. However, no such warning was presented within the WU interface, neither as a notification nor in any other way! Had he not scanned Event Viewer (most people would not), he would not have known the process had failed!
• He rebooted (as per MS advice that some systems may fail, and rebooting can resolve), went back to WU; again, process stalled at 61%.
• He did some research: the stall at 61% seems to be a common issue with systems having Conexant drivers during the insider phase of the 20H2 release, and for some during the general release.
• He rebooted again, disabled the driver (but did NOT delete or change to a generic), rebooted, launched WU — which was still stuck at 61%. He then rebooted once again, deleted the driver and its files (from within device manager), did not reboot, and then ran WU again.
• This time, 1909 was successfully upgraded to 20H2 (and pretty quickly, too).
• After logging into Windows post-update, he saw that the same Conexant driver had been downloaded and installed by Windows (which is something others have also reported).

As Howard noted: “Had I been an average user, I would probably have been stuck at 61% indefinitely. In my quick research, some reported being stuck at 61% for days and never completing the upgrade.”

As he put it best: “So the good news is I am on 20H2 and all seems well. The very bad news: MS ‘offered’ the update via Windows Update, which, one would assume, means they lifted the block and resolved the issue.”

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

This was the key instruction for me:

“He then rebooted once again, deleted the driver and its files (from within device manager), did not reboot, and then ran WU again.”

I have been trying since March to get this updated.  This finally did it.  I believe the issue I was having is that I was re-booting after deleting the Conexant driver and it’s software, and MS was re-installing it upon the re-boot!  So delete it, do not reboot, run WU.

Since WU was already running, and now hung at 61%, I also needed to stop it from running, then re-start it once Conexant was deleted.  I found the following instructions for this (I was not asked for an Admin Acct).  I suggest you first stop WU.  Then delete Conexant.  Then return here and re-start WU.  All without rebooting.  That did it for me, I am now fully updated:

At the Control Panel:
Click the left mouse button on the search box displayed in the Control Panel window.
Type in the search box: Administrative tools.
Click with the left mouse button or click on the Administrative Tools function. (You can also get to Windows Administrative Tools>Services from your Start menu.)
Now double-click on the Services function.

You may be asked for an administrator account and password, in this case you will need to enter them.
In the displayed list you should look for Windows Update.
Right-click on the Windows Update service. From the menu that appears, click Stop. You can also select the Restart option.

Reply | Quote

Thank you guys. From Services I stopped the Windows Update service, then   From Device Manager I removed the Conexant audio driver, I updated the audio driver from internet, I did not restart,  went to Windows Update and press “Download and install” ( the msg stuck in 61% wasn’t there any more after stopping the service) and now I am far away from 61%. Now it’s 88% and moving on.

Couldn’t wait till 100% to write the message!!!

Reply | Quote