Bug 130059 - Since W10 Update KB4528760 LibreOffice starts only in safe mode
Summary: Since W10 Update KB4528760 LibreOffice starts only in safe mode
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.3.4 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-17 16:28 UTC by Manfred Peickert
Modified: 2020-01-18 13:58 UTC (History)
3 users (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 Manfred Peickert 2020-01-17 16:28:15 UTC
Description:
Since the W10 update KB4528760, every LibreOffice application only starts in safe mode. Even after reinstalling LibreOffice version 6.3.4.
How can this be fixed?

Steps to Reproduce:
1. W10 Update KB4528760
2. Start LibreOffice
3.

Actual Results:
all LibreOffice Aplikations can be stated only in safe mode-

Expected Results:
LibreOffice starts in normal mode when click on a file with opensorce extension.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
[Information automatically included from LibreOffice]
Locale: de
Module: safemode
[Information guessed from browser]
OS: Windows 10 Update KB4528760
OS is 64bit: yes
Comment 1 Roman Kuznetsov 2020-01-17 18:49:10 UTC
Manfred, can you delete/rename your user profile of LibreOffice and try retest that problem?

https://wiki.documentfoundation.org/UserProfile#Windows
Comment 2 V Stuart Foote 2020-01-17 22:56:17 UTC
Can not confirm.

On Windows 10 64-bit en-US (OS Build 18362.592) with
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 6095612850973388ba5b121b34d02292a2548e7d
CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win; 
Locale: en-US (en_US); UI-Language: en-US
Calc: CL

Have installed the MS KB4528760 security patch for this build of Windows 10.

Have no issue launching LibreOffice to StartCenter or directly to any of the LO modules.
Comment 3 Manfred Peickert 2020-01-18 13:48:16 UTC
After the second start of the PC everything went well. So it was obviously a Windows startup problem itself.
Many thanks to everyone who tried to help me.