MAU still didn't work

Anonymous
2019-10-16T18:20:05+00:00

Split from this thread from months ago

Well it's now October, and 16.30 just arrived. The MAU still didn't work. I noticed that it's now combined with the update so didn't try to download the updated first this time. But symptoms are all the same - the updater recognized that I needed all applications and told me to install 16.30 and when I saw the progress bar, each package showed download progress but the overall download progress kept resetting each time to zero and the package didn't finish saving on my Mac. At the end I got the telltale message "One or more packages..." 

This is the problem that Microsoft doesn't want to fix because they don't have enough people reporting it or saying they have the problem. 

So I'm a 365 subscriber who pays money to have what Microsoft described as the package I was purchasing and they're not going to provide it.

I guess this is what happens when integrity is an option left up to the workers and not the leaders.

Microsoft 365 and Office | Install, redeem, activate | For home | 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

79 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Jim G 134K Reputation points MVP
    2019-10-18T15:43:51+00:00

    Hi

    Sorry for the extra chatter here in your thread. Thanks for letting me know what you tried.

    Am I correct that by downloading and running the 16.30 installer you have successfully installed 16.30? If so, then you should be OK, yes?

    The mystery remains as to why AutoUpdate could not download the complete packages from the Microsoft servers. Let's see what happens next month when 16.31 comes out.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-10-17T22:48:53+00:00

    Yes, nothing has changed:-(

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-10-17T22:26:50+00:00

    Jim,

    I assure you, this has not gone stale.  This is still very much an issue that all of us out here are waiting for Microsoft to fix.  Personally, I've been dealing with it for at least 2-3 years, manually downloading all updates.  It's quite frustrating, especially since it does not appear as though it's either being taken seriously, or addressed by Microsoft.

    Thanks,

    Greg

    Greg - have you installed 16.30 yet? if not, can you try the fix that Alex posted on this new message stream?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-10-17T22:25:42+00:00

    Kent - have you installed 16.30 yet? If not, can you try this suggestion from Alex?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-10-17T22:24:52+00:00

    Hi Michael,

    Really sorry to hear that the MAU issue still persisting on your Mac. In my last reply in the original thread, there was a promising workaround on this issue, please check if that method is working on your side when the next update is released.

    1.Click on check for updates to open the MAU.

    2.Go to Finder >Application >Utilities > Activity Monitor.

    3.Check if there is a process called "StandAloneUpdaterDaemon", if so, please terminate it.

    4.Go back to the MAU and try updating your Office application. 

    For the other users who have the same issue while using the MAU, although your issue symptom might be the same, but the root cause could be different, we would kindly suggest you raise a new thread in this community, and we will assign agents to help you narrow down and resolve the issue.

    Your understanding and cooperation is highly appreciated.

    Regards,

    Alex Chen

    Alex

    No I had missed that one. Sounds like it's worth trying.

    I'll see if I have time to delete my whole MS package and start over. I would have to install 16.28 (was that the one before 16.30?) so I'll need some time otherwise I will wait until the next update and try it then.

    Appreciate your bringing that up.

    Perhaps someone else on this discussion who hasn't installed 16.30 could try this and let us know?

    Was this answer helpful?

    0 comments