Forum Discussion

Markus851021's avatar
Markus851021
Copper Contributor
Oct 08, 2025

Office 365 Problems

Hello everyone,

I have been experiencing the following problem since today:
As soon as I try to open Excel, Word, Outlook, etc., they close again immediately.
Online repair and reinstallation did not improve the situation. 
Some of my colleagues are experiencing the same problem.
Background: We roll out updates at intervals. The users who were in the first interval are experiencing these problems.
The update interval has been stopped, but unfortunately I can no longer undo the update.
The following version is displayed: Version 2509 Build 16.0.19231.20138.
The computers are running Windows 11 with the 24H2 update.

Does anyone have the same problem or know a solution?

Thanks in advance.

1 Reply

  • Take a look at the following:

     

    1. Disable Hardware Graphics Acceleration

      • Open any Office app (if possible) → File → Options → Advanced → Scroll to “Display” → Check “Disable hardware graphics acceleration”.
      • If you can’t open the app, try this via registry:
    [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Graphics]
    "DisableHardwareAcceleration"=dword:00000001

     

    2. Run System File Checker

      • Open Command Prompt as Administrator and run:
    sfc /scannow

     

      • This will scan and repair corrupted system files.

    3. Check for Windows Updates

      • Make sure your system is fully updated. Sometimes Microsoft releases hotfixes shortly after problematic updates.

    4. Rollback Office Update

      • Run this command in an elevated Command Prompt to revert to a previous stable build:
    cd %programfiles%\Common Files\Microsoft Shared\ClickToRun
    officec2rclient.exe /update user updatetoversion=16.0.19231.20116

     

      • Then disable automatic updates temporarily to prevent reinstallation of the problematic build.

    5. Check Event Viewer

      • Look for crash logs under “Application” in Event Viewer. DLLs like d3d11.dll or react-native-win32.dll have been implicated in similar cases.

Resources