Forum Discussion
Receiving "Something went wrong" Error 30088-27 AND "You're up to date" when updating..
After the update to 15330.20004, when performing an Office Update I get BOTH a dialog that says I'm up to date and simultaneously an error 30088-27 (see attached image).
Performed an online repair, then an uninstall and reinstall (not clean). Issue persists.
Not hung up on it since it seems I also got the latest update ๐
- Expect an update to build 15414 or higher. According to preliminary information, the error was fixed at an early stage of internal testing.
Please note that I am writing on behalf of an ordinary member, so my words cannot be considered an official response from the company.
35 Replies
- David OvertonCopper ContributorI've just upgraded to 15427.20000 and so far, I do not get the error message when checking for updates.
- danielbickelCopper Contributor
David Overton Same.
I've just upgraded to 15427.20000 and so far, I do not get the error message when checking for updates.
Seems to be fixed.
- tomelixCopper ContributorUpdate to 15427.20000 seems to have fixed the issue.
- Oberth1715Copper ContributorSame here with Version 2207 Build 16.0.15407.20000 64 bits On Windows 10.
- hstrangCopper ContributorHere as well with the same versions. Not a single word or a fix from Microsoft. Nice support for all of us who are prepared to alpha test their products.
- HappyrocksCopper Contributor
Same error here on two systems Version 2207 Build 15407.20000
- eRaz0rCopper ContributorSame error here - 5 Windows 11 Machine. Both RP or BETA Channels are affected ...
- BiserBorisovCopper Contributor
Same here. Still no resolution?
- LagunaJimCopper Contributor
BiserBorisov No comment from MS either. I'll send them a link to this thread via twitter - maybe that will get us a response ๐
- Fernando Pujol HerreroCopper Contributor
Lo mismo con versiรณn en espaรฑol
- danielbickelCopper Contributorsame here.
- ะะปะตะบัะตะน ะะพะปะผะฐัะพะฒCopper ContributorExpect an update to build 15414 or higher. According to preliminary information, the error was fixed at an early stage of internal testing.
Please note that I am writing on behalf of an ordinary member, so my words cannot be considered an official response from the company. - NextCatCopper Contributorfrom version 15407.20000, the same question.
- DerrikdennisCopper Contributor
I'm experiencing the same issue. I'm on Windows 11 Insider Preview 22621.1 (ni_release) and am on Build 15407.20000. Neither online nor quick repair solves the issue.
- m1hn3aCopper ContributorI have the same error on:
Version 2207 Build 1547.20000 on Beta channel.