[German]There seem to be problems with one of the latest Office updates, which affects the Click2Run versions of Microsoft Office 2016, 2019, 2021 and Office 365 version 2406. The attempt to perform an update search and update to the next build then fails with error code 30088-27. Here is the message from an affected person and the question: Are there other victims?
Advertising
A reader report on error 30088-27
Blog reader Rolf W. contacted me by email (thank you) and reported an issue that's annoying him under the subject "Office patched broken again?". He uses Microsoft Office 2019, which is only available as a Click2Run installation. Microsoft Office itself works, but the update function is broken. In June 2024, he was still able to update his Office 2019 installation without any problems. When he tried to update his Microsoft Office 2019 on July 3, 2024, the following error dialog appeared after selecting the Update button:
This is the German edition of the dialog box. The statement (translated) "Unfortunately, that didn't work" and the indication that a problem occurred when searching for updates is not very helpful. It is clear that the update function integrated in Office cannot contact Microsoft's update servers.
Further reports on the web
Blog reader Rolf sent me a link to the askwoody.com forum post Office Click-to-Run Updates May be Broken with Latest Version. The post from June 29, 2024 states that Microsoft is using Office 2019 Click-to-Run from June 19, 2024. This is the same build as Microsoft 365 V2405 17628.20164, which was updated to V2406 17726.20126 on June 26, 2024. And now the update search in Microsoft Office returns the error code 30088-27 ("Something Went Wrong"). So the same as Rolf reported above.
The user tried various things such as an Office repair, but was unsuccessful. Only a new installation brought success with Office 2019 (V2405 17628.20144 from June 11, 2024). But after updating to v2406, the above error was present again.
Advertising
I did some research, the error seems to be widespread. In the Microsoft Answers forum there is the post Update error code 30088-27 Office 2021 what to do to get correctred???? dated June 29, 2024, where the thread starter uses Microsoft Office 2021. There are other victims who have spoken up in the thread. Another Microsoft Answers thread can be found here.
There is also a post on tenforums Office 2016 C2R Update Error 30088-27, which complains about the error for Office Home And Business 2016 Version 2406 (Build 17726.20126 Click-to-Run). The only remedy is to go back to the previous build with the following steps:
- Disable Microsoft Office Updates (File/Office Account/Update Options and select the Disable Updates option)
- Open an administrative command prompt and then enter the following command to go back to the previous version.
"C:\Program Files\Common Files\microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16.0.17628.20164
There is an old Techcommunity post Receiving "Receiving "Something went wrong" Error 30088-27 AND "You're up to date" when updating.. from 2022 that also deals with the topic. Let's hope that Microsoft can also automatically fix the error on systems that have not been rolled back to the previous build. Anyone affected?
Advertising
Yes, same problem with Microsoft 365 since last update. The roll-back suggested by you did work. Thx.
I had the same problem. You solution is OK, thank you but when can I turn on Office Update again?
Go to privacy settings in Microsoft Office. Check "turn on all connected experience". Then you MUST restart your PC. Now try updating it again.
I have identified a solution that address this specific issue, as this exact problem affected my environment starting with the June Office Updates.
It appears that Microsoft has changed the communication method for Office Click-to-Run. Previously, OfficeC2Rclient.exe used the WinInet proxy settings (Internet Settings) to connect to Microsoft's cloud services. However, following the June update, OfficeC2Rclient.exe now utilizes the WinHTTP proxy (configured via NetSH) for communication.
Depending on your environment's configuration, systems without a properly configured WinHTTP proxy will default to using the Default Gateway to access the internet. This could result in traffic being blocked by your Default Gateway Firewall, as such traffic typically routes through a proxy. In environments where a WinHTTP proxy is configured to use an actual proxy server, authenticated proxy rules may cause the traffic to fail with a 407 error, as the Windows WinHTTP proxy does not handle authentication well.
In our environment, we addressed this by reconfiguring our firewalls and proxies to allow the necessary communication. Given the risks associated with recent CVEs affecting Office products in the past couple months, I hope this information helps others who have been unable to update their Office installations, thereby reducing their exposure to potential vulnerabilities.
Mark, thx for your feedback. Do you have more details?
This morning (August 17, 2024) I received feedback from German readers, that Office C2R is "suddenly" able to update. It seems that Microsoft has fixed this server-side.