question

artsnob avatar image
0 Votes"
artsnob asked artsnob commented

Cannot install Feature Update to Windows 10 Version 21H1

I have been trying to resuscitate a Windows 10 machine that eluded updates for almost a year. The business has a well-maintained WSUS server, and as soon as I reconnected the Windows 10 machine, some updates began installing successfully.

Then came “Feature Update to Windows 10 Version 21H1 x64-based systems 2021-05 via Enablement Package.” (The machine is version 20H2.) The Windows 10 machine just displays a status of “Downloading – 0%” for more than two hours, then displays this message:

136408-image.png


I tried installing it via Windows Update, but after searching for updates, it always comes up with this:

136418-image.png

I thought of installing it via the Windows Update Catalog, but the documentation for it states that it isn’t available via this avenue.

I investigated error Ox80d02002 very thoroughly, trying out ALL of the suggestions in these three articles:

How to Fix Windows 10 Update Error 0x80d02002rror Code 0x80d02002: How to Fix It In Windows 10
How to Fix Windows 10 Update Error 0x80d02002
Fix Windows 10 Update error code 0x80d02002 (thewindowsclub.com)

None of the generic suggestions work. This is not a generic problem. I need some WSUS expertise if this problem is ever going to be solved. One thing I’d like to know is if the update is still actually ON the WSUS server, or just a record of it. Would the update failure still take two hours to time out if the actual download was missing?


windows-server-update-services
image.png (23.8 KiB)
image.png (17.2 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AJTek-Adam-J-Marshall avatar image
1 Vote"
AJTek-Adam-J-Marshall answered abbodi86-0005 commented

Have you added the .ESD mimetype to the WSUS Server? If you're using WAM, you can simply open the WAM Shell and paste:
Add-ESDMimetype

Otherwise, follow the instructions here:
https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-3-windows-as-a-service-waas-and-group-policy-administrative-templates/

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Enablement Package is regular msu package, not ESD

0 Votes 0 ·
artsnob avatar image
0 Votes"
artsnob answered

I've been a WAM enthusiast for almost five years, and tried what you suggested. The instruction seemed to execute OK, but it's total status quo with the Windows 10 machine refusing to download the update. Does the Mimetype take some time to kick in?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AJTek-Adam-J-Marshall avatar image
0 Votes"
AJTek-Adam-J-Marshall answered artsnob commented

Run the client side script and try again. It DOES have a delay in starting to work if the client already had downloaded the upgrade. It will eventually fix itself after 3 or 4 more attempts and then it will re-download it from the WSUS server. The client side script just speeds it up by wiping it right away.

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I’ve tried three more times without success. When you say “run the client side script,” you mean run the windows update program under settings, right?

Is there any way of discovering if the update actually IS on the WSUS server somewhere? Would its absence explain the result I keep encountering? And why does Windows Update keep saying that the machine’s up-to-date when it’s a version behind?

0 Votes 0 ·
artsnob avatar image artsnob AJTek-Adam-J-Marshall ·

Hey, I went to the WSUS console to remove the workstation as you suggested, and discovered that it was inoperable, -- "An error occured trying to connect the WSUS server"

I can’t restore it to operability – I tried all of the suggested remedies in the detailed error message that the “copy error to clipboard” produces (see attachment) and all of the ones I could find on the web, such as

WSUS Error: Connection Error
FIX: An error occured trying to connect the WSUS server
AN ERROR OCCURRED TRYING TO CONNECT THE WSUS SERVER

Also, the WAM script won’t execute at all.

Is it possible that that “Add-ESDMimetype” instruction you told me to try has something to do with this? That’s the ONLY change that has been made to the server recently.
137020-wsus-breakdown.pdf

The WSUS server is backed up daily, so I’m pretty sure that I can recover, although it will be tricky, with current SQL data having to be preserved before the restore and then copied back. I’d sure like to avoid this. Could you please look at the details in the attachment and confirm that it’s an off-the-map error that it’s futile to try and fix?


0 Votes 0 ·
wsus-breakdown.pdf (439.7 KiB)