Windows 10: Proclaim keeps crashing immediately after opening

This started yesterday. I edited our Maundy Thursday service just fine but when I opened our template service from Easter Sunday last year to update it, the software crashed and closed itself. I tried re-opening it several times, but each time it will open for a few seconds and then close without letting me click on anything. I un-installed Proclaim; restarted and installed updates. I re-installed Proclaim. Same issue.
I updated the .NET framework as suggested in the help file. No luck.
I do not know which version of Proclaim I'm running since I can't access the Help menu (or any menu) in the software. I assume, however, that it's the latest since I downloaded it yesterday.
Attached are my Proclaim Log files.
Comments
-
Hello, Ginny --
I'm sorry for the frustrating experience.
Would you be able to depress the CTRL key and then try to start up Proclaim? Keep the CTRL key depressed until Proclaim is up and running.
If that doesn't allow you to start up, please call us at our Tech Support center: 888-634-2038.
0 -
Thanks, Brian! That seems to have done the trick! I was able to get Proclaim up and running last night. It still crashes when I open one specific template, but I can edit all of the others. I'll try get one of our other users to edit that template and will let you know if they run into the same issue.
Thanks!
0 -
Hello, Ginny --
I'm glad that got you moving forward. We would like to take a look at the one which is giving your team problems. If you would be so kind as to let us know which one that is, we could do some investigating on that...
You are always welcome to connect with us directly at 888-634-2038.
0 -
Thanks, Brian! It's the Template for Easter sunday that should have this Sunday's date (April 21) on it. If there is more than one recent Easter template, it is the one where the first slide is NOT a welcome screen. (The first slide is an Easter-related image but I can't remember exactly what and I'm not where I can log on to my computer right now. Sorry!)
Thanks for looking into this for us!
0