[FileVoyager (Author)]

Hi,

FileVoyager 23.5.7 is now live and has Single Instance capability.
Even if command line parameters are passed to a new instance that is about to be closed, the parameters will be received and processed by the Single Instance functionality in the current open instance.

Thanks Charles for the active contribution 👍

[FileVoyager (Author)]

Hi Charles,

Good news: I’ve implemented the Single Instance capability in FileVoyager a couple of days ago.
I’ll probably release a version this weekend with this.

Stay tuned!

[FileVoyager (Author)]

Hi Charles,

No it’s not foreseen in the app, but there’s an easy way to do it by yourself:

• Go to the Startup folder where you added the shortcut to FileVoyager
  • you can go there by navigating to %AppData%\Microsoft\Windows\Start Menu\Programs\Startup in your favorite file manager, or a more recent alternative which consist of navigating to Shell:Startup
• Normally, you should have a shortcut to FileVoyager. Right click the shortcut and open Properties
• In the Properties windows, change the value of the Run field to Minimized. Then apply the change.
• From now on, FV will start up with a new Windows session, in minimized.

On my side, I add a to do list item in my backlog to implement this feature out-of-the-box

 

[FileVoyager (Author)]

Hi Charles,

While I may not be able to address the root cause of your problem, I do have a workaround to suggest. Have you heard of AutoHotkey? This application allows you to automate complex tasks using keyboard combinations.

I tested overriding the Win+E pair with AutoHotkey and it worked like a charm on my machine. If you’d like to give it a try, here are the steps:

1. Go to https://www.autohotkey.com and download the V2.0 (don’t search it on google because some fake ones are better referenced)
2. Install the software and it will start up on the Dash
3. Select “New script”, give it a name, optionally select “Minimal for v2”, and click “Create” (by default, the file will be saves in your Document folder in an AutoHotkey subfolder)
   
4. Open the .ahk file from the folder mentioned above in your preferred file editor (notepad, notepad++, PSPad, SublimeText, …)
5. add the following line after the default one (if any):
   #e::run “C:\Program Files (x86)\FileVoyager\FileVoyager.exe”
   (Note: the command between quotes is here pointing to FileVoyager, but you can choose any program you want and add command-line parameters as well)
6. Save the file, but keep it open in your editor so that you can quickly make changes if necessary.
   (Note: each time you make changes to the file, you must save it and double-click it from your preferred file manager to apply the changes. AutoHotkey will ask you if you want to override – accept this.

[FileVoyager (Author)]

Hi Charles,

Are you aware that on the left of each pane, there is a Drive Panel ? If yes, I suppose you would like to have the drives in the treeview anyways.
I’m not against. Basically, I wanted to keep the hierarchy as basic as possible, knowing that the Root in Windows is the Desktop virtual folder. But I appreciate the idea to pimp it a bit. I add your suggestion to my to do list 👍

[FileVoyager (Author)]

Hi Charles,

After some research, I propose you do this:

1. Launch Regedit.exe
2. Navigate to HKEY_CURRENT_USER\SOFTWARE\Classes\CLSID\{52205fd8-5dfb-447d-801a-d0b52f2e83e1}
3. Delete the key

When done, re-execute the .reg script you created based on the initial post of this thread.

My assumption is that the “HKEY_CURRENT_USER\SOFTWARE\Classes\CLSID\{52205fd8-5dfb-447d-801a-d0b52f2e83e1}\shell\open” still refers to the default behaviour (File Explorer) and is executed prior to falling back on the “opennewwindow” key. By resetting the whole CLSID 52205fd8-5dfb-447d-801a-d0b52f2e83e1, we can start on a clean base.

If this doesn’t work, I must confess I don’t have any other idea 😶

[FileVoyager (Author)]

Hi Charles,

Thank you for your kind words and welcome to this forum!

To answer your question, I considered the possibility of replacing the default File Explorer. However, replacing File Explorer is challenging and can compromise some core Windows’ functionalities.

A better approach, as you suggested, would be to override the [win]+[E] shortcut.
I came across an easy and safe way to do it by reading a StackExchange.com article.

It is highly likely that I will implement this approach in FileVoyager in the futur
Alternatively, you can also follow the steps below:

1. In your favorite text editor, create a .reg file. Say FileVoyagerWinE.reg
2. copy and paste these commands into the file :
   

   Windows Registry Editor Version 5.00
   [HKEY_CURRENT_USER\SOFTWARE\Classes\CLSID\{52205fd8-5dfb-447d-801a-d0b52f2e83e1}]@=””
   HKEY_CURRENT_USER\SOFTWARE\Classes\CLSID\{52205fd8-5dfb-447d-801a-d0b52f2e83e1}\shell]
   HKEY_CURRENT_USER\SOFTWARE\Classes\CLSID\{52205fd8-5dfb-447d-801a-d0b52f2e83e1}\shell\open]
   HKEY_CURRENT_USER\SOFTWARE\Classes\CLSID\{52205fd8-5dfb-447d-801a-d0b52f2e83e1}\shell\opennewwindow]
   [HKEY_CURRENT_USER\SOFTWARE\Classes\CLSID\{52205fd8-5dfb-447d-801a-d0b52f2e83e1}\shell\opennewwindow\command]@=”C:\\Progam Files (x86)\\FileVoyager\\FileVoyager.exe”
   “DelegateExecute”=””

