Deployed O365 applications crash on start

Anonymous
2017-03-02T22:43:54+00:00

Hello all,

We're pushing out O365 this weekend to about 65 computers. We'd like to avoid having each one stream the download and install, but given some trouble we're having with the ODT that might be our only option. I used XML script editor to configure a new XML for deployment. It looks like this:

<Configuration>

    <Add OfficeClientEdition="32" Channel="Current" SourcePath="\fsstl06\DataDir\Installs\Software Distribution\Office_2016_365" OfficeMgmtCOM="TRUE">

        <Product ID="O365BusinessRetail">

            <Language ID="en-us"/>

        </Product>

    </Add>

    <Display Level="Full" AcceptEULA="TRUE"/>

    <Logging Level="Standard" Path="\fsstl06\DataDir\Installs\Software Distribution\Office_2016_365\Logging"/>

</Configuration>

Since display is on Full for now, I can say it gives us no error messages. I do have a log, and it looks okay, but I have no idea what to look for besides the word "failure" (which I saw none). So it installs fine, but when we open any application, it crashes and asks us to Close. If we ignore that, you can use Word and Excel in the background just fine. Obviously this won't work, but it makes me think the applications are okay. Also - we're not being prompted to activate or sign in to our O365 accounts that we have for our staff. What are we missing?

*Each computer had a VL Office version on it, but we removed it. Even tried running the Office removal FixIt tool just in case. It made no difference. I'm building up a fresh PC right now to try out, but that won't help much since all staff computers cannot be rebuilt for this.

Microsoft 365 and Office | Subscription, account, billing | 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
Answer accepted by question author
Anonymous
2017-05-14T09:08:08+00:00

Hi Jeremy,

Thanks for your updates. Please try the steps below and see if the issue can be fixed.

  1. Since the Office apps can be opened in Safe Mode, you can try disabling all the add-ins (e.g. for Word) and try to launch Word again.

HKEY_CURRENT_USER\Software\Microsoft\Office\application name\Addins\add-in ID

For each Add-in, there will be a key named “LoadBehavior”. Please kindly set it to “0” for every add-in to disable it from automatically being loaded when launching Office.

Then please try to launch the Word again to see if the crash happens again.

  1. Disable the Hardware Graphics Acceleration and then try again:

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common

Create a new value called “DisableHardwareAcceleration” and set it to “1”:

  1. If still crashed, please kindly add this registry key to check:

HKEY_CURRENT_USER\software\policies\microsoft\office\16.0\common\internet

Create a new value called “useonlinecontent” and set it to “0”:

Please let us know if you have any updates.

Regards,

Spike

Was this answer helpful?

0 comments

51 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-05-25T09:34:20+00:00

    Hi Jeremy,

    You can let us know the update when you are free.

    Thanks,

    Jim

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-07-21T20:00:59+00:00

    Just ran across this thread.  Not sure if you ever resolved your issue or not, but we experienced the exact same problem.  All office applications would crash immediately after installing Office 365. Error messages indicated mso20win32client.dll as the faulting module, not prompted to activate, etc...  This was occurring even on clean OS and Office installations, so Add-Ins were never an issue.

    Well.. after scratching my head for an hour and trying different fixes it finally hit me...

    We do not allow the use of OneDrive or any other remote storage features so we have GPO's in place to lock down some of these types of features in Office.  We are new to Office 365 moving from the old standard Office 2013/2016 installations, so we had existing GPO's in place to prevent some of the remote access/storage features.

    Well, like us, I'm willing to bet you have the following GPO set to Disabled:

    User Configuration -> Administrative Templates -> Microsoft Office 2016 -> Miscellaneous -> Block signing into office

    I changed it to Enabled (and in our case we also opted for Org ID only), ran GPUpdate /force on the machines and the problem instantly went away.

    Makes sense as Office 365 needs to allow a sign in to activate.

    Hope this helps someone else experiencing the same issues.

    -Brian

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2017-07-21T22:24:11+00:00

    Brian - 

    Thanks for posting this.  We came to the same conclusion about a week ago, but I forgot to come back here and post the results.

    We can confirm this worked for us and allowed the O365 applications to finally launch and successfully activate.

    Was this answer helpful?

    0 comments