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

Windows Terminal session restore is not remembering the last directory that was set in each tab #18887

New Issue
Open
opened 2026-01-31 06:27:17 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 06:27:17 +00:00
Owner
Copy Link

Originally created by @cyclr-adrian on GitHub (Nov 14, 2022).

Windows Terminal version

1.15.2875.0

Windows build number

10.0.22621.0

Other Software

I did have Oh-My-Posh module loading in via PowerShell profile, but I have since commented out that module from loading and running to eliminate it from this issue.

Steps to reproduce

Pre-Requisites

In your Windows Terminal Settings page set the following:

  1. Settings => Startup => When Terminal Starts set value to Open windows from previous session.
  2. The PowerShell profile you are using has a startingDirectory set e.g. "startingDirectory": "%USERPROFILE%"

Steps

  1. Load 2 PowerShell tabs in Windows Terminal
  2. Rename the tabs Tab 1 and Tab 2
  3. In Tab 2 change the directory so that it is different to the directory in Tab 1.
  4. Close Windows Terminal
  5. Re-Open Windows Terminal

Expected Behavior

When Re-Opening Windows Terminal Tab 1 and Tab 2 are restored with their tab names (Tab 1 and Tab 2) plus the initial directory in each tab is the same as it was when the previous Windows Terminal session was closed.

Actual Behavior

When Re-Opening Windows Terminal Tab 1 and Tab 2 are restored with their tab names (Tab 1 and Tab 2) however the initial directory in each tab is NOT the same as it was when the previous Windows Terminal session was closed, but tabs appear to have the same directory set.

I have tried changing the startingDirectory for the profile I was using from "startingDirectory": "%USERPROFILE%" to "startingDirectory": null but it makes no difference.

Originally created by @cyclr-adrian on GitHub (Nov 14, 2022). ### Windows Terminal version 1.15.2875.0 ### Windows build number 10.0.22621.0 ### Other Software I did have Oh-My-Posh module loading in via PowerShell profile, but I have since commented out that module from loading and running to eliminate it from this issue. ### Steps to reproduce #### Pre-Requisites In your Windows Terminal Settings page set the following: 1. `Settings` => `Startup` => `When Terminal Starts` set value to `Open windows from previous session`. 2. The PowerShell profile you are using has a `startingDirectory` set e.g. `"startingDirectory": "%USERPROFILE%"` #### Steps 1. Load 2 PowerShell tabs in Windows Terminal 3. Rename the tabs `Tab 1` and `Tab 2` 4. In `Tab 2` change the directory so that it is different to the directory in `Tab 1`. 5. Close Windows Terminal 6. Re-Open Windows Terminal ### Expected Behavior When Re-Opening Windows Terminal `Tab 1` and `Tab 2` are restored with their tab names (`Tab 1` and `Tab 2`) plus the initial directory in each tab is the same as it was when the previous Windows Terminal session was closed. ### Actual Behavior When Re-Opening Windows Terminal `Tab 1` and `Tab 2` are restored with their tab names (`Tab 1` and `Tab 2`) however the initial directory in each tab is NOT the same as it was when the previous Windows Terminal session was closed, but tabs appear to have the same directory set. I have tried changing the `startingDirectory` for the profile I was using from `"startingDirectory": "%USERPROFILE%"` to `"startingDirectory": null` but it makes no difference.
claunia added the Issue-QuestionNeeds-TriageIssue-BugResolution-Answered labels 2026-01-31 06:27:17 +00:00
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 Issue-Question Needs-Triage Resolution-Answered
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#18887
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?