Microsoft Auto Update gives "One or more updates package could not be downloaded" message

Alex - note here's someone else who may have the same issue.

STEVE

are you running Mojave 14.10.5 or 6?

if yes, then it appears you have the same symptoms as I currently have.

Yes - downloading from their server link works fine.

As I have stated previously in this thread, I have unsuccessfully tried:

• new user
• reinstall MACOS
• clear all MS files and reinstall
• SAFE MODE
• repair permissions from terminal

I have other macs in my home same config and OS but they update fine. So this is a single machine issue.

MS Support has been working with me and this server officecdn-microsoft-com.akamaized.net is the download server using by MAU but it seems to download fine when you just address it and download to your desktop.

In my experience, MAU goes to work to download new packages and that portion works but when it begins to "unpack" the files and place them into the Applications folder is when things go wrong as the error message indicates.

Hi,

I have the same issue but if I use another admin account (a new one I created) on my Mac they download and install fine.  I don't want to have to delete my profile and create a new one with all the grief that will entail with file permissions etc.

The MAU log has this

The error given is "'Error Domain=com.microsoft.autoupdate Code=500 "Failed to verify file signature" UserInfo={NSLocalizedDescription=Failed to verify file signature, NSLocalizedFailureReason=Either it is a mismatch of key or hash is incorrect}'

2019-07-18 13:02:30 [Microsoft AutoUpdate] <Error> DownloadTask.DownloadFailure: ID: 34DCE731-D142-4210-9CEC-D1B23B9AB81D, Details: { DownloadURL = "officecdn-microsoft-com.akamaized.net/pr/CXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/MacAutoupdate/Excel_16.26.19060901_to_16.27.19071500_Delta.pkg";

ErrorDomain = "com.microsoft.autoupdate";

I just tried copying and pasting the "https://officecdn-microsoft-com.akamaized.net/pr/CXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/MacAutoupdate/Excel_16.26.19060901_to_16.27.19071500_Delta.pkg". and it successfully dowloaded the package.

I replaced the key above with X's as unsure whether this code identified anything about me.

Hope this additional info helps.

Hi Michael,

I have make a summary on this issue, and I've send it to you via the Private Message.

To ensure I didn't miss any steps in it, please help me check it when you have time.

Much appreciate.

Regards,

Alex Chen

Alex

Thanks. As you may know, I have now developed the condition where MAU cannot show any updates so I'm dead in the water for testing until my next update.

This has happened for several updates now - spanning a number of months. I generally simply update by download the latest update from the MS website and just manually update which works fine. I did that this morning.

So now my software is all update to date, my MAU no longer says I need an update, and I'm stuck until the next update of Office when the problem will show up again.

Our status as of this date on this issue is:

• Network DNS and related issues - I believe we have eliminated that from the picture.
• Integrity of MS Office SW - I think by installing this several times we have eliminated this on my Mac and of course we also have other Macs in my house same config that auto-install fine.
• OSX - I have reinstalled MACOS several times with no changes.
• Interference with other applications (SAFE MODE startup eliminates that) and interference from firewalls or proxies - our VPN test bypasses anything like that and shows the same symptoms over VPN.

I would say that the problem is definitely on my single Mac and definitely an OSX issue - it's not a MS issue per se although it may be something unique about how MS is interacting with OSX in this one particular case.

As a side note, I had a similar issue with Adobe Creative Cloud - its a little like MAU for the whole Adobe suite of products - it would not update Acrobat - just one of many packages for download. The problem turned out to be a permissions problem on a root OSX file called "sudoers" that is mainly created by OSX but utilized during an Adobe update. I had hopes this would also correct this MS Office issue but it didn't. But it illustrates how interactions between OSX and MS OFFICE can cause problems especially on upgrades to Mojave.

Thanks for all your efforts. I will repost on this thread next update.