Solved MS is force installing 25h2 ahead of 26h2 release

glasskuter · 2026-06-23T13:23:14-0400

If this has been posted, I couldn't find it. @Brink put it wherever you feel it needs to go or delete it entirely at your disgression..

Microsoft is force-installing Windows 11 25H2 on every PC before 26H2, but it's actually painless

Microsoft is force installing Windows 11 25H2 on all eligible Home and Pro PCs, as it clears the decks ahead of the 26H2 release this fall.

www.windowslatest.com

Brink · 2026-06-23T13:30:59-0400

Known and Resolved issues for Windows 11 version 25H2

Windows message center: Windows 11 version 25H2 End of Servicing on October 12, 2027 https://www.elevenforum.com/t/how-to-get-the-windows-11-2025-version-25h2-update.40398/ Current status as of May 15, 2026 Windows 11, version 25H2 is now available for all eligible devices. Devices running...

www.elevenforum.com

glasskuter · 2026-06-23T14:51:29-0400

Got a feeling 25h2 will be installed whether folks with eligible devices want it or not (unless they make the registry change setting a target version and even that might be ignored.) Gonna be some more POed users just like every time before.

cereberus · 2026-06-23T15:09:26-0400

glasskuter said:
Got a feeling 25h2 will be installed whether folks with eligible devices want it or not (unless they make the registry change setting a target version and even that might be ignored.) Gonna be some more POed users just like every time before.

Not sure what your point is - 25H2 is current RTM version. 26H2 is only an Insider version yet to be released.

The only people who will get annoyed is tiny minority who have not updated to 25H2 which frankly does not make sense unless a user has a specific issue.

It seems to me it always seems to me to be the same small subset of people who get annoyed. The vast majority just go with the flow.

pseymour · 2026-06-23T15:29:35-0400

The only people who will get annoyed is tiny minority who have not updated to 25H2 which frankly does not make sense unless a user has a specific issue.

Yep, the most "disruptive" thing is probably the Start menu change, I reckon, and that's starting to show up on 24H2 machines, so you're not going to avoid it.

gunrunnerjohn · 2026-06-23T15:32:44-0400

I saw very little difference between the releases, certainly not enough to get my panties in a bunch.

MachineLanguage · 2026-06-23T16:47:37-0400

Might not be enough to get panties in a bunch but it sure affects my g string

pseymour · 2026-06-23T16:53:52-0400

MachineLanguage said:
Might not be enough to get panties in a bunch but it sure affects my g string

I always unplug my guitar when doing updates.

glasskuter · 2026-06-23T21:12:33-0400

cereberus said:
Not sure what your point is

I posted the article for information only.
My point for posting it is..... (and we still see it in threads here)... is that there are still holdouts out there with compatible machines that are running 24h2 by choice. I agree that their decision to do so makes no sense to me, but the fact is they are. From what I read, I believe they will wake up some morning and have 25h2.

Heck, there are still holdouts running 23h2 which blows my mind..

garlin · 2026-06-23T21:18:07-0400

glasskuter said:
Heck, there are still holdouts running 23h2 which blows my mind..

Why? If your PC doesn't meet the 24H2 requirements, or you only knew enough to bypass them at install time, you would be stuck on 23H2. Overcoming the upgrade check is different because the reg values aren't the same ones on a clean install.

PhilB · 2026-06-23T21:39:26-0400

cereberus said:
It seems to me it always seems to me to be the same small subset of people who get annoyed. The vast majority just go with the flow.

Not to forget all the 'normies' who do not read this forum.

glasskuter · 2026-06-23T21:42:28-0400

garlin said:
Why?

@garlin I was referring to holdout users with compatible machines, not incompatible ones.

garlin · 2026-06-23T21:58:15-0400

Maybe they really, really like the 23H2 Start Menu?? :shush:

glasskuter · 2026-06-23T23:49:10-0400

garlin said:
Maybe they really, really like the 23H2 Start Menu??

Nah, that ain't it. I think it's because:
1.They've read or heard about issues someone else has had and they let their paranoia hold them back. (kinda like me and SB

)
2. Many aren't experienced enough to deal with issues so their solution is to hold out rather than jump in with both feet.
3. They don't accept change.
4. They don't trust WU.
5. all of the above

