Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
Maybe in your case. All our customers are in 2406, Build 17726.20126 and all the Office products report the same version.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Update error code 30088-27 Office 2021 what to do to get corrected????
Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Maybe in your case. All our customers are in 2406, Build 17726.20126 and all the Office products report the same version.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
I'm getting the same errors with 2406 Build 16.0.17726.20078
And on the same version 17726.20078 I have the same error!!!
So, can we conclude that there is some kind of problem with the 2406 - 17726.20126 version?
Microsoft ... are you listening? (Linn)
mschmieg et all,
The uninstall and reinstall NEVER worked for me. My apologies if I mislead you.
But, if it did for you, could you detail every step? I am installing directly from the M365 portal, so I have no access to a MSI package.
Regarding Online Repair, I tried both. No love.
I've done the uninstall and reinstall twice now - neither has solved the problem. After reinstalling from the MSI, the update works, but, after it reaches the current version, the update no longer works and it's back to where it started.
I also had no luck with the Online Repair; however, I suspect that, when a new version is released and the update does not work, the Online Repair will bring the software to the current version. I think that may well be the workaround until this issue is resolved.