Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File explorer super slow #9417

Closed
rluvaton opened this issue Mar 8, 2021 · 4 comments
Closed

File explorer super slow #9417

rluvaton opened this issue Mar 8, 2021 · 4 comments
Labels
Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-Terminal The new Windows Terminal.

Comments

@rluvaton
Copy link

rluvaton commented 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

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 8, 2021
@zadjii-msft
Copy link
Member

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 zadjii-msft added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Product-Terminal The new Windows Terminal. labels Mar 8, 2021
@rluvaton
Copy link
Author

rluvaton commented 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...

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Mar 8, 2021
@rluvaton
Copy link
Author

rluvaton commented 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 -> #6010 (comment)

And it back to be fast, thanks!

@rluvaton rluvaton closed this as completed Mar 9, 2021
@CodyCardinal
Copy link

CodyCardinal commented 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 up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-Terminal The new Windows Terminal.
Projects
None yet
Development

No branches or pull requests

3 participants