Editor will not launch

Merry Christmas to everyone.
I just started having problems with lightroom 5. It seems that when i work on a image and go to export it into elements 13 i get a box that says "The file could not be edited
because photoshop elements editor could not be launched ". The thing is it takes about 2 to 3 minutes for the box to come up then if you click on the ok button it opens in elements
any how. I did a google search and from what i have found this has been going on for a number of years but after using the software since it came out and just started having
problems. My question is there any way that i can fix this as it takes forever to edit pictures the way it runs now. Thank you in advance for any help.

If it previously worked and now it doesn't it must be down to one of two things...
1. You changed a setting or installed something that is causing the problem
2. Something became corrupted, causing the two packages to have trouble communicating.

If you have a system restore point from before the problem occurred that should solve either problem. If not I would suggest starting by uninstalling both packages and then reinstalling.

Thanks Dan i have windows 10 and it just updated and i have nothing but problems so i reset and did a recovery back to windows 8 not sure what is causing the problem as i have
not added any new software for a long time.

lonerider519 wrote in post #17827208
....My question is there any way that i can fix this as it takes forever to edit pictures the way it runs now. Thank you in advance for any help.

Couldn't you just export to a folder, then open your editor (not through LR) to access the file? That's what I do all the time.

teekay wrote in post #17829110
Couldn't you just export to a folder, then open your editor (not through LR) to access the file? That's what I do all the time.

That is what I would do also. The only advantage to "Edit in ..." is that the rendered RGB tiff is put in the same folder as the Raw original, automatically added to the LR catalog, and LR's preview is automatically updated when you save the tiff in PS. I think you could a accomplish the same by designating the export folder as a "watched folder".

Personally, I very rarely want rendered images added to my LR catalog - generally, only if I intend to print from LR to my Epson; usually a visit to PS is the last stop in the workflow for cleaning up heals/clones that LR didn't do well and creative/output sharpening in the Focus Magic plugin followed by the writing of a jpg that is then sent off and deleted. For this reason I prefer to use the "Open as Smart Object" option toward the bottom of the "Edit in" menu.

I had that problem with photoshop elements and Windows 10. It eventually started working again after I subscribed to CC. The most common fix is to close everything Adobe using task manager and update the Microsoft C++ 2010 redistributable. That didn't work for me but it may for you.

I never reverted and I'm not sure how that affects the repair process.

I had a similar problem with exporting from LR to PS after upgrading to win 10.
Win 10 had turned on graphics acceleration when it updated the drivers.
LR froze and PS would not open the file.Have a look at Edit>preferences>performance and see if use graphics processor is turned on , if it is turn it off, that solved my problem

lonerider519 wrote in post #17828773
Thanks Dan i have windows 10 and it just updated and i have nothing but problems so i reset and did a recovery back to windows 8 not sure what is causing the problem as i have
not added any new software for a long time.

Similar thing happened to me. I UPDATED from windows 7 to 10 and it killed everything. EVERY adobe product now crawls and is almost unusable. Even after reinstalling the adobe products and updating all drivers. It's too late for you and I, but spread the word, DONT UPDATE TO WINDOWS 10. It seems to be fine for people who have done a clean install of it or bought a computer with it already on it. There are more and more stories of people updating having issues. I read somewhere (can't remember the site) that said there is some issue with Windows 10 updating where it won't utilized all of the RAM properly. I'm sure there are other issues. Just wish they would fix it!

Anyway. Sorry about your situation. I have no advice other than to reinstall your programs and update drivers.

BlakeC wrote in post #17829546
Similar thing happened to me. I UPDATED from windows 7 to 10 and it killed everything. EVERY adobe product now crawls and is almost unusable. Even after reinstalling the adobe products and updating all drivers. It's too late for you and I, but spread the word, DONT UPDATE TO WINDOWS 10. It seems to be fine for people who have done a clean install of it or bought a computer with it already on it. There are more and more stories of people updating having issues. I read somewhere (can't remember the site) that said there is some issue with Windows 10 updating where it won't utilized all of the RAM properly. I'm sure there are other issues. Just wish they would fix it!

And I upgraded from Windows 8 to 10 when it was first available (end of July IIRC), not clean install - on top of Win 8, accepted every update since then and it performs like a champ. CPU is i7-4720, 16 GB Ram, SSD drive and LR 6.3 with GPU usage enabled (Nvidia GTX 960M) flies, even with lots of clones and brush/local filter adjustments on the image. Using Edit In, writing to disk a 16 bit 21 MP (~120 MB) tiff and cataloging it plus launching pixel editor (PSE 12, Topaz apps, OnOne 9 Suite) and opening the tiff, takes 5 seconds. With four or five apps open at the same time, Windows 10 has no problem using all the installed memory before dipping deeply into the virtual.

YMMV

tzalman wrote in post #17829640
And I upgraded from Windows 8 to 10 when it was first available (end of July IIRC), not clean install - on top of Win 8, accepted every update since then and it performs like a champ. CPU is i7-4720, 16 GB Ram, SSD drive and LR 6.3 with GPU usage enabled (Nvidia GTX 960M) flies, even with lots of clones and brush/local filter adjustments on the image. Using Edit In, writing to disk a 16 bit 21 MP (~120 MB) tiff and cataloging it plus launching pixel editor (PSE 12, Topaz apps, OnOne 9 Suite) and opening the tiff, takes 5 seconds. With four or five apps open at the same time, Windows 10 has no problem using all the installed memory before dipping deeply into the virtual.

YMMV

Yes for YOU... But like I said... there are more and more people having issues with the upgrade. I didn't say YOU or EVERYONE has an issue. Had I heard the stories before hand, I would not have upgraded. There was no reason for me to upgrade when everything was running lightning fast on my i7, 16gb ram, Adobe CC , Samsung 850 EVO SSD 500gb. I thought, "O cool I will try the new OS!" Now it runs like a sh*t.

What do you have to gain by upgrading from a perfectly fine OS? What do you have to lose by upgrading if you happen to be one of the unfortunate ones that has issues? If your current OS runs fine and performs well, don't upgrade. Not worth the risk IMO.

tzalman wrote in post #17829640
And I upgraded from Windows 8 to 10 when it was first available (end of July IIRC), not clean install - on top of Win 8, accepted every update since then and it performs like a champ. CPU is i7-4720, 16 GB Ram, SSD drive and LR 6.3 with GPU usage enabled (Nvidia GTX 960M) flies, even with lots of clones and brush/local filter adjustments on the image. Using Edit In, writing to disk a 16 bit 21 MP (~120 MB) tiff and cataloging it plus launching pixel editor (PSE 12, Topaz apps, OnOne 9 Suite) and opening the tiff, takes 5 seconds. With four or five apps open at the same time, Windows 10 has no problem using all the installed memory before dipping deeply into the virtual.

YMMV

That is most interesting, I am running a similarly specced system with the exception of the graphics card ( AMD Radeon 5400) which is a far lower spec than your Nvidia it does make me wonder if the "standard" graphics card is up to the job in win 10

Thanks to everyone i find if i wait for about 2 to 3 minutes the box pops up then when you click on it the editor goes into elements anyhow. In the beginning windows 10 worked well and slowly as more and more updates showed up the systems on my laptop and desktop started to screw up more and more.

I fixed my issue! Or, should I say, NVidia fixed it. NVidia released new drivers for the GTX 560M on 2-15-16. So, if anyone has an NVidia card, go to the NVidia site and update your drivers. This is why you should never hop on the band wagon on launch day of major new software like an OS. Everything else needs time to catch up to become compatible with it. I usually wait a year and I should've waited but everything is good now.... I hope