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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-11-14T01:21:04+00:00

    Alex

    I finally found the process "StandAloneUpdaterDaemon" using Activity Monitor while running MAU 4.16 and trying to download/install 4.17.

    It was just sitting there with no apparent activity but it was running. I tried rerunning the MAU to see if it would show any activity but it didn't.

    I force quit it and then reran the MAU to see if it would come back active and it did not. 

    I quit MAU and restarted it but no change. I quit Activity Monitor and restarted no change.

    So I only saw the StandAloneUpdaterDaemon once and after I quit it I could never make it come back again.

    Even with it gone, my MAU still gets the same error as prior.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-11-11T16:15:02+00:00

    Jim

    i have been working on this problem for a year. Through Mojave and Catalina. I only have a Macbookpro - no exotic screens or other hardware.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-11-11T16:14:18+00:00

    Hi Jim,

    I know this isn't related to me, but the MacBook Air I am using is not, and has not, been ever connected to a monitor.

    Thanks

    Kent

    Was this answer helpful?

    0 comments
  4. Jim G 134K Reputation points MVP
    2019-11-11T15:57:54+00:00

    Hi Michael,

    I see lots of shooting in the dark replies and that the problem persists.

    A severe bug has surfaced with Catalina where multiple monitors and/or graphics cards is involved. By any chance does your Mac have multiple monitors and/or graphics cards?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-11-11T09:52:31+00:00

    Hi Michael,

    I have successfully received your log file.

    Actually, I have identify some same points from your log files with the other member, for instance:

    In your log document page 16, the error returned is exactly the same as TomStitt1 has provided in the original thread.

    Also, for the part error code 500 you mentioned, I think Greg is also facing the same issue, check his reply on Nov 7 in this thread.

    I will discuss this with our internal resources and keep you informed.

    @Kent, would be appreciate if you could also provide your MAU log file, please check if you could locate the log file in the folder below:

    ~/Library/Logs/Microsoft

    Regards,

    Alex Chen

    Was this answer helpful?

    0 comments