Bug 165327 - LibreOffice does not start in Windows 11 Pro
Summary: LibreOffice does not start in Windows 11 Pro
Status: RESOLVED DUPLICATE of bug 165149
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
25.2.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-19 00:37 UTC by Goran
Modified: 2025-02-19 00:42 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 Goran 2025-02-19 00:37:22 UTC
Description:
Double click on any of shortcuts created by LibreOffice_25.2.0_Win_x86-64 Paket Windows Installer bring the following system error:
"""
soffice.bin
The code execution cannot proceed because
MSVCP140_ATOMIC_WAITdll was not found. Reinstalling the program may fix this problem
"""
But reinstalling the program did not fix the problem.

Steps to Reproduce:
1.Insall LibreOffice by LibreOffice_25.2.0_Win_x86-64 Paket Windows Installer
2.Double-click on any shortcut to start the program
3.Read the "Description" field and think for a few seconds how senseless is to insist on filling this field.

Actual Results:
System error:
"""
soffice.bin
The code execution cannot proceed because
MSVCP140_ATOMIC_WAITdll was not found. Reinstalling the program may fix this problem
"""
But reinstalling the program did not fix the problem.
Please, read the "Description" field and think for a few seconds how senseless is to insist on filling this field.

Expected Results:
I expect the program to start.
Please, read the "Description" field and think for a few seconds how senseless is to insist on filling this field.


Reproducible: Always


User Profile Reset: No

Additional Info:
Please, read the "Description" field and think for a few seconds how senseless is to insist on filling this field.
Comment 1 m_a_riosv 2025-02-19 00:42:13 UTC

*** This bug has been marked as a duplicate of bug 165149 ***