3. Replace the path, in bold above, with the path on your system. Be sure to use double backslashes “\\” instead of a sigle one “\”.
4. Execute FileVoyagerWinE.reg

No need to reboot, your [win]+[E] shortcut is launching FileVoyager now.

To reset the default [win]+[E] behaviour, just delete the CLSID key from your registry:

1. Launch Regedit.exe
2. Navigate to HKEY_CURRENT_USER\SOFTWARE\Classes\CLSID\{52205fd8-5dfb-447d-801a-d0b52f2e83e1}
3. Delete the key

No need to reboot, your [win]+[E] shortcut is launching the default File Explorer.

[FileVoyager (Author)]

Hi BigB,

1. Unfortunately, there is currently no setting available to specify which pane should be in focus when the application starts up.
2. It appears that the feature is no longer operational. I have gone ahead and added a bug report to my issue tracker.
3. Indeed, the address bar is the element that indicates the currently focused pane by subtly changing color.
   What would you suggest to better indicate the focused pane ?

[FileVoyager (Author)]

Hi Key Bored,

version 22.11.13 is now live and fixes your issue. Thanks for having reported this!

[FileVoyager (Author)]

Hi Key Bored,

I just tested on a High DPI device and I confirm this issue. Placed as high priority on my to do list.
I will post on this discussion when the fix is online and ready to be downloaded.

[FileVoyager (Author)]

Hi Compupix,

First of all, let me clarify that it’s not a FileVoyager behaviour. It’s driven by Windows.

If you are using Windows 10, there’s a setting where you can configure the action Windows will take when opening a removable media. Search for “Autoplay” in your start menu, you’ll land on this screen:

Select “Take no action” in the drop down lists and you will not be nagged anymore.

[FileVoyager (Author)]

Hi Pseudo Kasiopee,

The favorites are the only stuff you loose ?
You loose them only after computer restart ? not after FileVoyager restart ?

The most common reasons why users loose their config is generally because they downloaded a Portable version and installed it in a protected folder (eg c:\Program files). By running in a protected folder, saving of settings is prevented.

The avoid this, install the “setup” version of FileVoyager. With those versions, settings are saved in AppData, which is not heavilly protected by Windows

[FileVoyager (Author)]

Hi kasiopee,

There are several potential causes. It could be a Shell Extension installed by another program that leads FileVoyager to the crash.

Can you identify a pattern of what you’re doing before it crashed ?

eg: Open the context menu, open the Thumb 3D view, navigate a specific disk or folder

[FileVoyager (Author)]

Hi Martin,

Any improvement after restarting the app ? If you use Portable version, make sure to execute it from a folder that is not restricted.

[FileVoyager (Author)]

Hi dhruv2193!

Drive letters in Windows are often partitions. Do you mean you would like a low-level search that finds files that are not in a mapped drive ? If yes, I’m afraid I have no clue how to do this… If you have a hint, I’m curious to know

[Author]

Posts