Elements 14: Keeps crashing on startup; "A problem caused the program to stop working correctly"

  • 1
  • Question
  • Updated 4 weeks ago
  • (Edited)
Just upgraded to Windows 10 Home, version 1709, build 16299.64. Since updating, PSE 14 keeps crashing on startup; "A problemm caused the program to stop working correctly" I removed and reinstalled, keep getting same error. Please help.
Photo of Rob Owsiany

Rob Owsiany

  • 2 Posts
  • 0 Reply Likes

Posted 3 months ago

  • 1
Photo of Steve Lehman

Steve Lehman

  • 479 Posts
  • 52 Reply Likes
Rob, 

This can happen whenever you upgrade and Windows 10 does a full update, then right off, it makes your apps do things like this.   So, let's try to reset your PSE14 in Windows 10.  Go to Settings, System, Apps and Features, and highlight your PSE program (on the right) that you're having this problem, and see if there is a blue-hypertext link under its highlight.  If so, click on it, and on the left is a reset button.   And that's it.  

If not we'll go to the Windows Power Shell to reset it from there.  Launch the Windows Power Shell from your Programs list (under the Windows icon on the far left) it's listed under the W's for Windows Power Shell, and when it opens, it'll open in a DOS windows.  At its current cursor, type scannow and press enter.  Let it work a while, then let it find any errors.  It probably won't find any but at least your programs might be reset by doing this.   That's all I have for now.   

Steve Lehman Windows MCSE   
Photo of Rob Owsiany

Rob Owsiany

  • 2 Posts
  • 0 Reply Likes
After installing another Windows update, PSE 14 will now start, but now when I try to open a file or work on a photo, the mouse lags way behind and jumps around.  I could not run scannow, even as an administrator, but Windows said it was command was now recognized.
(Edited)
Photo of Steve Lehman

Steve Lehman

  • 479 Posts
  • 52 Reply Likes
I have not had this problem before this.   The scannow needs to be run.   Otherwise, it won't reset.  Another reset in the tools in Windows 14 might do the same type of reset or close, in the program itself.   In PSE14, load an image (if you can) then on the lower right corner near the ? is a down-menu.  In that menu is "reset all tools" which may reset the entire program.  It should work right away but if not, reboot the program.  But the scannow needs to be run if that does not reset it.  Then reboot Windows.   It it's not working for you, reboot Windows first before doing the scannow reset.     
Photo of Steve Lehman

Steve Lehman

  • 479 Posts
  • 52 Reply Likes
Rob, the "scannow" command can  only be recognized in the Windows Power Shell.  Did you open that?  It should open a DOS window and where the blinking cursor is, is where you type scannow then press enter.  It will recognize it there.   The Windows Power Shell is located in the list of programs at the Windows icon on your lower-left corner.  Click on all programs, and it should be listed there at the bottom in the w's fore Windows Power Shell.  Open that and type scannow at the blinking cursor then press enter and reset your Windows so your app will run.  ok?    
Photo of Grace3

Grace3

  • 6 Posts
  • 1 Reply Like
Yes, I used Windows Power Shell & copied exactly what came back several times onto my last comment.  No AOL--- ACK!!!!! Ok, I will try the uninstall-reinstall & post what happens. Thank you for your help, I really appreciate it
Photo of Grace3

Grace3

  • 6 Posts
  • 1 Reply Like
I uninstalled PSE 15, rebooted computer, reinstalled PSE 15. Tried scannow in Windows Powershell & got this:
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\Users\grace> scannow
scannow : The term 'scannow' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ scannow
+ ~~~~~~~
    + CategoryInfo          : ObjectNotFound: (scannow:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

PS C:\Users\grace>

***************************************************************************
Not easily being deterred, I uninstalled PSE15 completely, rebooted, & installed PSE 2018. But got the same message again. "Windows found a problem" with PSE 2018 & shut it down immediately. I also did check and the problem is NOT my PSE catalog. Both the catalog in PSE15 & the new one in PSE 2018 show no errors & look fine, if I could just get Windows 10 to stop shutting it down every time I start PSE.
Photo of Steve Lehman

Steve Lehman

  • 479 Posts
  • 52 Reply Likes
Grace,

The reason it doesn't find scannow as anything is because you are using it as a user name after the C prompt.   Even in the Windows Power Shell, it wouldn't have a user name in that window as it resets its Windows but not as a user name.  Scannow is a command that is used in the Windows Power Shell that resets Windows (only), and the Windows Power Shell will open in a smaller DOS window which has a black background.  Does that sound familiar to you?  

And then, this prompts me to wonder if you did install your program correctly.  No matter what, Windows 10 should be recognizing it as a program.  Are you sure you have it install in the programs folders?  It's not installed along with another program is it?   

You may need to take this to a technician in your area and have him watch how you install your program or having him do that for you.   Your PSE should be working perfectly in Windows 10.   In fact, even if it didn't, Windows 10 should be fixing it for you and if it is not, then you don't have it installed correctly.   
Photo of Steve Lehman

Steve Lehman

  • 479 Posts
  • 52 Reply Likes
Grace,

Disregard my last note.   Scanow does come after a user name although it needs to be the administrator, and I trust you are that person.   I know you are inside the Windows Power Shell because the word, cmdlet is a code used.   I don't know why scannow is not working, but more importantly, Windows is shutting down your program.   I'd like you to take it to a technician in your locale and have him reinstall your program.   I want a technician to watch your screen for this.   If Windows is shutting down PSE then it may not be installing in the correct folder.     
Photo of Grace3

Grace3

  • 6 Posts
  • 1 Reply Like
Turned out my user account was corrupt. MS tech support created a new user account and copied over my old info. Of course, they didn't take into account that this would zombie ALL my programs which were installed under a different folder structure!

Scannow needed to have SFC in front of it. Figured that out via googling. Ran it & it found no problems. All my Adobe programs are installed in the correct folder & I don't use browser installation.

In this whole process I upgraded to PSE /PRE 2018. I had to convert my catalog twice. Now it lets me go into Organizer, but crashes when it tries to reconnect files & won't let me type in the new file structure to help it out. Sigh.