Bug 158775 - Critical Update for Windows 10 Version 22H2 KB4023057 causes LibreOffice stops to work
Summary: Critical Update for Windows 10 Version 22H2 KB4023057 causes LibreOffice stop...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
7.6.2.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-19 12:39 UTC by Orwel
Modified: 2023-12-19 18:36 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Orwel 2023-12-19 12:39:38 UTC
Description:
After few days of investigation why LibreOffice hangs on starting, I wound out that the problem is caused by Critical Update for Windows 10 Version 22H2 KB4023057 (26. 10. 2023).
Before installing this update, everything works fine.
After installing it, LibreOffice stops to opening documents and freeze.
I tried also similar descriptions to solve the problem (like here: https://ask.libreoffice.org/t/libreoffice-7-1-dont-work-after-windows-update/62412), but it does not help.
Description of the behaviour is bellow.

Steps to Reproduce:
1. Everything works fine with installed LO 7.6.2.1
2. Installing Windows update KB4023057 
3. Trying to open a LO document (.odt, .ods) makes LO freeze.

Additional info: LO start ok, if you start it with the LO icon, but also freeze, if you try to open a document (does not matter if from Windows Explorer or from Open in Menu of LO)

Actual Results:
LO freeze.

Expected Results:
LO works.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
I had investigated thiss issue by using a system backup and trying to update all apps and Windows updates step by step. I found out the KB4023057 makes LO freezing, no other update.


Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: sk-SK (sk_SK); UI: en-GB
Calc: threaded
winver: Version 22HS (OS Build 19045.2965).

As I understand it is probably a Microsoft bug, as the KB4023057 is described as CRITICAL UPDATE, I think, the LO community should know about the problem as in my PC is LO not usable, if installing this update.

I also tried to reinstall LO, tried to install older version also, nothing helps. If KB4023057 is installed, LO freezes by opening document.
Comment 1 V Stuart Foote 2023-12-19 13:28:47 UTC
Hmm, can't confirm. That MS patch from Feb 2023 has been widely in use with no other reports. Shows in the MS AppWiz as "Microsoft Update Health Tools" ver. 3.74.0.0

For OP have you launched LO with a clean User profile (rename %APPDATA%/LibreOffice), or launched with LO in SafeMode?

Alternatively if you have nothing of value in your LO profile (customizations, templates, etc.) just fully uninstall LibreOffice, delete your profile, restart Windows and do a clean install.
Comment 2 Orwel 2023-12-19 18:36:49 UTC
Hi, thank you for the answer. My Windows shows me for this patch a date of 26. 10. 2023, not February. It is shown on my system as:
20232-10 Update for Windows 10 Version 22HS x64-based System (KB4023057) and is shown as Critical Update.

Regarding your question:
Yes, I tried all mentioned procedures, indeed. Also, what was described at the link I mentioned above, also with new user profile and fresh install of LO.

But after your answer, I tried to insert some restarts, so I used these steps, which worked:
1. install and update everything on the PC unless the mentioned patch. 
2. restart PC,
3. fully uninstall od LO (Control panel/Programs and features)
4. restart PC, 
5. install the MS Patch KB4023057, 
6. restart PC, 
7. install fresh LO with (also with a new profile, I deleted the previous one). 
And now, LO is working.
I have also in step 8. recover my old profile and it still works.
Interesting....beside the restarts, the only one thing which was different was, that no LO was installed when installing the patch.

Nevertheless, many thanks for answering and bringing me to the last try, which helped.