I deployed Windows 11 25H2 Feature Update via Intune, but some devices temporarily show 24H2 before reaching 25H2

Question

I am trying to upgrade Windows 11 feature update from 23H2 to 25H2.

I have deployed Windows 11 25H2 Feature Update using Intune Feature Update policy.

Observed, A subset of devices temporarily report version 24H2 instead of 25H2 during the upgrade process.

Would request please help.

Answer 1

Hi Rajesh Gupta,

What you are observing can happen during staged Windows feature update servicing and is not always a problem with the Intune Feature Update policy itself.

In some cases, devices upgrading from Windows 11 23H2 may temporarily report 24H2 before finally reaching 25H2 because:

• Dynamic Update components

Enablement packages

servicing stack sequencing

or intermediate platform updates

are applied during the upgrade workflow.

A few things to verify:

Check whether the devices eventually complete to 25H2 Some devices may briefly report 24H2 during:

setup phase

first reboot phase

post-OOBE servicing

before final compliance updates complete.

Verify safeguard holds Some hardware/drivers may currently have compatibility holds that temporarily block direct transition to 25H2.

Check:

Windows Update for Business reports

Intune Feature Update deployment reports

SetupDiag logs

WindowsUpdate.log

Review Update Rings and Expedite policies Conflicting:

Update Rings

Quality Update policies

Expedite policies

driver policies

can sometimes cause devices to receive intermediate builds first.

Confirm installed build numbers Sometimes the displayed release label can lag behind the actual servicing state.

Check:

winver

and:

Get-ComputerInfo | Select WindowsVersion, OsBuildNumber

Verify device eligibility for direct 25H2 enablement Some systems may require:

latest SSU

latest cumulative update

BIOS/firmware updates

before the final 25H2 enablement package is offered.

If devices remain permanently on 24H2 and never transition to 25H2 after several scan cycles/reboots, then it would be worth investigating:

safeguard holds

deployment conflicts

or feature update applicability rules

But if the state is temporary during deployment, that behavior can occur during staged servicing transitions.

If my answer is useful for you, please hit Accept Answer to support me.

Thank you so much.