starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Cannot rename folder in File Explorer once opened in Windows Terminal #20859

New Issue
Closed
opened 2026-01-31 07:26:05 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 07:26:05 +00:00
Owner
Copy Link

Originally created by @ehea617 on GitHub (Nov 20, 2023).

Windows Terminal version

1.18.2822.0

Windows build number

10.0.22631.0

Other Software

No response

Steps to reproduce

  1. Navigate to a folder in File Explorer and choose Open In Terminal
  2. Navigate out of the folder (cd ..) using the Terminal
  3. Attempt to rename the folder in File Explorer
  4. You will get an error stating that the action can not be completed because the folder is in use
    image
  5. Close Windows Terminal
  6. Attempt to rename the folder again from File Explorer and the rename will succeed

Expected Behavior

You should be able to rename the folder in File Explorer at minimum once you are navigated out of the folder in Windows Terminal. In cmd.exe or powershell.exe you are able to rename the folder through File Explorer even if you are currently in the directory in the terminal.

Actual Behavior

Unable to rename folder until Windows Terminal is fully closed. The folder appears to be write-locked by Windows Terminal.

Originally created by @ehea617 on GitHub (Nov 20, 2023). ### Windows Terminal version 1.18.2822.0 ### Windows build number 10.0.22631.0 ### Other Software _No response_ ### Steps to reproduce 1. Navigate to a folder in File Explorer and choose Open In Terminal 2. Navigate out of the folder (cd ..) using the Terminal 3. Attempt to rename the folder in File Explorer 4. You will get an error stating that the action can not be completed because the folder is in use ![image](https://github.com/microsoft/terminal/assets/12926544/74418bc0-300f-4834-a49a-3a5f9b381819) 5. Close Windows Terminal 6. Attempt to rename the folder again from File Explorer and the rename will succeed ### Expected Behavior You should be able to rename the folder in File Explorer at minimum once you are navigated out of the folder in Windows Terminal. In cmd.exe or powershell.exe you are able to rename the folder through File Explorer even if you are currently in the directory in the terminal. ### Actual Behavior Unable to rename folder until Windows Terminal is fully closed. The folder appears to be write-locked by Windows Terminal.
claunia added the Resolution-By-DesignNeeds-TriageIssue-BugNeeds-Attention labels 2026-01-31 07:26:05 +00:00
claunia commented 2026-01-31 07:26:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 20, 2023):

What shell are you running in the Terminal? PowerShell/?

@zadjii-msft commented on GitHub (Nov 20, 2023): What shell are you running in the Terminal? PowerShell/?
claunia commented 2026-01-31 07:26:07 +00:00
Author
Owner
Copy Link

@ehea617 commented on GitHub (Nov 20, 2023):

What shell are you running in the Terminal? PowerShell/?

I am using Windows PowerShell as my default shell.

@ehea617 commented on GitHub (Nov 20, 2023): > What shell are you running in the Terminal? PowerShell/? I am using Windows PowerShell as my default shell.
claunia commented 2026-01-31 07:26:07 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 20, 2023):

I think we fixed this for the Terminal in 1.18, but IIRC PowerShell leaves itself in the CWD it was created in, even after you cd out of that directory. You might be able to check by opening a Command Prompt tab, and then cd'ing somewhere else, and closing the pwsh tab.

@zadjii-msft commented on GitHub (Nov 20, 2023): I think we fixed this for the Terminal in 1.18, but IIRC PowerShell leaves itself in the CWD it was created in, even after you `cd` out of that directory. You might be able to check by opening a Command Prompt tab, and then cd'ing somewhere else, and closing the pwsh tab.
claunia commented 2026-01-31 07:26:07 +00:00
Author
Owner
Copy Link

@ehea617 commented on GitHub (Nov 20, 2023):

I think we fixed this for the Terminal in 1.18, but IIRC PowerShell leaves itself in the CWD it was created in, even after you cd out of that directory. You might be able to check by opening a Command Prompt tab, and then cd'ing somewhere else, and closing the pwsh tab.

Closing the Windows PowerShell tab allows renaming the folder. Additionally, If I go into the Windows Terminal settings and set the default profile to Command Prompt the issue does not occur.

@ehea617 commented on GitHub (Nov 20, 2023): > I think we fixed this for the Terminal in 1.18, but IIRC PowerShell leaves itself in the CWD it was created in, even after you `cd` out of that directory. You might be able to check by opening a Command Prompt tab, and then cd'ing somewhere else, and closing the pwsh tab. Closing the Windows PowerShell tab allows renaming the folder. Additionally, If I go into the Windows Terminal settings and set the default profile to Command Prompt the issue does not occur.
claunia commented 2026-01-31 07:26:07 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 21, 2023):

Unfortunately, this isn't Terminal can help with. PowerShell is running with that folder locked (even if it is not currently using it). Windows is more strict than other platforms with regards to deleting files that are open.

@DHowett commented on GitHub (Nov 21, 2023): Unfortunately, this isn't Terminal can help with. PowerShell is running with that folder locked (even if it is not currently using it). Windows is more strict than other platforms with regards to deleting files that are open.
claunia commented 2026-01-31 07:26:07 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 21, 2023):

It may be worth filing an issue over on the PowerShell repository!

@DHowett commented on GitHub (Nov 21, 2023): It may be worth filing an issue over on the [PowerShell repository](https://github.com/powershell/powershell)!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Attention Needs-Triage Resolution-By-Design
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20859
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?