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 presence breaks Windows Start Quick Launch of any Folder #10382

New Issue
Closed
opened 2026-01-31 02:20:03 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 02:20:03 +00:00
Owner
Copy Link

Originally created by @zakutin on GitHub (Aug 29, 2020).

Environment

Windows build number: Microsoft Windows 10 Pro 2004 x64 [Version 10.0.19041.450]
Windows Terminal version (if applicable): 1.2.2381.0

Any other software?
- N/A (freshly installed Windows)

Steps to reproduce

After Windows 2004 update I noticed that the quick launch of any folder using Windows Start became buggy. I got used to launch the folders and any apps with help of Win button. And after the fresh installation of the Windows 2004 I experimentally detected, that the presense of Windows Terminal in the system breaks the usual behavior of the quick and fluent folder opening. I created an empty user account and installed Windows Terminal from Microsoft Store. The behavior is clearly reproducible. On the previous version of Windows 1909 everything was working well with Terminal installed. This issue is observed on both of my laptops.

I'm not sure if this is a Terminal issue or new Windows version 2004, that's why I'm reporting this here.

It does not brake the quick launch of the apps. It only relates to folders, as far as I noticed.

Steps to reproduce (assume Windows Terminal is installed):

  1. Press Win button (or click Start with mouse)
  2. Type any existing folder name you want to open
  3. Press Enter
  4. The search window is stuck and not disappeared to bring the focus on the opened folder.

Expected behavior

The folders shall be launched fluently. Search window shall disappear after Enter is pressed.

Actual behavior

You can see this on the video. I create a test account in Windows only to install the Terminal. At the beginning the quick folder launch works well, the focus goes to the opened folder and search window disappears after Enter is pressed. As soon as Terminal is installed, the quick folder launch is stuck and folder is blinking on background. That interrupts the fluent and quick usage of the search, as the user has to make some additional actions to switch on the opened folder (win+tab or mouse action).

Can anyone confirm this behavior?

https://youtu.be/16ULVHmZOvk

Originally created by @zakutin on GitHub (Aug 29, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Microsoft Windows 10 Pro 2004 x64 [Version 10.0.19041.450] Windows Terminal version (if applicable): 1.2.2381.0 Any other software? - N/A (freshly installed Windows) ``` # Steps to reproduce After Windows 2004 update I noticed that the quick launch of any folder using Windows Start became buggy. I got used to launch the folders and any apps with help of Win button. And after the fresh installation of the Windows 2004 I experimentally detected, that the presense of Windows Terminal in the system breaks the usual behavior of the quick and fluent folder opening. I created an empty user account and installed Windows Terminal from Microsoft Store. The behavior is clearly reproducible. On the previous version of Windows 1909 everything was working well with Terminal installed. This issue is observed on both of my laptops. I'm not sure if this is a Terminal issue or new Windows version 2004, that's why I'm reporting this here. It does not brake the quick launch of the apps. It only relates to folders, as far as I noticed. Steps to reproduce (assume Windows Terminal is installed): 1. Press Win button (or click Start with mouse) 2. Type any existing folder name you want to open 3. Press Enter 4. The search window is **stuck** and **not disappeared** to bring the focus on the opened folder. <!-- A description of how to trigger this bug. --> # Expected behavior The folders shall be launched fluently. Search window shall disappear after Enter is pressed. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior You can see this on the video. I create a test account in Windows only to install the Terminal. At the beginning the quick folder launch works well, the focus goes to the opened folder and search window disappears after Enter is pressed. As soon as Terminal is installed, the quick folder launch is stuck and folder is blinking on background. That interrupts the fluent and quick usage of the search, as the user has to make some additional actions to switch on the opened folder (win+tab or mouse action). Can anyone confirm this behavior? https://youtu.be/16ULVHmZOvk <!-- What's actually happening? -->
claunia added the Resolution-Duplicate label 2026-01-31 02:20:03 +00:00
claunia commented 2026-01-31 02:20:04 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Aug 29, 2020):

This is like what know in #7122 and it’s currently a known issue. You may found that thread helpful

@skyline75489 commented on GitHub (Aug 29, 2020): This is like what know in #7122 and it’s currently a known issue. You may found that thread helpful
claunia commented 2026-01-31 02:20:04 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 3, 2020):

Yep! Thanks, @skyline75489. /dup #7122

Thanks for the additional info @zakutin

@DHowett commented on GitHub (Sep 3, 2020): Yep! Thanks, @skyline75489. /dup #7122 Thanks for the additional info @zakutin
claunia commented 2026-01-31 02:20:05 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 3, 2020):

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!

@ghost commented on GitHub (Sep 3, 2020): 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!
claunia commented 2026-01-31 02:20:05 +00:00
Author
Owner
Copy Link

@zakutin commented on GitHub (Sep 3, 2020):

Thanks for info!

@zakutin commented on GitHub (Sep 3, 2020): Thanks for info!
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 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#10382
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?