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 prevents search dialog from closing automatically when searching for folders #13219

New Issue
Open
opened 2026-01-31 03:36:58 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 03:36:58 +00:00
Owner
Copy Link

Originally created by @renard11 on GitHub (Mar 28, 2021).

Hello!
I've never written a bug report before, so I don't really know how to do this...

For about a year I'm having an issue with Windows that drives me crazy. Not only me, also a few colleagues of mine and my brother (so I'm not an isolated incident). Whenever I press the Windows-Key and search for a folder, or press Windows-Key+S and search, or click on the search icon and conduct a search, after finding the folder and pressing "Enter", Windows Explorer opens that folder, but the search dialog does not close automatically as it is supposed to do. It stays open, and Windows Explorer opens in the background, and the symbol in the taskbar starts blinking because it's blocked by the search dialog. This is highly annoying, because you always have to manually look for the opened folder in the taskbar. The same happens if you pin a folder to the start menu. If you click on it, explorer opens in the background, and the start menu does not close automatically and blocks everything. This is even more annoying if you have set your start menu to open in full screen, and you always have to press Esc! I have written my Masters Thesis while both of my Laptops (a Surface Pro 7 and an Acer Aspire) drove me mad when I had to open folders! This only happens for folders, files and apps open as they should. I contacted Microsoft several times because of this, but I was always told to reinstall Windows by downloading an ISO.
Now I asked a couple of my friends and colleagues if they had this problem because I couldn't work like this any longer, and some of them did. And by pure chance we figured out that all of us who had this problem had Windows Terminal installed. We uninstalled it, and now everything works smoothly (at least as smooth as Windows can be)! Now I also found a thread on answers.microsoft.com where other people are having the same issue (since July 2020)! Please fix that!!

https://answers.microsoft.com/en-us/windows/forum/windows_10-start-win_menu/start-menu-not-closing-after-opening-anything-from/eaae4553-a746-47f8-ae6a-acd62bbf6187?page=1

https://answers.microsoft.com/en-us/windows/forum/all/windows-search-doesnt-close-after-opening-a-folder/6d9be224-0f02-4ab8-a2f8-24ad6a8c26aa

Originally created by @renard11 on GitHub (Mar 28, 2021). Hello! I've never written a bug report before, so I don't really know how to do this... For about a year I'm having an issue with Windows that drives me crazy. Not only me, also a few colleagues of mine and my brother (so I'm not an isolated incident). Whenever I press the Windows-Key and search for a folder, or press Windows-Key+S and search, or click on the search icon and conduct a search, after finding the folder and pressing "Enter", Windows Explorer opens that folder, but the search dialog does not close automatically as it is supposed to do. It stays open, and Windows Explorer opens in the background, and the symbol in the taskbar starts blinking because it's blocked by the search dialog. This is highly annoying, because you always have to manually look for the opened folder in the taskbar. The same happens if you pin a folder to the start menu. If you click on it, explorer opens in the background, and the start menu does not close automatically and blocks everything. This is even more annoying if you have set your start menu to open in full screen, and you always have to press Esc! I have written my Masters Thesis while both of my Laptops (a Surface Pro 7 and an Acer Aspire) drove me mad when I had to open folders! This only happens for folders, files and apps open as they should. I contacted Microsoft several times because of this, but I was always told to reinstall Windows by downloading an ISO. Now I asked a couple of my friends and colleagues if they had this problem because I couldn't work like this any longer, and some of them did. And by pure chance we figured out that all of us who had this problem had Windows Terminal installed. We uninstalled it, and now everything works smoothly (at least as smooth as Windows can be)! Now I also found a thread on answers.microsoft.com where other people are having the same issue (since July 2020)! Please fix that!! [https://answers.microsoft.com/en-us/windows/forum/windows_10-start-win_menu/start-menu-not-closing-after-opening-anything-from/eaae4553-a746-47f8-ae6a-acd62bbf6187?page=1](https://answers.microsoft.com/en-us/windows/forum/windows_10-start-win_menu/start-menu-not-closing-after-opening-anything-from/eaae4553-a746-47f8-ae6a-acd62bbf6187?page=1) [https://answers.microsoft.com/en-us/windows/forum/all/windows-search-doesnt-close-after-opening-a-folder/6d9be224-0f02-4ab8-a2f8-24ad6a8c26aa](https://answers.microsoft.com/en-us/windows/forum/all/windows-search-doesnt-close-after-opening-a-folder/6d9be224-0f02-4ab8-a2f8-24ad6a8c26aa)
claunia added the Resolution-Duplicate label 2026-01-31 03:36:58 +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 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#13219
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?