Bug 108148 - error 0xc000007b with Windows 10
Summary: error 0xc000007b with Windows 10
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.3.0.0.alpha1+
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsDevAdvice
Depends on:
Blocks:
 
Reported: 2017-05-27 07:13 UTC by guehenno
Modified: 2018-07-03 14:19 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 guehenno 2017-05-27 07:13:03 UTC
Hello
When launching LibreOffice I get the error message 0xc000007b.
I reinstalled windows, i reinstalled Redistributable Microsoft Visual C ++ 2015 Update 3 this operation unlocked nero burning room which had the same problem but freeoffice does not start
Do you have a solution to offer me
cordially
Comment 1 Buovjaga 2017-05-27 18:32:29 UTC
Which Windows are you using?

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.
Comment 2 Phil Nichols 2017-05-31 02:56:05 UTC
I'm having the same problem. Libreoffice x64 v5.3.3.2 installed on Win 10 pro x64 updated fully.
A 32bit x86 install works perfectly. When it is uninstalled and the x64 version installed, the windows startup error is:
"The application was unable to start correctly (0xc000007b)".
Attempting to start individual modules instead of soffice.exe didn't help.
The machine seems to be working flawlessly in all other respects, and no other apps generate this error. I have been unable to find a clue if a missing Visual C++ runtime is missing or perhaps something else.
Comment 3 Buovjaga 2017-05-31 14:27:20 UTC
Apparently you have to use this: http://www.dependencywalker.com/

"Use the Profile option to get diagnostics output of the load process. This will identify the point of failure and should guide you to a solution.

The most common cause of this error is trying to load a 64 bit DLL into a 32 bit process, or vice versa."

Source: https://stackoverflow.com/questions/10492037/the-application-was-unable-to-start-correctly-0xc000007b
Comment 4 Phil Nichols 2017-06-01 11:07:37 UTC
Solved for me by installing MS Visual C++ 2013 x64 runtime.

If there is a bug here, it may be that LIBO failed to emit a reasonably descriptive error message regarding a missing VC++ dependency.

Should LIBO x64 be expected to install the x64 VC++ runtime library if it is missing? If so, then it was failing to do so and perhaps that's the problem.
Comment 5 Xisco Faulí 2017-11-15 10:25:04 UTC
(In reply to Buovjaga from comment #3)
> Apparently you have to use this: http://www.dependencywalker.com/
> 
> "Use the Profile option to get diagnostics output of the load process. This
> will identify the point of failure and should guide you to a solution.
> 
> The most common cause of this error is trying to load a 64 bit DLL into a 32
> bit process, or vice versa."
> 
> Source:
> https://stackoverflow.com/questions/10492037/the-application-was-unable-to-
> start-correctly-0xc000007b

Dear Guehenno,
Are you sure you're loading the proper build images for your system architecture?
Could you please follow Buovjaga's comments?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' once you have retested it.
Comment 6 QA Administrators 2018-05-30 16:40:01 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2018-07-03 14:19:27 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20180703