Receiving "Something went wrong" Error 30088-27 AND "You're up to date" when updating..

[LagunaJim]

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 ;)

[#2]

Ditto at 15407.20000. Tried both online and quick repair to no avail.

[#3]

I have the same error on:
Version 2207 Build 1547.20000 on Beta channel.

[#4]

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.

[#5]

from version 15407.20000, the same question.

[#6 · Accepted solution]

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.

[#7]

same here.

[#8]

Lo mismo con versión en español

[#9]

@LagunaJim 

Same here. Still no resolution?

[#10]

@BiserBorisov No comment from MS either.  I'll send them a link to this thread via twitter - maybe that will get us a response ;)

[#11]

Same error here - 5 Windows 11 Machine. Both RP or BETA Channels are affected ...

[#12]

Same here with Version 2207 Build 16.0.15407.20000 64 bits On Windows 10.

[#13]

Here 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.

[#14]

Same error here on two systems Version 2207 Build 15407.20000

[#15]

I've just upgraded to 15427.20000 and so far, I do not get the error message when checking for updates.

[#16]

@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.

[#17]

Update to 15427.20000 seems to have fixed the issue.