Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The application installs itself under a different folder than it's expected by the application itself #39

Open
maeof opened this issue May 21, 2021 · 0 comments

Comments

@maeof
Copy link

maeof commented May 21, 2021

I have noticed that at least on Windows 10 the one-click application installer installs VaultExplorer at a different folder than it's expected by the application itself (there's a hardcoded path in the code which nowadays does not match to the fact installation directory).

string appref_ms = Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.StartMenu), "Programs", "Microsoft Corporation", "VaultExplorer.appref-ms");

I. e.
When you run the application using vault:// protocol, the error is being thrown and it states that it cannot find the file in
AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Microsoft Corporation\VaultExplorer.appref-ms
however it installs automatically under
AppData\Romaing\Microsoft\Windows\Start Menu\Programs\VaultExplorer\VaultExplorer.appref-ms
instead.

I troubleshoot this exact error via editing the registry. I simply set the path which is saved in the Registry correctly at least in Windows 10 making the vault:// protocol to work properly:

REG ADD HKCU\Software\Classes\vault\shell\open\command /t REG_EXPAND_SZ /d "\"C:\windows\system32\rundll32.exe\" C:\windows\system32\dfshim.dll, ShOpenVerbShortcut %APPDATA%\Microsoft\Windows\Start Menu\Programs\VaultExplorer\VaultExplorer.appref-ms|%1" /F

I did not make a pull request just yet because I am not quite sure if changing the hardcoded path to a new one is sufficient enough, therefore a more in depth look would be really appreciated. I assume that ideally it should grab the installation path of itself dynamically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant