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

Closing One Instance of Windows Terminal Closes All Instances When unfocusedAppearance with Opacity 100 is Enabled #22230

New Issue
Closed
opened 2026-01-31 08:07:13 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 08:07:13 +00:00
Owner
Copy Link

Originally created by @NikoEscobar on GitHub (Sep 7, 2024).

Windows Terminal version

1.20.11781.0

Windows build number

10.0.22631.0

Other Software

No response

Steps to reproduce

  1. Open Windows Terminal.

  2. In the settings, set the following configurations:

    {
  "opacity": 40,
  "useAcrylic": true,
  "unfocusedAppearance": {
    "opacity": 100
  }
}

  3. Open multiple instances of Windows Terminal.

  4. Close one of the open instances.

Expected Behavior

Only the closed instance of Windows Terminal should close, leaving the other instances open and unaffected.

Actual Behavior

Closing one instance of Windows Terminal causes all other open instances to close unexpectedly.

Originally created by @NikoEscobar on GitHub (Sep 7, 2024). ### Windows Terminal version 1.20.11781.0 ### Windows build number 10.0.22631.0 ### Other Software _No response_ ### Steps to reproduce 1. Open Windows Terminal. 2. In the settings, set the following configurations: ```json { "opacity": 40, "useAcrylic": true, "unfocusedAppearance": { "opacity": 100 } } 3. Open multiple instances of Windows Terminal. 4. Close one of the open instances. ### Expected Behavior Only the closed instance of Windows Terminal should close, leaving the other instances open and unaffected. ### Actual Behavior Closing one instance of Windows Terminal causes all other open instances to close unexpectedly.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 08:07:13 +00:00
claunia commented 2026-01-31 08:07:14 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 9, 2024):

This sounds a lot like #17520 - can you try Windows Terminal v1.21.2361.0 or Windows Terminal Preview v1.22.2362.0 and see if it's fixed for you there/?

@zadjii-msft commented on GitHub (Sep 9, 2024): This sounds a lot like #17520 - can you try [Windows Terminal v1.21.2361.0](https://github.com/microsoft/terminal/releases/tag/v1.21.2361.0) or [Windows Terminal Preview v1.22.2362.0](https://github.com/microsoft/terminal/releases/tag/v1.22.2362.0) and see if it's fixed for you there/?
claunia commented 2026-01-31 08:07:15 +00:00
Author
Owner
Copy Link

@NikoEscobar commented on GitHub (Sep 11, 2024):

This sounds a lot like #17520 - can you try Windows Terminal v1.21.2361.0 or Windows Terminal Preview v1.22.2362.0 and see if it's fixed for you there/?

I can confirm the issue is not present on Windows Terminal Preview v1.22.2362.0

As for the Windows Terminal v1.21.2361.0 version, I'm not really sure how to update my current version to this one, Microsoft Store is not detecting new a version to update.

@NikoEscobar commented on GitHub (Sep 11, 2024): > This sounds a lot like #17520 - can you try [Windows Terminal v1.21.2361.0](https://github.com/microsoft/terminal/releases/tag/v1.21.2361.0) or [Windows Terminal Preview v1.22.2362.0](https://github.com/microsoft/terminal/releases/tag/v1.22.2362.0) and see if it's fixed for you there/? I can confirm the issue is not present on [Windows Terminal Preview v1.22.2362.0](https://github.com/microsoft/terminal/releases/tag/v1.22.2362.0) As for the [Windows Terminal v1.21.2361.0](https://github.com/microsoft/terminal/releases/tag/v1.21.2361.0) version, I'm not really sure how to update my current version to this one, Microsoft Store is not detecting new a version to update.
claunia commented 2026-01-31 08:07:15 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Sep 25, 2024):

Awesome! Thanks for filing and following up! We'll mark this as a /dup of #17520.

@carlos-zamora commented on GitHub (Sep 25, 2024): Awesome! Thanks for filing and following up! We'll mark this as a /dup of #17520.
claunia commented 2026-01-31 08:07:15 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Sep 25, 2024):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Sep 25, 2024): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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 Resolution-Duplicate
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#22230
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?