We see this mentality every single time a new version comes out.
Always brings to mind how long some Windows 7 users wouldn't take the free upgrade to Windows 10 that would run on most anything.

Kudos Garlin for your contributions here.

garlin · 2026-06-23T23:58:50-0400

The required files to implement Secure Boot updates have been pushed across all Windows releases from W10 22H2, to W11, and different Insider channels. It's the same Secure Boot task that's expected to perform the work.

Windows versions that have ended support will have stopped with the Oct 2025 versions of the Secure Boot files. You can still use them to install CA 2023 and revoke CA 2011. What you don't get are newer versions of the boot manager (security fixes) that happened after Oct 2025. The core certs don't change over time, only the boot manager and additional DBX EFI signatures get refreshed for currently supported Windows.

If you have W11 24H2 or 25H2, and delayed installing the latest monthly updates, the same principle applies. You have all the files necessary to install CA 2023 and revoke CA 2011, but are behind on the boot manager fixes.

So not upgrading Windows because of Secure Boot is a red herring, or possibly because users are uninformed by the process (thanks MS!).

MachineLanguage · 2026-06-24T11:23:09-0400

@pseudosphere You gavem an idead. From now ono I will make sure there are non strings in tune boefer the windows updates.
Hopefully when I retune it will render powerless the potantial demons that have not yet been activated by windows. Wish me Luck.

spapakons · 2026-06-24T12:30:28-0400

Just a reminder, as soon as you can run 24H2, you don't have to do a full upgrade to 25H2 and then to 26H2 with all the risks involved. You can simply download and use the 25H2 Enablement Package to switch from 24H2 to 25H2 and in October use the 26H2 Enablement Package to switch to 26H2. The only difference between a Windows 11 compliant computer and an unsupported computer is that these updates are not offered via Windows Update. We have to manually download them from this forum or Microsoft Update Catalog and upgrade our unsupported computers. Also there is no compatibility check as with a full upgrade using the respective ISO. Regarding the start menu or other aspects of the GUI, thanks to Winaero Tweaker, Explorer Patcher and other similar tools we can cancel them and return to our preferred interface.

cereberus · 2026-06-24T13:38:12-0400

glasskuter said:
I posted the article for information only.
My point for posting it is..... (and we still see it in threads here)... is that there are still holdouts out there with compatible machines that are running 24h2 by choice. I agree that their decision to do so makes no sense to me, but the fact is they are. From what I read, I believe they will wake up some morning and have 25h2.

Heck, there are still holdouts running 23h2 which blows my mind..

Fair enough that you posted it for information but it is hard to have sympathy with such luddites.

MS made it absolutely clear over a decade ago about forced updates as too many pcs were getting infected with viruses etc. and MS were getting the flak that Windows was insecure.

It did not matter that most of the issue was caused by people blocking updates as was common in W7/8 days.

MS were facing a major confidence crisis and could potentially get sued for things outside their control.

One can love or hate forced updates but the undeniable truth is that virus attacks are much rarer.

Hell I spent half my time fixing infected pcs for friends and family but I cannot remember the last time I did that apart from one case where a friend had disabled defender and guess what....

In the end, this is really all old news revisited but one thing is sure MS are not going to change their policy and, frankly, I support this 100%.

One only has to remember the wannabe attack a few years ago. It was only W7/8 users AND W10 users who had blocked updates that got infected, not W10 users who updated.

Solved MS is force installing 25h2 ahead of 26h2 release

aka Mama Glass

My Computers My Computers

At a glance

At a glance

Administrator

My Computers My Computers

At a glance

At a glance

aka Mama Glass

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

We summon thee from the dead, old threads!

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

We summon thee from the dead, old threads!

My Computer My Computer

At a glance

aka Mama Glass

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

aka Mama Glass

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

aka Mama Glass

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Similar threads

My Computers

My Computers

My Computers

My Computer

My Computer

My Computers

My Computers

My Computer

My Computers

My Computer

My Computer

My Computers

My Computer

My Computers

My Computer

My Computers

My Computers

My Computer