Win11 25H2 enablement package installs successfully, but OS is still reporting 24H2 after reboot

Hey all,

Wondering if anyone has any thoughts or suggestions on where I can look for an issue I'm encountering. I have a fleet of workstations and VDI VMs that are running 24H2, and several have taken the enablement package for 25H2 without issue. However, on a handful of both physical workstations and VDI VMs, the enablement package installs without any errors, but on reboot the system still reports itself as 24H2. I've tried installing via WUSA and DISM, and both have the same outcome. The other systems that are installing without issue are identical specs and update levels, so I'm at a loss as to where to look to troubleshoot. Obviously this isn't an issue that is super critical today, but in order to keep the systems on a consistent baseline I'd like to figure this out sooner than later.

Anyone else experience this hiccup, or have any suggestions on where I could look?

Thanks!!

Where does it report it's 24H2? Settings app, Winver, etc?
What's the full build number? Which Enablement Package did you install (there's a few versions of it floating around)?

Winver will always show the version and the build number.

garlin said:

Where does it report it's 24H2? Settings app, Winver, etc?
What's the full build number? Which Enablement Package did you install (there's a few versions of it floating around)?

Click to expand...

Yes to both - full build number is 26100.4652

The enablement package I installed is windows11.0-kb5054156-x64_9fd13360d2c5af23ec4f591b86f1c1db37aada37.msu

SilvaFox27 said:

Yes to both - full build number is 26100.4652

The enablement package I installed is windows11.0-kb5054156-x64_9fd13360d2c5af23ec4f591b86f1c1db37aada37.msu

Click to expand...

Here's the link to the official one...

windows11.0-kb5054156-x64_a0c1638cbcf4cf33dbe9a5bef69db374b4786974.msu

means you still need updates. the enablement package will be successful but you need to keep running windows updates. i've seen this on multiple PCs after running the 25h2 EP. ran updates a few more times and then the winver changes to 25h2.

The minimum baseline for the production EP is August 2025 Preview (26100.5074). Your 26100.4652 (July 2025) release needs to be updated to Sep. 2025 or later for 25H2 to take effect.

There were other EP files for the Preview builds which enabled earlier versions of RP to 25H2, but you shouldn't be playing with them on a production system.