21H2 -> 22H2 – 80242014

Topic

New Reply

I recently had to replace my laptop and did so with a no-name desktop, which came with Win11 21H1 installed.

When I first started the system, before the initial login-screen, “Updates in Progress” appeared for less than 30 seconds. After this, I logged in with my MS account, did some customizing (none of which caused any downloads to occur) and downloaded/installed Powershell 7.

I then ran WuMgr to check for updates and, not surprisingly, the upgrade to 22H1 appeared. I clicked on it and all went well. When it was done a “Need to restart the computer” message appeared. I closed WuMgr and restarted the computer. I was expecting the “Updates in Progress” to appear before the login-screen, but none did. After logging-in, I ran WinVer and saw the system was still at Win11 21H1. I ran WuMgr to check for updates and the status for Win11 21H2 was “in progress (80242014)”

I googled the error-code and all the responses suggested 1) run repair on Update (no problems were found), and 2) delete the SoftwareDistribution (SD) folder. After stopping the Update service I deleted the 4 SD sub-folders (I wanted to preserve the ReportingEvents.log file.) I immediately did a Restart (without restarting the Update service.) The problem persists after the restart.

Assuming there is no simple resolution I have 2 questions:
1) Should I attempt to do the upgrade from an ISO image?
2) Should I wait for 23H2?

—
Lee Silver

Reply | Quote

Replies

Before going any further, I’m presuming that where you mention Windows 11 21H1, you meant to say 21H2 instead.

You only did part of the necessary work to fully reset the Windows Update mechanism (which WuMgr uses to do its work). Please see the following AKB article here on AskWoody for the complete procedure, written by Susan Bradley:

https://www.askwoody.com/forums/topic/2000023-resetting-the-software-distribution-folder/

You needed to stop two other services and delete (or rename, your choice) a folder in another location besides the Software Distribution folder.

Once you’ve deleted (or renamed) the items listed in that article and you’ve restarted the three services you stopped, then run WuMgr and see what it says about your update from 21H1 to 22H2.

A WORD OF CAUTION (based upon my own painful experience doing this same procedure incorrectly by mistake): ONLY delete or rename the folder labeled “catroot2” in the System32 folder. DO NOT delete or rename the folder labeled “CatRoot” in the System32 folder.

One final note. Unless I’m mistaken, I believe that the upgrade from 21H2 to 22H2 is via an enablement package that’s rather small in size, so the actual work shouldn’t take more than 5 minutes or so, complete with a successful reboot.

I hope this helps.

Reply | Quote

One final note. Unless I’m mistaken, I believe that the upgrade from 21H2 to 22H2 is via an enablement package that’s rather small in size, so the actual work shouldn’t take more than 5 minutes or so, complete with a successful reboot.

WRONG!

For Windows 11, the 21H2 to 22H2 upgrade is a FULL-FEATURE upgrade from build 22000 to 22621. therefore, it is NOT a small update.

It’s only in Windows 10 where going from 21H2 to 22H2 in that version is done by “enablement package” from build 19044 to 19045.

1 user thanked author for this post.

Bob99

Reply | Quote

Bob99 wrote:

…Unless I’m mistaken, …

Well, I guess I was indeed mistaken. 😳

@EP , thanks for the correction! BTW, can you please pass the salt and pepper, they might make my foot that I stuck in my mouth taste a little better!  😉

Reply | Quote

Bob:

Thanks for the response.

Yes, 21H1 should have been 21H2.

I followed the steps on Susan’s post as follows (all with no success):

1) I stopped the 3 services and renamed the 3 folders. I then re-booted.

2) I stopped the services and, keeping the .bak-folders, deleted the newly created folders. I ran WuMgr, which showed the upgrade as pending. I clicked ‘install’ and when it was done (displayed the ‘need reboot’ message) I rebooted.

3) I re-did step (2) until the reboot. I again stopped the services and, keeping the .bak-folders, deleted the newly created folders. I restarted the stopped services and rebooted.

Reply | Quote

Is your PC compatible with W11 22H2 (not all running 21H2 are compatible)

Reply | Quote

Since the machine came with Win11 preinstalled I was fairly sure it would be 22H2 compatible.

I checked via the link you supplied anyway (never hurts to double-check) and it is 22H2 compatible.

Reply | Quote

Something probably unimportant that I forgot to mention…

After the very first time I used WuMgr to attempt the upgrade the “Update in Progress” status also displayed the error-code. On all other attempts the status was “Update in Progress” by itself.

Reply | Quote

WuMgr is just a front end for Windows Update. Any messages will be from WU.

cheers, Paul

Reply | Quote

Might be time for a repair over the top, after an image backup of course. Got a misbehaving Windows 10? reinstall

cheers, Paul

Reply | Quote

Lee-

After reading through what you say you’ve tried up to this point, and what @EP has said above, it seems to me as if you may have a loused up servicing stack that’s not quite right. To fix this sort of thing, you may want to first run the dism tool that’s built into Windows (run it from the command line with Administrator privileges) using the following command:

DISM /Online /Cleanup-Image /RestoreHealth

Let it run to completion without doing anything else with the computer while it’s running. It will take a little while (up to 10 or 20 minutes depending on if it finds any corrupt files to repair). Once it’s done, it will tell you what it found and what it did if it found anything that needed fixing.

Next, run the following command, again from an elevated command prompt:

sfc /scannow

As with DISM, let it run to completion. It shouldn’t take as long as DISM and it will do the same thing as DISM when it’s done, in that it will let you know what it found and what it did if it found anything to fix.

Once you’ve completed BOTH of these commands in the sequence indicated, proceed to try checking for the upgrade again and if it shows up, proceed with the installation, rebooting when you’re asked to.

If you’d prefer not to do these, or if you’ve done them and you’re still experiencing the same error code, then @Paul-T ‘s suggestion above is a very viable alternative with the caveat he mentions. Although the link points to an article here on AskWoody that was intended for Windows 10, the same procedure probably works just as well on Windows11.

Reply | Quote

Bob:

Thanks for the response and advice.

Both DISM and sfc ran successfully with no error/warning.

I then ran WuMgr with the same results – Restarted after it ran and updates not applied.

Since 23H2 is coming soon, I’ll wait for it. At that point, if I still cannot upgrade via WuMgr I’ll download the ISO and try to install from that.

—
Lee

Reply | Quote

Thanks for the update and the effort to try to repair the servicing stack.

If the 23H2 update does the same thing, then I believe @Paul-T ‘s solution might just be the way to go.

Here’s hoping you have better luck with that!

Reply | Quote