You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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:
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.
The text was updated successfully, but these errors were encountered:
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).
AzureKeyVaultExplorer/Vault/Explorer/ActivationUri.cs
Line 91 in 394b79c
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.
The text was updated successfully, but these errors were encountered: