search

srwi / EverythingToolbar

Everything integration for the Windows taskbar.
Other
9.49k stars 412 forks source link

Bug: Opening a folder runs the same named executable instead #303

Closed Kamilkampfwagen-II closed 2 months ago

Kamilkampfwagen-II commented 1 year ago

Preflight Checklist

EverythingToolbar Version

0.7.4

Windows Version

Windows 10 version 21H2 LTSC

Steps to reproduce

  1. Put a folder.
  2. Put an executable (.exe .bat .cmd) to the same directory.
  3. Rename the executable to the folder name.
  4. Search for the folder using EverythingToolbar.
  5. Open the folder from the search results.

Expected Behavior

Opens the folder in the Windows Explorer.

Actual Behavior

Runs the executable near the folder.

Screenshots

bug

Log output

2023-01-21 21:00:10.6245|INFO|EverythingToolbar started. Version: 0.7.4.0, OS: Microsoft Windows NT 10.0.19044.0| 2023-01-21 21:00:10.7785|INFO|Everything version: 1.4.1|

Additional Information

Everything version: 1.4.1 Windows shell has the same issue.

srwi commented 1 year ago

Very interesting find. Apparently this is the intended behavior of Process.Start. I implemented a workaround for that, which will be available in the next release (after 1.0.0).

Kamilkampfwagen-II commented 1 year ago

Thank you for your effort.

Kamilkampfwagen-II commented 11 months ago

Apparently this issue has reappeared. I am not sure after which release. I am currently on 1.2.0

srwi commented 11 months ago

Thank you, I'll take a look.

srwi commented 2 months ago

I had some time to look into it. It's a really unfortunate behavior of Process.Start that doesn't play well with third-party file browsers that some people are using. Unfortunately I broke the fix again with some changes related to third-party file browsers.