Solved Can no longer update Win 11 version 25H2 (OS Build 26220.7019) IoT Enterprise LTSC

Hi. Updating issue, again:

Since about two months or so, I’m no longer able to update my Windows 11.

My desktop Dell Inspiration 3630 PC used to run:
Windows 11 insider beta channel, version 25H2 (OS Build 26200.7019) IoT Enterprise LTSC
As far as I know build 26200.xxxx denotes an insider beta channel build …

Then around late October / early November 2025 I noticed that somehow a recent update must have moved my Win 11 install to the insider dev channel, as my PC suddenly started to run:
Windows 11 insider dev channel, version 25H2 (OS Build 26220.7019) IoT Enterprise LTSC
As far as I know build 26220.xxxx denotes an insider dev channel build …

Ever since this fateful (and uninvited) ‘upgrade’, my system updates as well as protection updates fail to install new versions. I can download the latest builds no worries, but on each time the installation routine ends at around the 75% mark with a simple message that the update was not install. No reason, no error code.

Perhaps I should mention that I also installed the MS Store app as I needed a couple of apps from there, Stardock’s Start11 start-menu plus the latest release of ExplorerPatcher (I like my task-bar at the top) … Nothing else non-standard springs to mind.

I’ve tried the usual-advise routines, like:

dism / sfc /scannow restoreHealth / cleanup-image commands health routines
or:
net stop bits / net stop wuauserv / net stop cryptsvc commands
plus Shawn Brink’s excellent (and thanks 1001) tutorial, but nothing has worked so far.

Other than this update issue, my Win 11 install works just fine. So I’m wondering if any of the following may have impacted on my Win 11 install’s ability to run further updates;

• Could the (uninvited) move from 26200 to 26220 have stumped my Win11’s ability to update?
• Could it be that this Dev version now conflicts with the Enterprise version?
• Could it be that the Dev channel updates no longer accept installing on IoT and / or LTSC builds?
• On this system I run Windows 11 with a local account. Do I now need now to change to a Microsoft-based account to be able to receive / install / run Windows 11 updates?

I realise I’m picking at straws here, but I can’t think of anything else that may point me in the right direction.

If all else fails, I might just sit this one out and wait until the next major update in the fall comes our way and see how that flies, before contemplating to start from scratch – once again.

These constant updates are a bit of a bummer lately, but hell, where would we be without Gates and Windows… LOL

Any and all advise would be very much appreciated. Cheers to ya’ all. Ajarn AJ

i had similar problem, i fixed it with ntlite, i used latest 26100.1742 MSDN build + KB5066383 + 26220.7535, but ntlite had problem with KB5072046 4gb MSU file, i had to remove all MSIX files using 7zip then use this script and after that integration worked https://github.com/abbodi1406/WHD/raw/master/scripts/PSFX_MSU_5.zip in-place upgrade also working as well

Thanks, George2024, I'll give it a shot during the week. For now, off to bed (AKL 1.42am )

You have type lots of things but no information about error message.

Use Windows Update Troubleshooter.

• Right-click on Start button and pick Settings
• Go to System > Troubleshoot
• Click on Other Troubleshooters > Windows Update and click Run button.

Download Windows updates manually.

• Go to the official Microsoft update catalog;
• Enter a specific update code, for example, KB4481031
• Select the correct version and click Download
• Click on the link and Windows will update your computer

Resetting the Windows Update components can usually solve these types of issues.

@guru: Please note:

Thanks for the heads-up, but with all due respect, perhaps you need to re-read my, admittedly long, original post. In respond to you writing:

“You have type lots of things but no information about error message.”

Did I not, and specifically, write in paragraph 4 or 5 of my original post:

“No reason, no error code.”

What could be clearer than that?

If I did have an error code, indication or otherwise, I would have mentioned it right there!

It goes without saying that if I had gone down the (these days largely pointless) troubleshooter alleyway, (pointless, as MS is working hard to depreciate / replace it in the hopefully near future), I would have included any found causes. And yes, of course I gave it its best shot, but to no avail (hence I didn’t bother pointing that out).

So here in retrospect, in fact said troubleshooter returned finding nothing, nana, zilch, nix (as expected)!

As to checking / downloading manually relevant MS catalogue KB files: Yes, charged as guilty.

Perhaps I should have included a note that I did this kind of routinely, after checking other options related to troubleshooting MS Win 11 update issues, including relevant files. I downloaded, specifically, but not exclusively:

• Update KB5043080 – crucial Sep 2025 cumulative security update, must be already installed – checked A-ok
• Windows11.0-KB5072046-x64.msu– should update Win 11 install to version xxxx.7535, tried without success

As pointed out in my original post: Downloaded A-ok, but refuses to install past ~75%, stops install routine, then reverses all changes and says “The update could not be installed.” Again: “No reason, no error code.”

You could also re-read how my further testing revealed that somehow the enablement packages for converting a 26200 install to a 26220 build, namely KB5066383, already were installed on my build. In other words, my install would have, and unbeknown to me (should have checked before, right?), already transferred to the dev channel (see my short but relevant explanation in my original post).

How my install changed from a beta insider build to a dev channel build remains a debatable mystery. Perhaps you’d like to comment on that? My two cents worth? Perhaps a more recent MS update sneaked that in? I seem to remember many online odd user-complaints about MS having sort of logic-defying upped many retail(?) users to an insider build around October last year without announcing that deed …

Lastly, you have pointed me, quiet correctly, to Shawn Brink’s excellent (and thanks 1001) tutorial. Perhaps you missed my pointing out this specifically in my original post? I even included Shawn’s name and hyperlink? And similarly missed that I specifically wrote “… but nothing has worked so far”?

Look, I do understand that you are trying to help us incompetent Windows users to stay on the right path, and that’s really greatly appreciated. But perhaps paying a little more attention prior to presuming the poster hasn’t included relevant information, does seem a tad …. well, presumptuous.

Thanks for all. Cheers AJ