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

File explorer super slow #12923

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

Originally created by @rluvaton on GitHub (Mar 8, 2021).

Environment

Windows build number: 10.0.19042.631 (20H2)
Windows Terminal: 1.6.10571

RAM: 16GB
CPU: Intel Core i7-9700 3.00GHz
Disk: 512GB SSD
GPU: Intel(R) UHD Graphics 630

Any other software?

Note: this is a fresh new computer and it happens before with my previous computer

Steps to reproduce

I downloaded the Windows Terminal from GitHub Release and installed it on offline computer, the second I installed it the File Explorer because super slow that it takes about 5 seconds to open a folder when I uninstalled the Windows Terminal the File Explorer returned to his normal speed.

Expected behavior

File Explorer stay fast

Actual behavior

File Explorer very slow

Originally created by @rluvaton on GitHub (Mar 8, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: 10.0.19042.631 (20H2) Windows Terminal: 1.6.10571 RAM: 16GB CPU: Intel Core i7-9700 3.00GHz Disk: 512GB SSD GPU: Intel(R) UHD Graphics 630 Any other software? ``` Note: this is a fresh new computer and it happens before with my previous computer # Steps to reproduce <!-- A description of how to trigger this bug. --> I downloaded the Windows Terminal from GitHub Release and installed it on **offline** computer, the second I installed it the File Explorer because super slow that it takes about 5 seconds to open a folder when I uninstalled the Windows Terminal the File Explorer returned to his normal speed. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> File Explorer stay fast # Actual behavior <!-- What's actually happening? --> File Explorer very slow
claunia added the Needs-TriageNeeds-Tag-FixNeeds-AttentionProduct-Terminal labels 2026-01-31 03:29:05 +00:00
claunia commented 2026-01-31 03:29:07 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 8, 2021):

Huh. If this was more widespread, then I'm sure we would have heard of this by now. It's possible that this is just explorer.exe trying to populate the context menu entries for the Terminal. Maybe it goes away after a reboot (and explorer caches the results).

  • How specifically did you install the terminal offline? By double-clicking the .msix, or by doing the "rename to zip, unzip" trick?
  • Does installing the Terminal, then rebooting the machine, then opening explorer repro the same slowness?
  • Is it slow every time you navigate in explorer (like, every time you change directories), or just on the initial launch of the explorer window?
@zadjii-msft commented on GitHub (Mar 8, 2021): Huh. If this was more widespread, then I'm sure we would have heard of this by now. It's possible that this is just `explorer.exe` trying to populate the context menu entries for the Terminal. Maybe it goes away after a reboot (and explorer caches the results). * How specifically did you install the terminal offline? By double-clicking the `.msix`, or by doing the "rename to zip, unzip" trick? * Does installing the Terminal, then rebooting the machine, then opening explorer repro the same slowness? * Is it slow every time you navigate in explorer (like, every time you change directories), or just on the initial launch of the explorer window?
claunia commented 2026-01-31 03:29:08 +00:00
Author
Owner
Copy Link

@rluvaton commented on GitHub (Mar 8, 2021):

Huh. If this was more widespread, then I'm sure we would have heard of this by now.

It's possible that this is just explorer.exe trying to populate the context menu entries for the Terminal. Maybe it goes away after a reboot (and explorer caches the results).

Is there an option to remove the context menu entries so I can test that?

The same issue happening for a colleague of mine too

  • How specifically did you install the terminal offline? By double-clicking the .msix, or by doing the "rename to zip, unzip" trick?

Double-clicking

  • Does installing the Terminal, then rebooting the machine, then opening explorer repro the same slowness?

Yes

  • Is it slow every time you navigate in explorer (like, every time you change directories), or just on the initial launch of the explorer window?

Every time

@zadjii-msft The weird thing is that it doesn't happen in the open file dialog (when trying to upload a file to Chrome for example)

It happened too with my previous computer which running Windows 10 2004

On my personal laptop, this issue doesn't exist...

@rluvaton commented on GitHub (Mar 8, 2021): > Huh. If this was more widespread, then I'm sure we would have heard of this by now. > It's possible that this is just `explorer.exe` trying to populate the context menu entries for the Terminal. Maybe it goes away after a reboot (and explorer caches the results). Is there an option to remove the context menu entries so I can test that? The same issue happening for a colleague of mine too > * How specifically did you install the terminal offline? By double-clicking the `.msix`, or by doing the "rename to zip, unzip" trick? Double-clicking > * Does installing the Terminal, then rebooting the machine, then opening explorer repro the same slowness? Yes > * Is it slow every time you navigate in explorer (like, every time you change directories), or just on the initial launch of the explorer window? Every time @zadjii-msft The weird thing is that it doesn't happen in the open file dialog (when trying to upload a file to Chrome for example) It happened too with my previous computer which running Windows 10 2004 On my personal laptop, this issue doesn't exist...
claunia commented 2026-01-31 03:29:08 +00:00
Author
Owner
Copy Link

@rluvaton commented on GitHub (Mar 9, 2021):

When I installed it offline I got the same issue as #6010, I solved it by changing the permission for the WindowsApps directory (terrible idea), so I uninstalled and installed again using this workaround -> https://github.com/microsoft/terminal/issues/6010#issuecomment-632381385

And it back to be fast, thanks!

@rluvaton commented on GitHub (Mar 9, 2021): When I installed it offline I got the same issue as #6010, I solved it by changing the permission for the WindowsApps directory (terrible idea), so I uninstalled and installed again using this workaround -> https://github.com/microsoft/terminal/issues/6010#issuecomment-632381385 And it back to be fast, thanks!
claunia commented 2026-01-31 03:29:08 +00:00
Author
Owner
Copy Link

@CodyCardinal commented on GitHub (Aug 3, 2022):

On a computer with a messed up windows store ( and the store reset app does nothing for me ). I had also changed permission on the windows app directory as a last ditch effort to fix the above issue. Working around it I had to create a new windows user, log in as that and then I could install WSL. It's been a journey.

I used chocolatey to install windows terminal, then proceeded to reboot at some point.
After that Explorer was absolutely useless if the internet was connected, disabling all my network adapters would immediately resolve.
I troubleshooted right click context menu changes, drivers, you name it for hours.
uninstalling windows terminal fixed it immediately. not sure why it cares about an internet connection when i'm right clicking in explorer ( and why it's faster otherwise ).

@CodyCardinal commented on GitHub (Aug 3, 2022): On a computer with a messed up windows store ( and the store reset app does nothing for me ). I had also changed permission on the windows app directory as a last ditch effort to fix the above issue. Working around it I had to create a new windows user, log in as that and then I could install WSL. It's been a journey. I used chocolatey to install windows terminal, then proceeded to reboot at some point. After that Explorer was absolutely useless if the internet was connected, disabling all my network adapters would immediately resolve. I troubleshooted right click context menu changes, drivers, you name it for hours. uninstalling windows terminal fixed it immediately. not sure why it cares about an internet connection when i'm right clicking in explorer ( and why it's faster otherwise ).
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 Needs-Attention Needs-Tag-Fix Needs-Triage 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#12923
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?