https://bugs.documentfoundation.org/show_bug.cgi?id=174004

            Bug ID: 174004
           Summary: LibreOffice completely fails to launch (infinite
                    loading/hourglass briefly flashes then vanishes) after
                    recent Windows 11 update; only Portable version works.
           Product: LibreOffice
           Version: 26.8.1.1 release
          Hardware: x86-64 (AMD64)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: LibreOffice
          Assignee: [email protected]
          Reporter: [email protected]

Description:
[Environment]
- OS: Windows 11 (Latest Update)
- LibreOffice Version: Latest stable installer (x64)
- Antivirus: Kaspersky Standard (confirmed no blocks/quarantine logs)

[Current Symptoms]
After the recent Windows 11 update, LibreOffice (installed version) has become
completely unresponsive. 
1. Clicking on any shortcut (including LibreOffice Calc, Writer, Impress, or
even "Safe Mode") results in the mouse cursor turning into an hourglass for a
brief second, then disappearing. Nothing else happens. No error messages or
codes are shown.
2. Checking the Task Manager shows that 'soffice.bin' or 'soffice.exe' is
terminated instantly upon execution.
3. The CMD command `soffice.exe --safe-mode --norestore` also exits instantly
without any output or error logs.

[Steps Already Attempted (Failed to fix)]:
- Ran LibreOffice installer to "Repair" the installation.
- Completely uninstalled LibreOffice and reinstalled the latest version.
- Completely deleted the user profile folder in `%appdata%\LibreOffice`.
- Temporarily disabled Windows Defender's "Controlled folder access".
- Added LibreOffice execution paths to Kaspersky's trusted exclusions.

[Workaround Found]:
The LibreOffice Portable version works flawlessly. It can open .xlsx files and
launch all components without any issues on the exact same Windows 11 system. 

[Conclusion]:
This indicates the issue is not with the software files themselves, but rather
a catastrophic conflict introduced by the Windows 11 update regarding registry
entries, DLL path loading, or system-level permission handling specifically
tied to the default C:\Program Files installation path. Please investigate.


Steps to Reproduce:
1.Please see the description above.
2.
3.

Actual Results:
Please see the description above.

Expected Results:
Please see the description above.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
NONE

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to