Why are some Microsoft 365 installations stuck on older builds?

0
4
Asked By MellowPine47 On

I inherited several Windows 11 devices managed through Intune that are stuck on Microsoft 365 Apps builds from previous months, including build 2605 on the Monthly Enterprise Channel. Windows Update and the update checker inside Office both report that the installations are current.

I checked the usual locations for update controls, including the Cloud Update policy keys, Intune PolicyManager settings, and the Click-to-Run configuration. Cloud Update is not enabled, and the Intune application XML does not specify a version. These devices are a mix of Windows 11 Pro and Business editions.

Could another Intune or Click-to-Run setting be controlling which builds are detected? In particular, could the Microsoft 365 Apps deployment be pinned to a specific version? Would changing the channel to Current through the Office Deployment Tool or the UpdateBranch registry value safely bring the devices up to date?

2 Answers

Answered By BrightCedar29 On

The Windows edition and supported-build matrix is worth checking too. Some older Windows editions or server versions stop receiving feature builds and only receive security updates. Since these are Windows 11 Pro and Business devices, that is less likely here, but comparing a stuck device with one that updates normally could still reveal a difference in edition or servicing policy.

MellowPine47 -

They are all Windows 11, split between Pro and Business, so I’ll compare the editions and focus first on the Intune app configuration and any target-version policies.

Answered By QuietHarbor8 On

Check the Microsoft 365 Apps application assignment in Intune before changing the registry. The app can be configured to install either the latest version or a specific build. If a specific build was selected, Office considers that version current, so Windows Update and the in-app checker will not look for anything newer.

Also check Settings Catalog policies for an Office target version or update channel. A deployment configuration and a policy can conflict, and the setting may not appear in the policy locations you already searched. Finally, inspect the ClickToRun configuration for an UpdateToVersion value; that can indicate the installation was pinned by the original deployment.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.