search

sandboxie-plus / Sandboxie

Sandboxie Plus & Classic
https://Sandboxie-Plus.com
GNU General Public License v3.0
13.83k stars 1.54k forks source link

Long times to open Explorer.exe windows ... #69

Open MaikBS opened 4 years ago

MaikBS commented 4 years ago

It takes a long time to open folders (save as) in Firefox. It takes a long time to open menus (right mouse button) in Opera. It all started with the upgrade to the Windows 10 2004 feature update.

I use the current version 5.41.2, Windows 10 2004 (Build 19041.329) Thanks!

rwasef1830 commented 4 years ago

I'm facing the same issue, it started after I enabled Device Guard and Hyper-V in Windows and enabled WSL2.

DavidXanatos commented 4 years ago

so when you disable device guard its fine? imho hyper-v alone shouldnt be an issue

rwasef1830 commented 4 years ago

Completely disabling device guard and virtualization based security and hyper-v using the DG_Readiness powershell script here https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-manage improves the performance a bit, however the issue remains. Also build 2004 here. The slowdown appears to be in the invocation or rendering of native controls as even native text box drop-downs take a second to appear, even the print dialog or native windows shell dialogs.

rwasef1830 commented 4 years ago

This issue doesn't affect Edge Chromium

henrikx commented 4 years ago

Basically doing anything in Explorer is slow for me.

Hyper-V and Virtualization Based Security disabled.

henrikx commented 4 years ago

@DavidXanatos Will you please look at this?

DavidXanatos commented 4 years ago

yes I will patience... please :)

skyler14 commented 4 years ago

Currently is there a recommended set of configurations with regards to Hyper-V/Virtual Machine Platform/WSL and other virtualization configurations in Win 10 to use.

henrikx commented 3 years ago

Has anyone found a solution to this? Does this happen to everyone on 20H2?

rwasef1830 commented 3 years ago

Yes, it still happens in build 2009. this is not solved.

DavidXanatos commented 3 years ago

i have updated my development VM to 20h2 an will take a look on that issue soon

rugabunda commented 3 years ago

Thanks david, same problem here! 20H2. I too am using virtualization.

henrikx commented 3 years ago

Just so that this is not mistakenly closed: Just mentioning that this is still an issue with "Explorer.exe" Windows, regardless of the changes in v0.7.4.

DavidXanatos commented 3 years ago

strange for me in the latest build the explorer runs very well, can you make a video and descripe in which usecases you are still getting these slowdowns?

henrikx commented 3 years ago

Video of problem is attached. If you need more info or want to see the problem on the machine directly then contact me. I can arrange for a TeamViewer session.

2021-06-09_19-19-47

henrikx commented 3 years ago

One thing I noticed: I have a lot of disks on this system and it seems that Explorer is polling MountPointManager (and related) a lot. Don't know if related to this problem or not...

rwasef1830 commented 3 years ago

I was forced to basically abandon Sandboxie completely thanks to this bug. Not only is opening explorer things inside sandboxed applications unbearable and unusable slow, but it has a big slowdown on the whole machine even for non-sandboxed processes. When I removed Sandboxie I realized how much effect it had open my machine responsiveness as a whole. It just seems to be much much worse with Hyper-V and Memory Protection and Device Guard/VBS and those things active. Note : I had forced programs and forced folders also active at the time. The slowdown gets exponentially worse if you have something like TortoiseGit / TortoiseHg and other shell extensions active also.

DavidXanatos commented 3 years ago

@henrikx whdo you get a monitor buffer overflow? Do you have any tracing functions activated? in the trace tab of the box options? these low down everything.

also yea a remote session would be helpfull

henrikx commented 3 years ago

I don't normally get monitor buffer overflow, but I think it happened because of the recording software. Just tested it and didn't get that message and it does not make a difference to this bug.

Nothing in access trace log on box options enabled. Turning on or off the global "trace logging" button also makes no difference.

Where can I contact you to set up a remote session? I have Discord (ciken#9165) if you use that.

henrikx commented 3 years ago

@DavidXanatos Did not hear from you yet. Please let me know where I can contact you, so that we can troubleshoot and hopefully get this fixed soon :)

andcha commented 3 years ago

Definitely something went wrong after windows update last year. Explorer.exe and even applications calling explorer to select files is painfully slow.

I would also like to add that some programs installed inside sandboxie are also unbearably slow to open and operate, for eg. photoshop.

DavidXanatos commented 3 years ago

@henrikx you can email me at xanatosdavid[at]gmail.com

isaak654 commented 3 years ago

Windows 10 20H2/21H1: 1) Windows Explorer is very slow to load when you go back to the main "This PC" screen that I set as startup. 2) When I right-click on a drive, I need to wait 7-10 seconds in order to see the context menu. 3) When I right-click on a file, I need to wait 3 seconds in order to see the context menu. 4) When I attempt to select multiple folders on my root drive with the mouse cursor, I need to wait 6 seconds to see the selection. 5) When I navigate only drives without going back or without any right-click / mouse selection, the performance is slightly better than a few Sandboxie versions ago, but I think it could still be improved.

