I tried removing it, but same problems occuring
Windows update is stuck at 61%
Hello,
I am trying to update windows to version 20H2, however, the installation it's stuck at 61%.
What I tried:
1) I tried running this in administrator command prompt:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
2) I tried updating windows in safe mode,
**3)**I tried disabling every non Microsoft service in msconfig
**4)**I tried updating using the windows 10 update assistant
Does anyone know how to fix it?
Windows for home | Windows 10 | Windows update
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.
79 answers
Sort by: Oldest
-
Anonymous
2021-07-12T01:33:55+00:00 -
Anonymous
2021-07-13T00:59:50+00:00 Uninstall Sennheiser headphone drivers and then restart the PC, it will complete the update, you can reinstall those drivers after the windows update. Remember this method every time it get stuck in future, if you are still want to use that headphone. You can read my reply above
-
Anonymous
2021-07-13T01:00:03+00:00 Uninstall Sennheiser headphone drivers and then restart the PC, it will complete the update, you can reinstall those drivers after the windows update. Remember this method every time it get stuck in future, if you are still want to use that headphone. You can read my reply above
-
Anonymous
2021-07-13T01:06:55+00:00 Remove the sennheiser headphone related drivers, and then restart the PC and open update again, your PC will update successfully and after the update you can reinstall those headphone drivers, try this every time when a major windows update stucks in the future as long as you are using those headphones
-
Anonymous
2021-07-13T01:23:26+00:00 Audio drivers were deleted and reinstalled. That did not fix the issue. Continuing to try the update over a couple of months finally allowed the update. Microsoft must have made other changes to correct this condition. All is well now....