'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Microsoft 365 Not Updating via Group Policy
Question details
Microsoft 365 applications remain on older builds despite being configured to update via Group Policy for the Semi-Annual Enterprise Channel.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Administrators attempting to deploy and manage Microsoft 365 updates using Group Policy and the CDN.
- Observed behavior
- Updates do not apply as configured in the policy. Manual updates bypass the policy version, and update prompts appear despite being disabled.
Ensure you have administrative privileges to access Group Policy Management and can view system deployment logs on the affected machines.
Verify Group Policy Application and Target Version
Ensure that the Group Policy object is correctly applied to the target machines and that valid update parameters are set in the registry.
A cached or incomplete policy may prevent the update configuration from applying correctly to endpoint devices.
Open the Command Prompt as an administrator and run the command 'gpupdate /force' to ensure the latest policies are fetched from the domain.
Open the Registry Editor (regedit) and navigate to 'HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\office\16.0\common\officeupdate' to verify that the update channel and target version exactly match your intended policy.
Check the Office update logs located in 'C:\Windows\Temp' or your user '%temp%' directory. Look for files starting with the machine hostname and 'OfficeUpdate' to identify download or installation failures.
Reconfigure Updates using the Office Deployment Tool (ODT)
If Group Policy remains ineffective, use the Office Deployment Tool to explicitly set the update channel and reinstall or reconfigure Office.
Switch to WPS Office for Easier Software Management
Managing enterprise updates and Group Policies for Microsoft 365 can be complex and time-consuming. WPS Office offers a free, lightweight, and highly compatible alternative that is easy to deploy and manage across your organization without heavy configuration overhead.
- 1. Visit the WPS Website: Go to the official WPS Office website to download the enterprise or personal installer.
- 2. Download the Installer: Click 'Download' to get the lightweight setup file.
- 3. Install and Deploy: Follow the on-screen instructions to complete the installation across your devices quickly.
Frequently Asked Questions
Why does clicking 'Update Now' bypass my Group Policy settings?
The manual 'Update Now' button in Office applications connects directly to the Microsoft CDN and fetches the latest available version for that update channel. This action can override a specific target version previously configured via Group Policy.
Where can I find Microsoft 365 update logs to check the download status?
Office update and deployment logs are typically located in the system's Temp folder (C:\Windows\Temp) or the user's Temp folder (%temp%). Look for text files starting with the computer name followed by 'OfficeUpdate'.
Why are users still getting update prompts after I disabled update notifications?
This usually happens if the Group Policy object is incomplete, cached incorrectly, or failing to apply on the endpoint. Running 'gpupdate /force' or verifying the 'hideupdatenotifications' registry key can help resolve this issue.
