Office Insider - Error Code 30088-28

Anonymous
2019-08-29T18:15:04+00:00

Insider was working just fine. Then yesterday this error message 30088-28 came up after I tried to download the most recent update. I then tried a restart, then a quick repair, then a full repair. The full repair gave a different error message that 'something went wrong', the consequence being that Office was completely uninstalled. I then reinstalled it, restarted, and tried again to update to Insider - it came right back to the 30088-28 message! 

I urgently need to get back to Insider - can someone please help me?

Microsoft 365 Insider | Install, activate, and update | Windows

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.

0 comments
Answer accepted by question author
Anonymous
2019-09-04T20:27:59+00:00

I have received confirmation from the team that they have resolved this with the latest build, and it looks like several others in this thread have successfully updated today. If you were experiencing this error, please try updating again. If you run into any further issues, please create a new thread and provide details.

-Jesse

Was this answer helpful?

6 people found this answer helpful.
0 comments

65 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-08-29T22:06:05+00:00

    The team believes they have identified the issue and are working on a fix. No firm timeline quite yet, but hopefully by early tomorrow.

    -Jesse

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-08-29T22:18:52+00:00

    That's fine, thanks.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-08-29T23:43:38+00:00

    I don't know when you posted this Jesse but I got 1909 b12026.20000 today, which is newer than what I got on Tuesday (don't recall that exact build number).

    Not sure if this is the expected fix, or if a newer one is forthcoming. I did not hit this error, so cannot validate anything.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-08-29T23:55:15+00:00

    12026 is the build where it first turned up. So this is probably a case where you didn't happen to check for updates (or Office didn't try to update itself) during a certain window of time starting last night when 12026 was first made available and almost immediately threw that error when attempting to update to it. Those who did make the attempt may be stuck now given that you avoided the problem entirely, proving it's not currently a bad build.

    Was this answer helpful?

    0 comments