Skip to main content
vikingd
Participating Frequently
July 14, 2026
Question

Photoshop not releasing a folder after a save-as

  • July 14, 2026
  • 3 replies
  • 26 views

Issue: Photoshop not releasing a folder after a save-as
Photoshop version: Adobe Photoshop Version: 27.8.0 20260610.r.13 4081857  x64 (final, Release)
OS and version: Windows 11 Pro, 23H2, 22631.3007

Issue: steps to reproduce the behavior:
- Open any document
- do a Save-as
- close document

Expected result:
- Able to move containing colder after file closed

Actual result:
- Parent directory remains open
- Handle migrates between Photoshop.exe, node.exe, and Adobe Crash Processor
- Prevents moving completed job folders until Adobe eventually releases the handle
- Mostly releases the handle after next Save-as or Photoshop is closed unless Adobe Crash Processor takes the handle
- Killing Adobe Crash Processor sometimes moves the handle back to Photoshop

Extra info:
- Process Explorer and Handle64 confirm the handle is on the folder, not just the fine itself
- No third-party plug-ins required
- External NTFS 5400 RPM drive almost every time
- Occurs intermittently on internal M2 SSD
- No third-party plug-ins required
- Disabling plugins has no effect on the process
- External is also the scratch disk; however, changing this doesn't effect the result

My production workflow processes hundreds of image folders. After saving and closing a document, the completed folder is immediately moved to a 'done' folder. Photoshop's retained directory handle prevents this workflow.

    3 replies

    vikingd
    vikingdAuthor
    Participating Frequently
    July 15, 2026

    another interesting thing i just notied too is if i save-as but replace a file that’s already there it the handle is still with the previous folder and not that current one. 

    Anshul_Saini
    Community Manager
    Community Manager
    July 15, 2026

    Thanks for the additional testing. Could you please share:

    • Photoshop System Info (Help > System Info > Copy and paste it here).
    • A screen recording showing the Save As workflow along with Process Explorer/Handle64, if possible, so we can see when the folder handle changes ownership.
    • Can you also confirm whether this is reproducible only when using Save As > TIFF, or do you see the same behavior with other formats such as PSB or PS PDF?
    • Also, have you tried using File > Save a Copy instead of Save As when saving to TIFF? If so, does it exhibit the same folder handle behavior, or does the folder release normally after closing the document?

    I’ll share these details with the product team for further investigation.

    Best,
    Anshul Saini

    vikingd
    vikingdAuthor
    Participating Frequently
    July 15, 2026

    Thank you

    - preferences I already had save in background and auto save disabled- 
    - crash processor disabled
    - the REG was already in there set to 0

    tried again and the folder is still not releasing but bouncing etween just photoshop and node. 

    more details:
    - they are PSD files i’m opening so save as compressed tifs
    - recent files set to 0, clearing the list didn’t release the folder
    - Drive is connected with USB 3.2

    Test 1:
    - opened psd from folder 1
    - save-as tiff
    - closed file
    -> folder doesn't release and handle reports open with photoshop and node

    - folder 2 - open/save-as/close
    -> both folders aren't released
       - folder 1 handle -> held by node
       - folder 2 handle -> held by photoshop

    quitting photoshop released both folders

    Test 2:
    - folder 1 - open/save-as/close
    -> folder doesn't release and handle reports open with photoshop and node

    - folder 2 - open/save-as/close
    -> both folders aren't released
       - folder 1 handle -> held by node
       - folder 2 handle -> held by photoshop

    - folder 3 - open/save-as/close
    -> folder 3 and folder 1 aren't released
       - folder 1 handle -> held by node
       - folder 3 handle -> held by photoshop

    Extra info:
    - a plain save doesn't do this and opening a file and save-as to that same format appears to not lock the folder.
    - It's also just the folder; i can move files as normal inside the locked folder.
    - It appears to be tied to save-as to a different format, mostly tiff
    - Happens almost always opening a psd and save-as to a tiff
    - Happens with RAW images too but not as often as psd
    - killing the node process the handle goes back to photoshop; example Test 2 folder 1 went back to photoshop from node

    I dont think it's related to the general save pipeline. appears to be linked to the save-as

    any other info that would help please let me know

    Anshul_Saini
    Community Manager
    Community Manager
    July 14, 2026

    Hi ​@vikingd,

    Thank you for reaching out. Based on what you've described, here are a couple of things to try that may provide a workaround:

    1. Go to Edit > Preferences > File Handling and uncheck "Automatically Save Recovery Information Every [X] Minutes. Also, uncheck "Save in background."

    1. Disable Adobe Crash Processor. If the handle is no longer retained after this change, it confirms the crash processor's file-watch is the culprit.
       

    • Open Start

    • Search for "Command Prompt" and launch it

    • Enter the following command:

    • REG ADD HKEY_CURRENT_USER\Software\Adobe\CommonFiles\CRLog /v "Never Ask" /t REG_SZ /d 0

    • Press the Enter key

    • If asked, "Value Never Ask exists, overwrite (Yes/No)?" Choose No.
       

    If those steps don't help, a few more details would help us narrow it down:

    • Are you saving as PSD, PSB, TIFF, JPEG, or another format? Does the issue happen with all formats or only specific ones?

    • Do you have File > Open Recent enabled? Photoshop's recent file tracking holds directory references; clearing the list (Edit > Preferences > File Handling > Recent File List Contains: 0) might release the hold.

    • For the external NTFS drive with a 5400 RPM spindle, is it connected via USB 3.x, Thunderbolt, or a dock/hub? Certain USB controllers paired with Windows' delayed-write behavior can compound the problem of handle retention.

    • Does "Save" (overwrite) behave differently from "Save As" (new name or new folder)? This would help determine if it's tied to the new-file-creation code path or the general save pipeline.

     

    Let us know how it goes.

     

    Best,

    Anshul Saini