Bug 160052 - Since version 24.2 it is not possible to create new document in Windows
Summary: Since version 24.2 it is not possible to create new document in Windows
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
24.2.1.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-05 19:13 UTC by Siarhei Kuchuk
Modified: 2024-03-05 19:54 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 Siarhei Kuchuk 2024-03-05 19:13:00 UTC
Description:
Since version 24.2 it is not possible to create new document in Windows

Steps to Reproduce:
1. Open Explorer in folder
2. Open Context Menu \ File \ Create new document \ OpenDocument Text
3. Double click file
4. Try to type anything

Actual Results:
Not possible to type anything

Expected Results:
Possible to type


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: ru-RU
Calc: CL threaded
Comment 1 V Stuart Foote 2024-03-05 19:34:33 UTC
Integration with Windows Explorer is more a Windows registry issue.

Possible if you upgraded from 7.6 to 24.2

We'd need a verbose msiexec.exe /l*v log to even look at what did/didn't get touched. No way after the fact, so best approach at this time is to uninstall (appwiz.cpl from an admin enabled command line).

First Rename/Delete your user profile (C:\users\<yourUser>\AppData\Roaming\LibreOffice).

And then install again from scratch. GUI or command line msiexec (to catch a log).

Please report if that resolves issue for you. Or if you decide to go back around again, i.e. to install 7.6 then upgrade to 24.2 (but this time with a full log).

Absent that, this will likely be a "works for me" resolution.
Comment 2 Bogaboga Man 2024-03-05 19:45:17 UTC
(In reply to V Stuart Foote from comment #1)
> Integration with Windows Explorer is more a Windows registry issue.
> 
> Possible if you upgraded from 7.6 to 24.2
> 
> We'd need a verbose msiexec.exe /l*v log to even look at what did/didn't get
> touched. No way after the fact, so best approach at this time is to
> uninstall (appwiz.cpl from an admin enabled command line).
> 
> First Rename/Delete your user profile
> (C:\users\<yourUser>\AppData\Roaming\LibreOffice).
> 
> And then install again from scratch. GUI or command line msiexec (to catch a
> log).
> 
> Please report if that resolves issue for you. Or if you decide to go back
> around again, i.e. to install 7.6 then upgrade to 24.2 (but this time with a
> full log).
> 
> Absent that, this will likely be a "works for me" resolution.

Yup...works very well for me!
Comment 3 Siarhei Kuchuk 2024-03-05 19:54:46 UTC
> Integration with Windows Explorer is more a Windows registry issue.
Integration with Windows Explorer is done via Windows Registry. it's not an issue. Result of creating new document basically an empty file.

> Possible if you upgraded from 7.6 to 24.2
I upgraded from last previous released version to 24.2.

> We'd need a verbose msiexec.exe /l*v log to even look at what did/didn't get touched. No way after the fact, so best approach at this time is to uninstall (appwiz.cpl from an admin enabled command line).
I don't install updates. Kasperskiy Antivirus somehow does it in background and runs setup silently.

> First Rename/Delete your user profile (C:\users\<yourUser>\AppData\Roaming\LibreOffice).
After it, it's reproduced.

> And then install again from scratch. GUI or command line msiexec (to catch a log).
Installation from scratch solved the issue. I'm able to type now. Although I don't understand why it became broken after Kasperskiy updated it in the background. All previous times it worked flawlessly.

Thanks for your help.