terminal: when i open the windows terminal ,it`s show [error 0x80070002 when launching `powershell.exe']

It seems that your PATH environment variable may be damaged and not contain the Windows PowerShell directory. @pc-chin is your python executable named python3.8.exe or is it named python3.exe? If it is python3.exe, you will never be able to call it python3.8 and have it work properly.

I have the same problem. I know that my PATH variables are damaged, WT was not working before 0.8.10091.0

I think in some windows update my PATH got messed up. I have faced many problems because of it. Currently I cannot reinstall everything, Can we fix the path variables ?

When I try to launch PS from cmd, cmd cannot find PS, but the same is not true for my Windows sandbox env.

I am just hoping to fix my PATH, and use WT easily.

Thanks, Malhar

Edit:

Windows sandbox

My current env

my WT CMD and WSL work correctly in WT

After updating my PATH with %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\ at the top of the list, it seems to be working now My CMD can call PS now !

WT runs PS

This bug still exists and should be reopened.

It seems that your PATH environment variable may be damaged and not contain the Windows PowerShell directory.

@pc-chin is your python executable named python3.8.exe or is it named python3.exe? If it is python3.exe, you will never be able to call it python3.8 and have it work properly.

I have the same problem. I know that my PATH variables are damaged, WT was not working before 0.8.10091.0

I think in some windows update my PATH got messed up. I have faced many problems because of it. Currently I cannot reinstall everything, Can we fix the path variables ?

When I try to launch PS from cmd, cmd cannot find PS, but the same is not true for my Windows sandbox env.

I am just hoping to fix my PATH, and use WT easily.

Thanks, Malhar

Edit:

Windows sandbox

My current env

my WT CMD and WSL work correctly in WT

It seems that your PATH environment variable may be damaged and not contain the Windows PowerShell directory. @pc-chin is your python executable named python3.8.exe or is it named python3.exe? If it is python3.exe, you will never be able to call it python3.8 and have it work properly.

I have the same problem. I know that my PATH variables are damaged, WT was not working before 0.8.10091.0 I think in some windows update my PATH got messed up. I have faced many problems because of it. Currently I cannot reinstall everything, Can we fix the path variables ? When I try to launch PS from cmd, cmd cannot find PS, but the same is not true for my Windows sandbox env. I am just hoping to fix my PATH, and use WT easily. Thanks, Malhar Edit: Windows sandbox My current env my WT CMD and WSL work correctly in WT

After updating my PATH with %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\ at the top of the list, it seems to be working now My CMD can call PS now !

WT runs PS

Have you tried this solution ?

In case this helps someone else.

Installing a preview version of Powershell 7 places the following in the PATH: C:\Program Files\PowerShell\7-preview\preview

Which contains pwsh-preview.cmd not pwsh.exe. So pwsh or pwsh.exe will not work.

Change this to C:\Program Files\PowerShell\7-preview\ and it works fine.

link-preview

Sorry about that. We don’t actually have extensions or the “wt install” command right now. We are tracking that in #4000

i have the same problem when trying to install link-preview,

C:\Users\User>wt install link-preview

and then it goes :

[error 0x80070002 when launching 'install link-preview']

“Windows Powershell” is the name of a profile, not an executable, so you must put -p before it.