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

bug(terminal-preview): terminal opens multiple instances on launch #22934

New Issue
Closed
opened 2026-01-31 08:27:45 +00:00 by claunia · 16 comments
claunia commented 2026-01-31 08:27:45 +00:00
Owner
Copy Link

Originally created by @vipexv on GitHub (Feb 17, 2025).

Windows Terminal version

1.23.10353.0

Windows build number

10.0.26100.0

Other Software

No response

Steps to reproduce

Open the Terminal.

Expected Behavior

Expected behavior is for it to only open 1 instance not multiple.

Actual Behavior

Everytime i launch the terminal, it seems to open multiple instances, and this only happens on the preview version.

Also everytime i open it through the context menu it opens 3, so 1 of them is usually in the correct path and the rest are always opened in root.

Originally created by @vipexv on GitHub (Feb 17, 2025). ### Windows Terminal version 1.23.10353.0 ### Windows build number 10.0.26100.0 ### Other Software _No response_ ### Steps to reproduce Open the Terminal. ### Expected Behavior Expected behavior is for it to only open 1 instance not multiple. ### Actual Behavior Everytime i launch the terminal, it seems to open multiple instances, and this only happens on the preview version. Also everytime i open it through the context menu it opens 3, so 1 of them is usually in the correct path and the rest are always opened in root.
claunia commented 2026-01-31 08:27:46 +00:00
Author
Owner
Copy Link

@FlyMandi commented on GitHub (Feb 18, 2025):

I'm also on 1.23.10353.0 and have noticed this exact behaviour. This has only started happening with the most recent version and "firstWindowPreference": "defaultProfile" is set, so it's not that.

Additionally, when starting other applications, such as SKSE, two default profile and default location terminal preview windows open, when previously none did.

@FlyMandi commented on GitHub (Feb 18, 2025): I'm also on `1.23.10353.0` and have noticed this exact behaviour. This has only started happening with the most recent version and `"firstWindowPreference": "defaultProfile"` is set, so it's not that. Additionally, when starting other applications, such as [SKSE](https://skse.silverlock.org/), two default profile and default location terminal preview windows open, when previously none did.
claunia commented 2026-01-31 08:27:47 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Feb 19, 2025):

Thanks for filing! Looks like the persisted window layout is stored without any tabs. And even though firstWindowPreference is set to defaultProfile, we're still creating new tabs on launch!

We should take a look at how other tabbed applications handle storing state and a similar setting (open previous session).

Discussion topic: consider adding another setting to clarify if we want the last closed window to be stored

@carlos-zamora commented on GitHub (Feb 19, 2025): Thanks for filing! Looks like the persisted window layout is stored without any tabs. And even though `firstWindowPreference` is set to `defaultProfile`, we're still creating new tabs on launch! We should take a look at how other tabbed applications handle storing state and a similar setting (open previous session). Discussion topic: consider adding another setting to clarify if we want the last closed window to be stored
claunia commented 2026-01-31 08:27:47 +00:00
Author
Owner
Copy Link

@vipexv commented on GitHub (Mar 17, 2025):

Slight update, a little bit ago i moved to canary and this issue wasn't occurring, it just started happening once again on the canary build.

@vipexv commented on GitHub (Mar 17, 2025): Slight update, a little bit ago i moved to canary and this issue wasn't occurring, it just started happening once again on the canary build.
claunia commented 2026-01-31 08:27:47 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 17, 2025):

Argh! Thank you.

@DHowett commented on GitHub (Mar 17, 2025): Argh! Thank you.
claunia commented 2026-01-31 08:27:47 +00:00
Author
Owner
Copy Link

@vipexv commented on GitHub (Mar 17, 2025):

Some more information.

  1. The issue seems to be happening randomly (i have no idea what specifically causes this)
  2. The issue is more common when opening the terminal through the context menu, as when i was opening it through the search bar it seemed to be fine.
@vipexv commented on GitHub (Mar 17, 2025): Some more information. 1. The issue seems to be happening randomly (i have no idea what specifically causes this) 2. The issue is more common when opening the terminal through the context menu, as when i was opening it through the search bar it seemed to be fine.
claunia commented 2026-01-31 08:27:48 +00:00
Author
Owner
Copy Link

@wgetnz commented on GitHub (Mar 19, 2025):

same.

@wgetnz commented on GitHub (Mar 19, 2025): same.
claunia commented 2026-01-31 08:27:48 +00:00
Author
Owner
Copy Link

@BasOnline commented on GitHub (Mar 19, 2025):

Workaround for me was to change "When Terminal starts" under "Startup" to another option and back again.

@BasOnline commented on GitHub (Mar 19, 2025): Workaround for me was to change "When Terminal starts" under "Startup" to another option and back again.
claunia commented 2026-01-31 08:27:48 +00:00
Author
Owner
Copy Link

@remixbyte commented on GitHub (Apr 5, 2025):

Version: 1.23.250314002-preview
Encountered the same problem.
Is there any solution?

@remixbyte commented on GitHub (Apr 5, 2025): Version: 1.23.250314002-preview Encountered the same problem. Is there any solution?
claunia commented 2026-01-31 08:27:48 +00:00
Author
Owner
Copy Link

@remixbyte commented on GitHub (Apr 5, 2025):

Workaround for me was to change "When Terminal starts" under "Startup" to another option and back again.

Simple and magical. 😄
But it did solve the problem temporarily.

