openlp returned-1 fatal error Windows 10 after windows update

[John-Paul Larson]

Widows 10 Pro 64 bit
Microsoft Office 2010

Cannot open program or debug program after using it for months there was a new windows update and a NVIDIA Geforce update inbetween function of program and non function.

Turned off reporting and found at least this information if it is any help.

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Windows\explorer.exe

Problem signature
Problem Event Name: AppHangB1
Application Name: explorer.exe
Application Version: 10.0.14393.0
Application Timestamp: 57899981
Hang Signature: d7b9
Hang Type: 134217984
Betriebsystemversion: 10.0.14393.2.0.0.256.48
Gebietsschema-ID: 1033
Additional Hang Signature 1: d7b9d45c1ea1f7ae1bab8b23c483a6de
Additional Hang Signature 2: 401c
Additional Hang Signature 3: 401c2e1a829a9a7f37640bd0077368ff
Additional Hang Signature 4: d7b9
Additional Hang Signature 5: d7b9d45c1ea1f7ae1bab8b23c483a6de
Additional Hang Signature 6: 401c
Additional Hang Signature 7: 401c2e1a829a9a7f37640bd0077368ff

Extra information about the problem
Bucket ID: 51044d83ece844c0299cd0e7a873fe4a (129168339806)

2016-10-11 13:35:40,267 openlp.core.common.registry INFO Registry Initialising
2016-10-11 13:35:40,268 openlp.core.utils.__init__ INFO Openlp version 2.4.3
2016-10-11 13:35:40,268 openlp.core.OpenLP DEBUG Entering is_already_running

[Tomas Groth (tomasgroth)]

If the log message is correct, then the crash happens after OpenLP detects that an instance of OpenLP is already running. Could that be the cause of the error?

[John-Paul Larson (1jpl)]

It is weird because there is no other instance of it running.

[John-Paul Larson (1jpl)]

if one tries to run(Debug) Openlp returned-1 fatal error also occurs.

[Tomas Groth (tomasgroth)]

I have a suggestion that _might_ work...

I think the problem might be caused by some setting issues, so to test it you will have to reset the settings. To do this, open the Registry Editor (go to Win10 startmenu and search for "regedit"). In the editor navigate to "HKEY_CURRENT_USER\SOFTWARE\OpenLP". Once there right-click "OpenLP" in the tree and chose to rename, and name it to "OpenLP-broken". Now close the registry editor and try to open OpenLP 2.4. Let me know how it works out!
If it does not help, you can go back into the Registry Editor and revert the renaming.

You also mentioned that some updates was installed right before OpenLP broke (NVIDIA). If so you could try to temporarily disable the NVIDIA driver. I don't know how that is done on windows though, but I'm sure that google knows :)

[Tomas Groth (tomasgroth)]

Did resetting/clearing the registry work?

[Arjan Klok (gkvbrouw)]

I had the same problem on 1-1-17, and yes, it worked.
After i did that, i had to go trugh first run wizard.
After that i needed to select the theme to standard again.

its not an easy fix, but it works.
you've got to know what you are doing...
and if i look at my church, i'm the onlyone who could do this. so if this whas happend when i was sick or away or something, that would be a problem.

Maybe there is an option to add to the installation wizard: "clean register".
So people could just download it form the website, and click on that option.

Long story short, yes it works, please try to make it easier.

[Launchpad Janitor (janitor)]

[Expired for OpenLP because there has been no activity for 60 days.]

[John-Paul Larson (1jpl)]

The strange thing is that there is only one version running. Currently it
opens and runs finally but always when I close it it returns an error twice
as if there is two versions running. Registry problem?

On Oct 15, 2016 9:10 PM, "Tomas Groth" <email address hidden> wrote:

> If the log message is correct, then the crash happens after OpenLP
> detects that an instance of OpenLP is already running. Could that be the
> cause of the error?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1632439
>
> Title:
> openlp returned-1 fatal error Windows 10 after windows update
>
> Status in OpenLP:
> New
>
> Bug description:
> Widows 10 Pro 64 bit
> Microsoft Office 2010
>
> Cannot open program or debug program after using it for months there
> was a new windows update and a NVIDIA Geforce update inbetween
> function of program and non function.
>
> Turned off reporting and found at least this information if it is any
> help.
>
> Description
> A problem caused this program to stop interacting with Windows.
> Faulting Application Path: C:\Windows\explorer.exe
>
> Problem signature
> Problem Event Name: AppHangB1
> Application Name: explorer.exe
> Application Version: 10.0.14393.0
> Application Timestamp: 57899981
> Hang Signature: d7b9
> Hang Type: 134217984
> Betriebsystemversion: 10.0.14393.2.0.0.256.48
> Gebietsschema-ID: 1033
> Additional Hang Signature 1: d7b9d45c1ea1f7ae1bab8b23c483a6de
> Additional Hang Signature 2: 401c
> Additional Hang Signature 3: 401c2e1a829a9a7f37640bd0077368ff
> Additional Hang Signature 4: d7b9
> Additional Hang Signature 5: d7b9d45c1ea1f7ae1bab8b23c483a6de
> Additional Hang Signature 6: 401c
> Additional Hang Signature 7: 401c2e1a829a9a7f37640bd0077368ff
>
> Extra information about the problem
> Bucket ID: 51044d83ece844c0299cd0e7a873fe4a (129168339806)
>
>
> 2016-10-11 13:35:40,267 openlp.core.common.registry
> INFO Registry Initialising
> 2016-10-11 13:35:40,268 openlp.core.utils.__init__
> INFO Openlp version 2.4.3
> 2016-10-11 13:35:40,268 openlp.core.OpenLP
> DEBUG Entering is_already_running
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openlp/+bug/1632439/+subscriptions
>