Outlook 365 crashing on Server 2016

Anonymous
2025-01-13T01:48:03+00:00

Three terminal servers all with the same error today, all using Microsoft Office 365 and Server 2016:

“The required file react-native-win32.dll cannot be found in your path. Install Microsoft Outlook again.”

“Microsoft Outlook has stopped working”

“A problem caused the program to stop working correctly. Please close the program.”

A quick repair, a full repair, even uninstalling, rebooting and installing again didn’t fix the issue. On one server I uninstalled all of the recent security patches and rebooted, but no change.

I rolled it back to 5th December 2024 using the command below and it seems to be stable again:

cd %programfiles%\Common Files\Microsoft Shared\ClickToRun
officec2rclient.exe /update user updatetoversion=16.0.18227.20152

Outlook | Windows | Classic Outlook for Windows | For home

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 No comments

24 answers

Sort by: Most helpful
  1. Anonymous
    2025-01-13T09:18:06+00:00

    thank you was workin also for me

    cd %programfiles%\Common Files\Microsoft Shared\ClickToRun
    officec2rclient.exe /update user updatetoversion=16.0.18227.20152

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-01-13T20:34:57+00:00

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration]

    "UpdatesEnabled"="False"

    "O365ProPlusRetail.ExcludedApps"="groove,lync,onedrive,teams"

    Just wanted to point out that O365ProPlusRetail is just one type of MOLP based licensing, and may not be suitable for others who have different versions or bought their Office 365 through other distribution channels.

    For us we use "O365BusinessRetail" so ours shows as "O365BusinessRetail.ExcludedApps"

    Also the "ExcludedApps" removes those apps, which is helpful for a terminal server, it doesn't exclude them from not getting updates if they are installed (I'm just pointing this out because it could be interpreted differently).

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2025-01-13T14:46:26+00:00

    Hi

    THANK YOU!

    I had exactly the same issue today and all our reports on our SQL servers running on windows datacenter 2016 failed due to them relying on Excel sheduled tasks.

    We also rolled back office click2Run to Dec 5th and we are back up and running again.

    For reference you can also disable the office click to run autoupdate via this reg file, just save it with "true" or "false" if you wish to re-enable autoupdate for office 365.

    Windows Registry Editor Version 5.00


    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration]

    "UpdatesEnabled"="False"

    "O365ProPlusRetail.ExcludedApps"="groove,lync,onedrive,teams"

    Hope future updates get this fixed ASAP eh Microsharft?

    -dk

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2025-01-13T07:15:08+00:00

    Precisely the same circumstances here. Server 2016 acting as RD hosts and Office 365, this morning all Office apps crash with this error. Thanks for the rollback suggestion, need to give that a whirl as an emergency workaround. /Edit: No luck with that workaround. Blah.

    It seems likely it is the January 7 release that caused this, 2412 build 18324.20168, in my opinion. The dates should match up pretty well.

    Guess I'll try to roll back to December with the install tool and see how that goes.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2025-01-13T03:19:45+00:00

    Hello AlexLeadingEdge,

    Good day! Thank you for publishing in Microsoft Community. We are happy to assist you!

    Sincere apologies for any inconvenience this issue might be causing you. Based on the information you provided, I have consulted with my team members about your situation, and I would like to share some more specific directions with you. 

    Your current scenario must be diagnosed by the Microsoft Technical Support Team. Microsoft's back-end support team should check the advanced logs. A front-line technical support engineer can also have a specific support team investigate some specific situations further. 

    Due to the limited permissions and access resources of our forum moderators, we are unable to collect certain types of log information in public forums for this reason and for the privacy of our users' data. After diagnosing the situation, our technical support team can provide possible information from their point of view. 

    For the standard procedure information provided above, in your organization, Office 365 Global Admins may need to contact the Office 365 support team on the backend through an open service request so that they can diagnose this particular scenario with some more technical resources,  

    For this standard procedure, the following is the official documentation that Global Admins refer to: Get support - Microsoft 365 admin | Microsoft Learn (Online option). 

    You can also call MS support via - Global Customer Service phone numbers - Microsoft Support

    Note: If you are an end-user person, you may need to contact the Office 365 Global Administrator in your business organization to contact a Technical Support Engineer for further processing. 

    Important: If any of your organization's Office 365 Business/Business/Education subscriptions are from a federated partner or reseller and the global admin can't open a service request on their end, they may need to contact the reseller's support provider so they can help the global admin open the service request on their end. After that, the Office 365 support team will participate in the service request that was created. 

    Moreover, you may also post your query on Questions - Microsoft Q&A. This platform can provide valuable insights and solutions from a broader community familiar with Outlook's rendering quirks across different versions. Your engagement on Questions - Microsoft Q&A would greatly assist in finding a resolution to this issue.

    If you have any questions or need further assistance, please feel free to reach out to us. Thank you very much for your valuable time and your cooperation.

    Sincerely,

    Nafis Iqbal Shuvo

    Was this answer helpful?

    0 comments No comments