@remixbyte commented on GitHub (Apr 5, 2025): > Workaround for me was to change "When Terminal starts" under "Startup" to another option and back again. Simple and magical. 😄 But it did solve the problem temporarily.
claunia commented 2026-01-31 08:27:49 +00:00
Author
Owner
Copy Link

@quyenvsp commented on GitHub (Apr 9, 2025):

Correct workaround is backup your settings.json then System Settings > Installed apps > Advanced options of Terminal Preview > Reset. Now just restore settings.json

@quyenvsp commented on GitHub (Apr 9, 2025): Correct workaround is backup your settings.json then System Settings > Installed apps > Advanced options of Terminal Preview > Reset. Now just restore settings.json
claunia commented 2026-01-31 08:27:49 +00:00
Author
Owner
Copy Link

@crumbr commented on GitHub (Apr 15, 2025):

Correct workaround is backup your settings.json then System Settings > Installed apps > Advanced options of Terminal Preview > Reset. Now just restore settings.json

Worked for me

@crumbr commented on GitHub (Apr 15, 2025): > Correct workaround is backup your settings.json then System Settings > Installed apps > Advanced options of Terminal Preview > Reset. Now just restore settings.json Worked for me
claunia commented 2026-01-31 08:27:49 +00:00
Author
Owner
Copy Link

@windwhim commented on GitHub (Apr 17, 2025):

Correct workaround is backup your settings.json then System Settings > Installed apps > Advanced options of Terminal Preview > Reset. Now just restore settings.json

It's amazing, but it does work for me.

@windwhim commented on GitHub (Apr 17, 2025): > Correct workaround is backup your settings.json then System Settings > Installed apps > Advanced options of Terminal Preview > Reset. Now just restore settings.json It's amazing, but it does work for me.
claunia commented 2026-01-31 08:27:49 +00:00
Author
Owner
Copy Link

@golf1052 commented on GitHub (Apr 19, 2025):

I'm seeing this with version 1.23.10732.0 (Terminal Preview).

Replication steps:

  1. Ensure all instances of Terminal are closed
  2. Trigger an action that will open a Terminal window (for example debug a console based application in Visual Studio)
  3. Your expected Terminal window will open but a second Terminal window will open along with the first one.
@golf1052 commented on GitHub (Apr 19, 2025): I'm seeing this with version 1.23.10732.0 (Terminal Preview). Replication steps: 1. Ensure all instances of Terminal are closed 2. Trigger an action that will open a Terminal window (for example debug a console based application in Visual Studio) 3. Your expected Terminal window will open but a second Terminal window will open along with the first one.
claunia commented 2026-01-31 08:27:50 +00:00
Author
Owner
Copy Link

@softwrx commented on GitHub (Apr 28, 2025):

Workaround for me was to change "When Terminal starts" under "Startup" to another option and back again.

I just started having two windows open when I started the first session (1.23.11132.0) for on apparent reason. After a reboot, no other changes to settings, and no update that I'm aware of, it just started. Click the terminal icon in the dock, two terminals open instantly.

Changing this setting to the other option, saving, closing terminal, starting it up and chanege it back, save and close. Now it's back to opening just a single window. Odd, but glad that worked. Thanks.

@softwrx commented on GitHub (Apr 28, 2025): > Workaround for me was to change "When Terminal starts" under "Startup" to another option and back again. I just started having two windows open when I started the first session (1.23.11132.0) for on apparent reason. After a reboot, no other changes to settings, and no update that I'm aware of, it just started. Click the terminal icon in the dock, two terminals open instantly. Changing this setting to the other option, saving, closing terminal, starting it up and chanege it back, save and close. Now it's back to opening just a single window. Odd, but glad that worked. Thanks.
claunia commented 2026-01-31 08:27:50 +00:00
Author
Owner
Copy Link

@valepu commented on GitHub (May 4, 2025):

Workaround for me was to change "When Terminal starts" under "Startup" to another option and back again.

I just started having two windows open when I started the first session (1.23.11132.0) for on apparent reason. After a reboot, no other changes to settings, and no update that I'm aware of, it just started. Click the terminal icon in the dock, two terminals open instantly.

Changing this setting to the other option, saving, closing terminal, starting it up and chanege it back, save and close. Now it's back to opening just a single window. Odd, but glad that worked. Thanks.

I'm having the same issue on the same version. The workaround worked for me but after a few reboots I started having the issue again

@valepu commented on GitHub (May 4, 2025): > > Workaround for me was to change "When Terminal starts" under "Startup" to another option and back again. > > I just started having two windows open when I started the first session (1.23.11132.0) for on apparent reason. After a reboot, no other changes to settings, and no update that I'm aware of, it just started. Click the terminal icon in the dock, two terminals open instantly. > > Changing this setting to the other option, saving, closing terminal, starting it up and chanege it back, save and close. Now it's back to opening just a single window. Odd, but glad that worked. Thanks. I'm having the same issue on the same version. The workaround worked for me but after a few reboots I started having the issue again
claunia commented 2026-01-31 08:27:50 +00:00
Author
Owner
Copy Link

@vipexv commented on GitHub (May 17, 2025):

Thank you to the team for working on this & fixing it, i hope all of you have a great day :]

@vipexv commented on GitHub (May 17, 2025): Thank you to the team for working on this & fixing it, i hope all of you have a great day :]
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 Area-Windowing Issue-Bug Needs-Discussion Needs-Tag-Fix Product-Terminal
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#22934
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?