I'm encountering an unusual issue with the November build of Office 365 version 2508 (19127.20358) as well as version 2507 (19029.20294). We primarily use the Semi-Annual Channel for our Microsoft 365 apps, but with the recent elimination of the Semi-Annual Preview Channel, we've been piloting changes on a select number of devices using the Monthly Enterprise Channel. Now, as we're ready to deploy the November build to a larger group, the installations are failing with an error message saying "Something went wrong" along with error code 30094-44 and "InvalidSignature" errors in the Office ClickToRun log. I've attempted multiple installations across different setups, including fresh installs and clean configurations with the Office Deployment Tool, yet all methods result in the same failure. I'm wondering if anyone else is experiencing this issue or if there are known fixes pending from Microsoft.
4 Answers
Hey there! I feel your pain with the installation failure! It turns out that the issue is related to an update in Microsoft's signing certificates. The certificates for the .cat files got mixed up, affecting compatibility with older ClickToRun clients, especially on S-mode systems. Although it seems this shouldn't affect non-S-mode machines, it's best to report it if you've noticed problems. In the meantime, there are a couple of workarounds:
1. Uninstall the current version and reinstall it.
2. Update to the September version (2509) first, then downgrade back to 2508. Just a heads up, these might not be practical for large scale deployments, but the official fix should be out soon!
Thanks for the insight! We're not using S-mode either, and I'm having a tough time with the uninstall/reinstall workaround. Does this mean uninstalling the newer version first? That seems convoluted. I'm planning to try the second workaround but it's not really scalable for our team. Any idea when the official fix might drop?
We tried both versions too and hit the same snag! We managed to download 2509 without issues, but that's no help since we're trying to test 2508 as a release candidate. It's frustrating since we need to move forward with our testing!
We’re in the same boat here! The 30094-44 error is a headache, especially when we're trying to move to the next release candidate. Any updates from Microsoft would be great. Seems like they’re aware but nothing concrete yet.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures