Explorer++

There was code added a few months back to navigate up if the current directory is deleted. It should only trigger in those circumstances, though. Does it happen with any directory, or only in specific locations?

This sounds like the same issue as the one described in viewtopic.php?t=1232 and fixed in https://github.com/derceg/explorerplusp ... 87c76bb074. If it is that issue, then using the dev version should fix the problem.

When you set Explorer++ as the default file manager, it changes one of two registry keys: HKEY_CURRENT_USER\Software\Classes\Directory\shell - Used if you change the default file manager for filesystem folders. HKEY_CURRENT_USER\Software\Classes\Folder\shell - Used if you change the default file man...

Past builds weren't very tolerant of issues with the loaded data. That meant that if a saved value had an incorrect or unexpected value, you could end up with a situation similar to the one described here - that is, where the application crashes on startup. It's something I've made changes to recent...

Hi John, are you able to pinpoint exactly where the issue starts? You can download previous dev builds from https://explorerplusplus.com/builds?prefix=dev%2F. Knowing the specific build where the issue appears would be very helpful.

From what I remember when I looked into it a few months back: - When transforming a path like "C:\Users\Username\Downloads" into a shell item, the shell would return a reference to an item on the desktop. - That item wasn't the same as the "Downloads" item that typically appeared...

You can download older dev builds from https://explorerplusplus.com/builds?prefix=dev%2F, with the oldest available build being from August last year.

The latest dev build (1.5.0.2296) appears to work correctly when I extract it to a location, then run it on Windows 8. Are you extracting it to a location where there's an existing config.xml file? Does the application open correctly if you switch back to the default settings? (You can easily do tha...

I have seen a false positive from Defender at least once before. In that case, it was fixed fairly quickly (in less than 24 hours, if I remember correctly). In this case, scanning Explorer++ 1.4.0.2210 with security intelligence version 1.397.1414.0 shows no results, so hopefully it's already fixed.

Thanks, this should be fixed by https://github.com/derceg/explorerplusp ... b85017b259.