Check your MSI logs (if you haven't enabled MSI logging - do so) / return codes.
Start from there .
The distribution package is using a Bat file. Not sure how to enable MSI logging.
OK - so for a batch file, first up, I'd HIGHLY recommend to make sure you've read this thing here:
How to enable MSI logging is very simple - it's just a command line switch for the MSI and quite google-able .
Here's a few things to look at for instance:
That should give you a head-start.
Batch-file based exit codes can be quite a bit of a red herring at times (depending on how well or badly the batch-file in question handles passing on exit codes). Since Office tends to be an MSI at heart, getting "the truth" of what's actually happening.
Equally, potentially enabling debug-logging on our side may get you a bit more information which step fails in your batch (careful, that makes our logs a *LOT* more chatty, which is the point). Steps on how to do that are included here -- How to enable Xtrace Diagnostic Logging -- .