isaak654 commented 3 years ago

See #1127, basically same issue on Windows 11.

DavidXanatos commented 3 years ago

I have randomly noticed somthign funny on 11 installs with this tool: https://www.startisback.com/tbd the explorer starts fast, what that tool does is it disables some win 11 stuff from explorer...

NyaMisty commented 3 years ago

I have randomly noticed somthign funny on 11 installs with this tool: https://www.startisback.com/tbd the explorer starts fast,

what that tool does is it disables some win 11 stuff from explorer...

Yep, and ExplorerPatcher does the same thing. The Win11 constantly enumerates HKR, that's why it's causing the whole system being slow.

DavidXanatos commented 3 years ago

I have randomly noticed somthign funny on 11 installs with this tool: https://www.startisback.com/tbd the explorer starts fast, what that tool does is it disables some win 11 stuff from explorer...

Yep, and ExplorerPatcher does the same thing. The Win11 constantly enumerates HKR, that's why it's causing the whole system being slow.

Yea, the whole windows 11 somehow feels like MSFT lost the source codes and is now using dirty patches to change the UI, I mean it really feels like a windows with a badly write 3rd party overlay software, LOL.

isaak654 commented 3 years ago

@DavidXanatos Did you manage to reproduce this on Windows 10 ?

DavidXanatos commented 3 years ago

No on windows 10 the explorer seams to work ok for me, not as fast as unsandboxed but bwloe 1-2 seconds for the context menus

andcha commented 3 years ago

No on windows 10 the explorer seams to work ok for me, not as fast as unsandboxed but bwloe 1-2 seconds for the context menus

On average spec PC like mine, it takes anywhere between 2-6 seconds to open explorer and then same for context menus. Trust me, it gets highly frustrating if the job requires repetitive action.

Maybe windows 10 thing was passed on to windows 11 due to which windows 11 also has similar issues. And maybe windows 11 solution could work on windows 10.

DavidXanatos commented 3 years ago

Windows 11 solution was to wait for a fixed windows 11 insider build, so it wil defiently not apply to 10

isaak654 commented 3 years ago

I've just noticed that ReadFilePath=%UserProfile%\AppData\Local\Microsoft\Windows helps to reduce my delay issue on Windows Explorer, and if you replace ReadFilePath with OpenFilePath the delay will be back.

I can reproduce this issue only on my real machine, not on a VM environment.

henrikx commented 3 years ago

I've just noticed that ReadFilePath=%UserProfile%\AppData\Local\Microsoft\Windows helps to reduce my delay issue on Windows Explorer, and if you replace ReadFilePath with OpenFilePath the delay will be back.

I can reproduce this issue only on my real machine, not on a VM environment.

Can confirm this. The performance is still reduced, but it is a lot better than before.

henrikx commented 3 years ago

There is not much reduction in delay when interacting with the files and folders. See attached gif if

henrikx commented 3 years ago

One interesting aspect to this bug is that it seemingly only affects the standalone instance of Explorer.exe. If I am using a program invoking a OpenFileDialog, the dialog runs fine with no performance issue (I tested Firefox's save page dialog).

isaak654 commented 3 years ago

There is not much reduction in delay when interacting with the files and folders. See attached gif.

I may have a few additional lines for that too. Please make sure to have installed 0.9.8c / 5.53.2 and apply:

OpenIpcPath=*\*BaseNamedObjects*\*HWNDInterface*
# Sync Integration Manager
ClosedClsid={9AA46009-3CE0-458A-A354-715610A075E6}
# Thumbnail Cache Out of Proc Server
ClosedClsid={AB8902B4-09CA-4BB6-B78D-A8F59079A8D5}
# OneDrive
ClosedClsid={71DCE5D6-4B57-496B-AC21-CD5B54EB93FD}
ReadFilePath=\Device\MountPointManager
ReadFilePath=%AllUsersProfile%\Microsoft\Windows\Caches
ReadFilePath=%UserProfile%\AppData\Local\Microsoft\Windows
ClosedIpcPath=*\Shell.CMruPidlList
BlockNetworkFiles=n

P.S. Make sure to not have repeated BlockNetworkFiles or ReadFilePath=%UserProfile%\AppData\Local\Microsoft\Windows references on your sandbox.

henrikx commented 3 years ago

There is not much reduction in delay when interacting with the files and folders. See attached gif.

I may have a few additional lines for that too. Please make sure to have installed 0.9.8c / 5.53.2 and apply:

OpenIpcPath=*\*BaseNamedObjects*\*HWNDInterface*
# Sync Integration Manager
ClosedClsid={9AA46009-3CE0-458A-A354-715610A075E6}
# Thumbnail Cache Out of Proc Server
ClosedClsid={AB8902B4-09CA-4BB6-B78D-A8F59079A8D5}
# OneDrive
ClosedClsid={71DCE5D6-4B57-496B-AC21-CD5B54EB93FD}
ReadFilePath=\Device\MountPointManager
ReadFilePath=%AllUsersProfile%\Microsoft\Windows\Caches
ReadFilePath=%UserProfile%\AppData\Local\Microsoft\Windows
ClosedIpcPath=*\Shell.CMruPidlList
BlockNetworkFiles=n

P.S. Make sure to not have repeated BlockNetworkFiles or ReadFilePath=%UserProfile%\AppData\Local\Microsoft\Windows references on your sandbox.

Thanks! These lines improved performance a little bit, but unfortunately not enough to call the performance "good". It still chugs quite a lot while selecting files, and it freezes for half a second when entering a directory.

isaak654 commented 3 years ago

Thanks! These lines improved performance a little bit, but unfortunately not enough to call the performance "good".

Well, I looked into this issue and obtained a few results, so I'm sure that an experienced dev could do better. 😘

kimpurcell commented 3 years ago

Any updates on getting File Explorer to run on Windows 11? It's been officially released.

isaak654 commented 3 years ago

Any updates on getting File Explorer to run on Windows 11? It's been officially released.

I think the maintainer is waiting the next updated Windows 11 release, see here. About Windows 10, the issue is different and I published a workaround a few posts ago.

isaak654 commented 2 years ago

The slowness with sandboxed sessions of Windows Explorer is definitely improved for me with Plus 1.0.7 / W10 21H1.

But there are still two remaining things:

henrikx commented 2 years ago

The slowness with sandboxed sessions of Windows Explorer is definitely improved for me with Plus 1.0.7 / W10 21H1.

The only thing left is the delay with the right-click context menu on a single drive which now it takes almost two seconds. About this one, I think it's something related to SandboxieCrypto.exe that it loads at the same time of the context menu delay.

Yes! There is a big improvement with this update. However, there are some additional things that I found: Opening one of the ribbon menus at the top will slow Explorer down. Each menu you open adds delay, so after opening all of them it is back to the unusable slowness we have seen before. See attached gif: gif

isaak654 commented 2 years ago

I think that the Ribbon menu slowdown is related to multiple \Device\MountPointManager entries that are called a lot of times without apparent reason:

Plus 1.0.7 log with Windows Explorer (ribbon menu slowdown) ``` |Processo| |Tipo| |Stato| |Valore| explorer.exe (9064, 5268) - 21:19:01.008 WinClass (U) Net UI Tool Window explorer.exe (9064, 5268) - 21:19:02.880 WinClass (U) Progman explorer.exe (9064, 9052) - 21:19:02.880 Ipc (U) \Sessions\1\BaseNamedObjects\Local\Shell.CMruPidlList explorer.exe (9064, 9052) - 21:19:02.880 Ipc (D) \Sessions\1\BaseNamedObjects\Shell.CMruPidlList explorer.exe (9064, 5268) - 21:19:02.880 WinClass (U) Progman explorer.exe (9064, 5268) - 21:19:02.880 WinClass (U) $:explorer.exe explorer.exe (9064, 5268) - 21:19:02.880 WinClass (U) Closed Progman explorer.exe (9064, 9052) - 21:19:02.880 Ipc (U) \Sessions\1\BaseNamedObjects\Local\Shell.CMruPidlList explorer.exe (9064, 9052) - 21:19:02.880 Ipc (D) \Sessions\1\BaseNamedObjects\Shell.CMruPidlList explorer.exe (9064, 5268) - 21:19:02.880 ComClass (U) {3EEF301F-B596-4C0B-BD92-013BEAFCE793} Desktop Undo Manager explorer.exe (9064, 2424) - 21:19:02.880 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:02.880 Pipe (U) (2) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:02.880 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:02.880 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:02.880 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:02.880 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:02.880 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:02.880 Pipe (U) \Device\MountPointManager explorer.exe (9064, 9052) - 21:19:03.475 Ipc (U) \Sessions\1\BaseNamedObjects\Local\Shell.CMruPidlList explorer.exe (9064, 9052) - 21:19:03.475 Ipc (D) \Sessions\1\BaseNamedObjects\Shell.CMruPidlList explorer.exe (9064, 9052) - 21:19:03.475 Ipc (U) \Sessions\1\BaseNamedObjects\Local\Shell.CMruPidlList explorer.exe (9064, 9052) - 21:19:03.475 Ipc (D) \Sessions\1\BaseNamedObjects\Shell.CMruPidlList explorer.exe (9064, 5268) - 21:19:03.475 ComClass (U) {3EEF301F-B596-4C0B-BD92-013BEAFCE793} Desktop Undo Manager explorer.exe (9064, 2424) - 21:19:03.485 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.485 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.485 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.485 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.485 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.485 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\MountPointManager explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 2424) - 21:19:03.496 Pipe (U) \Device\MountPointManager explorer.exe (9064, 5268) - 21:19:04.103 ComClass (U) {3EEF301F-B596-4C0B-BD92-013BEAFCE793} Desktop Undo Manager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) (2) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\HarddiskVolume5 explorer.exe (9064, 11560) - 21:19:04.134 Pipe (U) \Device\MountPointManager ```