Windows 10 upgrade via WSUS gets stuck at 0% [FIX]
If you can’t upgrade to Windows 10 via WSUS, you’ve got the solution for you. Oftentimes, the Windows 10 upgrade process gets stuck at 0% and then fails after a few hours. If you’re experiencing the same issue, follow the troubleshooting steps listed below.
But first, here’s how one user describes this issue:
We have the same issue with multiple Windows 10 Professional client machines trying to pull update 1703 from WSUS. All stuck at 0% even after a 24 hour period. […] WSUS is reporting the client machines as “Updates with errors”
How to fix Windows 10 upgrade issues via WSUS
To fix this issue, you need to add the MIME type .esd (application/octet-stream) in IIS on the WSUS server. Here are the steps to follow: go to the WSUS server > Sites > WSUS Administration Site > MIME Types > add the MIME type .esd.
Once you’ve added the MIME type, your machine should start pulling the update. There is no restart required for the server or the client.
It is worth mentioning that the Windows 10 upgrade on WSUS gets stuck at 0% if you haven’t installed KB3159706. This update enables Windows Server Update Services to natively decrypt Electronic Software Distribution (ESD) in Windows Server 2012 and Windows Server 2012 R2.
Users must install KB3159706 on any WSUS server used to sync and distribute Windows 10 upgrades and feature updates released after May 1, 2016.
You can download this update from Microsoft’s Update Catalog website.
If you’ve come across other solutions to fix this Windows 10 upgrade issue via WSUS, you can list the troubleshooting steps in the comment section below.
RELATED STORIES YOU NEED TO CHECK OUT:
- How to fix Windows 10 0xc1800118 error on WSUS
- Windows 10 Fall Creators Update comes with more built-in security features
Two of the fixes made in version 20H1 were back-ported by Microsoft to version 1903 (Release Preview, build 18362.263). The first fix is about an […]
After the release of the new Windows 10 build 18362.10006 and the features unlock on build 18362.10005, few Windows insiders from the Slow ring started […]
Did you ever face error There was a problem and we couldn’t continue 0x80a4001a while you were trying to log in into your Xbox One […]