Adobe Crash Processor.exe locks files after exit

[5T0RMTR00PER]

Googling has not helped and, while there is one post in the Adobe Community that presents EXACTLY my same issue, there was no assistance provided (link: https://community.adobe.com/t5/photoshop-ecosystem-discussions/adobe-crash-processor-exe-doesn-t-sto...)

Every time I close Photoshop, I am unable to move or delete the file that I just closed. When I run PowerToys' File Locksmith, I can see the file is locked by Adobe Crash Processor.EXE. I end the Adobe Crash Processor.EXE process and my file is unlocked and can be manipulated. This happens EVERY time I close photoshop, even after ensuring I am updated to the most recent version.

Any assistance is appreciated. Thank you.

[Urraco37]

this  bug doesn't happen to me with all the files, but it's quite annoying when it happens...

until adobe offers a good solution, I use this:
- open Run Windows (win+r)
- resmon.exe
- Associated Handles / Search Handles ( insert path folder or folder name )
- Right click / End Process for Adobe Crash Processor.exe or AcroCEF.exe

[Shivani Somayajula]

Hey there, 

We're sorry for the trouble you're experiencing with Photoshop. We need more details. What version of Photoshop and Windows are you using? Did this ever happen with the previous version of Photoshop? Would you mind sharing a screenshot of the error?  

We do not see any submitted crash reports from you in our system. If you haven't done so already, please submit all Crash Reports along with your email address: https://adobe.ly/3CtVrd2 That will help us diagnose the crash. 

It may help if we could see your Photoshop System Info. Launch Photoshop, select Help >System Info and copy/paste the text into a reply.  

If you want to terminate the Adobe Crash Processor manually, you can do so by following these steps:

1. Click the Apple icon in the upper-left corner of your screen (for macOS) or right-click the taskbar and select Task Manager (for Windows).
2. In macOS, choose Force Quit and select Adobe Crash Daemon from the list. In Windows, find the process in the Task Manager under the Processes tab.
3. Select the process and click End Task (Windows) or Force Quit (macOS).

Let us know how it goes,

Thanks, 
Shivani 

[Bobby Childs Jr.]

This happens constantly with me as well, and has been happening consistently on every version of Photoshop on Windows 10 from 2023 forward. I already knew how to close the process manually, but found this post after a search for a more permanenet solution - a search which showed this has actually been reported numerous times. The processor is locking files when you open them and after closing them keeps their source folders from being manipulated until you manually kill the process; please produce a fix for this undesired and frustrating behavior.

This is the third set of files in a row: I open a TGA, perform an action, and then trying to move the folder when I'm done I get this until I close the crash processor:

[5T0RMTR00PER]

Admittedly, this is a TERRIBLE remedy but it does work: 

The next time this happens

1. Open Task Manager and right-click Adobe Crash Processor.EXE

2. Select "Go to file location."

3. End the Adobe Crash Processor.EXE process

4. Delete the Adobe Crash Processor.EXE file

This will work until Adobe pushes another update. Then you'll have to do it all again.

[CactusHacker13]

This happens for InDesign (February 2025) as well...

[Marc330270555mxk]

Hi Shivani,

this is not only a Photoshop problem but inDesign, too. This exists since many versions. And to end the task everytime I want to delete or change a folder is not a permanten solution. 

Please fix this asap. 

Thank you

[PeithmanS]

I have the same problem when using Adobe Acrobat. I have to use Windows "Locksmith" app to stop Crash Protector, after which I can delete or rename the file or folder.

[marco_2875]

I have the same problem with Photoshop and need to force close up to 4 Adobe Crash Processor processes everytime I want to delete a folder of files I used in PS. I guess you wold have to find out what crash exactly happens, but how do I know that?