Hive: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths I guess these are supposed to be under HKCU now?
#Windows r command cannot find path windows#
The existing entry for Windows Terminal under HKEY_LOCAL_MACHINE was working fine, so I left it where it was. (Windows Terminal Preview is still broken in this regard, but I just wanted to be able to get working again). from the Windows Explorer address bar to invoke vanilla Windows Terminal. So, I renamed it from wt.exe to wtp.exe, just so that it wouldn't interfere with my use of wt -d. I saw that Windows Terminal Preview was "hogging the spotlight" by having it configured under HKEY_CURRENT_USER. HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths, HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths, and The one for Windows Terminal was turned on, and the one for Windows Terminal Preview was turned off. The settings in the "App Execution Aliases" panel looked right. I was trying to invoke vanilla Windows Terminal. I have the preview installed, but I'm not using it at the moment. from the address bar in Windows Explorer was broken completely, with the same error dialog from Windows Terminal Preview in the original post. ^^ this was quite a helpful clue, have both Windows Terminal Preview and Windows Terminal, both installed via the store. If Windows needs a Registry key in App Paths, then perhaps it should keep the per-user key always synchronized with the app execution aliases, and not create the per-machine key.įWIW I do not see a wt.exe key under HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths, but I do see one under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths. If I disable the skype.exe app execution alias and type skype.exe in the Windows+R run box or in the File Explorer address bar, then I get a similar access-denied dialog box, so this is not specific to Windows Terminal. If I disable both wt.exe app execution aliases, then wt in File Explorer opens in my Web browser.If I enable the wt.exe app execution alias of Windows Terminal, then wt in File Explorer runs Windows Terminal.If I enable the wt.exe app execution alias of Windows Terminal Preview, then wt in File Explorer runs Windows Terminal Preview.If I rename the Registry keys, then the results change: Those Registry keys stay there when I enable or disable the wt.exe app execution aliases. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe.HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe.
![windows r command cannot find path windows r command cannot find path](https://user-images.githubusercontent.com/54781138/103865532-63598780-50d5-11eb-8ec7-7c77c6117a93.png)
#Windows r command cannot find path install#
When I install Windows Terminal Preview, AppXSvc creates the following Registry keys: ? In this case though, I shouldn't expect wt to work anyway. If I disable both wt.exe app execution aliases, then wt in File Explorer shows the access-denied dialog box.If I enable the wt.exe app execution alias of Windows Terminal, then wt in File Explorer shows the access-denied dialog box.If I enable the wt.exe app execution alias of Windows Terminal Preview, then wt in File Explorer starts Windows Terminal Preview.