Update error code 30088-27 Office 2021 what to do to get corrected????

Anonymous
2024-06-29T17:25:07+00:00

Update error code 30088-27 Office 2021 what to do to get corrected????

Microsoft 365 and Office | Install, redeem, activate | Other | Other

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

345 answers

Sort by: Most helpful
  1. Anonymous
    2024-07-26T16:35:45+00:00

    My problem did not resolve, with your solution, do you have any other solution?

    There IS no solution. We need to wait for MSFT to fix this on THEIR end.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-07-26T16:19:58+00:00

    ITNOA

    My problem did not resolve, with your solution, do you have any other solution? my office version is Microsoft® LTSC MSO (Version 2406 Build 16.0.17726.20078) 64-bit

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-07-26T11:15:33+00:00

    I also had the same problem with Office 2024 Preview which started from Update 2407 (build 17830.20056) after licence-switching retail.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-07-25T10:49:45+00:00

    Happened to me as well. I'm on the retail channel, made a online repair of Microsoft 365 a couple of days ago and got version 2407 (build 17830.20094) from the preview channel. But the issue is still existenting. Then I deinstalled and reinstalled Microsoft 365 from the retail channel and now I'm having version 2406 (build 17726.20160) again on my system.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-07-25T10:08:43+00:00

    A few days ago I did an online repair and I am not a preview channel subscriber.
    I was updated to the 2407 build of Office 365 on a Windows 10 Pro Machine. I was till getting the error.
    Today I did an online repair of 2407 and the error is not fixed.
    I have rolled back to 2405 and will wait to update once the error is confirmed as being fixed.

    Was this answer helpful?

    0 comments No comments