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 No 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 No comments

65 additional answers

Sort by: Most helpful
  1. Anonymous
    2019-09-06T00:56:21+00:00

    THANK YOU

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-09-05T22:59:16+00:00

    But no XLOOKUP yet! :-(

    You should have XLOOKUP today. They pushed it to all insiders late yesterday.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2019-09-02T16:05:13+00:00

    I have the same issue

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2019-08-29T22:05:36+00:00

    The team believes they have identified the issue and are working on a fix. I don't have an exact timeframe, but hopefully it will be resolved by tomorrow.

    -Jesse

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments