search

Open-Shell / Open-Shell-Menu

Classic Shell Reborn.
MIT License
6.58k stars 417 forks source link

Explorer → left-hand pane → context menu → "Open in new window" or "Properties" crashes explorer.exe #1873

Open EdStauff opened 3 months ago

EdStauff commented 3 months ago

Describe the bug

Explorer.exe crashes whenever I try to select "Properties" or "Open in new window" from the context menu of a folder in the left-hand (navigation) pane of an Explorer window. This is 100% reproducible, and has been happening literally for years.

Area of issue

Windows Explorer

To reproduce

  1. Open (or activate) a Windows Explorer window.
  2. In the left-hand (navigation) pane, navigate to any folder and select it.
  3. Invoke the context menu (right-click or menu key).
  4. Select either the "Properties" item or the "Open in new window" item.
  5. After about 1 second, explorer.exe crashes. Actual observed "crash" behaviour: • Any open Explorer windows disappear. • The Windows desktop disappears for a second or two, including the task bar. • Process Explorer shows the "explorer.exe" process as having just started a few seconds ago.

Expected behavior

Same behaviour as with a folder in the right-hand Explorer pane.

Open-Shell version

4.4.191

Windows version

10.0.18362.959

Additional context

No response

ge0rdi commented 3 months ago

Explorer.exe crashes whenever I try to select "Properties" or "Open in new window" ...

Please, provide crash dump using this guide.

10.0.18362.959

You should also consider updating Win10 to latest version.

EdStauff commented 3 months ago

Okay, here is the requested crash dump (731MB) and also the console transcript (2KB) from procdump: http://www.mewsic.com/temp/explorer.exe_240319_135238.dmp http://www.mewsic.com/temp/OpenShell_explorer_dump_transcript.txt

ge0rdi commented 3 months ago

I can see the crash happens during WM_RBUTTONDOWN message handling. It goes through CExplorerBHO::SubclassTreeProc in Classsic Explorer, but it is supposed to just ignore it (and pass further).

There is bdhkm64.dll (BitDefender Hooking DLL) further down the stack that sends a message somewhere.

Try to disable BitDefender hooking into Explorer (not sure how to do that as I'm not familiar with Defender). Eventually try to submit the dump to their support. They may be able to tell more.