Description: LibreOffice apps crash at invoke. 1st draws window border, clears interior to white, then becomes a plain black pane interior, then window vanishes at 1st events inside the window. Event Viewer shows exception in C:\Windows\System32\ucrtbase.dll. Faulting application name: soffice.bin, version: 24.2.3.2, time stamp: 0x6631ee8e Faulting module name: ucrtbase.dll, version: 10.0.22621.3640, time stamp: 0x10c46e71 Exception code: 0xc0000409 Fault offset: 0x000000000007f6fe Faulting process id: 0x0x39BC Faulting application start time: 0x0x1DABE0224C15904 Faulting application path: D:\PgmFiles\wnt-x64\LibreOffice\24\program\soffice.bin Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Since the soffice.exe PE-COFF guts does not DIRECTLY specify a need for ucrtbase.dll, I assume some other loaded .dll is requesting it, probably by full pathname. These latest builds of Windows have a newer version of ucrtbase.dll than historical builds. The only machine I have with Windows 11 is this one with Insider program beta, and is up-to-date. Steps to Reproduce: 1.Begin with Windows 11 "Insider" beta running on an x86_64 machine 2.Install LibreOffice ver. 24.2.3.2 3.Click on LibreOffice icon to start soffice.exe 4.App will draw initial window frame, clear interior and crash after screen is redrawn in black Actual Results: App draws initial window border, clears to white, then black then crashes and leaves screen, leaving and Event Viewer Application Crash Expected Results: soffice.exe should have completed drawing its GUI features and the icons of recent documents Reproducible: Always User Profile Reset: No Additional Info: Help - About LibreOffice not available; app crashes before drawing any GUI or menu elements
No MSFT apps seem to have this problem, nor other 3rd party apps (like Google chrome or Mozilla Firefox). Is there a way to find if some LibreOffice settings are causing this that I can try out with iterative change attempts?
First upgrade to LO 24.2.4 then apply https://wiki.documentfoundation.org/QA/FirstSteps. If you still reproduce this, a backtrace would be useful (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace)
Thanks for your suggestion. A complete un-install of 24.2.3... reboot, then installation of 24.2.4..., then reboot, has fixed the problem. (I had not seen that a 24.2.4... was available, or I'd have tried that 1st.) Note: that I also had forced upon me an update from Microsoft at this same time - along with the 1st reboot mentioned. Heaven knows what that might have fixed also. Sigh...
Thank you for your feedback. Let's rather put this one to WFM then since there was no fix per se.