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

用作为当前目录的以上路径启动了 CMD.EXE。 UNC 路径不受支持。默认值设为 Windows 目录。 #11507

Closed
1 of 2 tasks
LifeJustDLC opened this issue Apr 24, 2024 · 6 comments

Comments

@LifeJustDLC
Copy link

Windows Version

Microsoft Windows [版本 10.0.19045.4291]

WSL Version

0.0.0.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.10.102.1

Distro Version

Ubuntu-20.04

Other Software

No response

Repro Steps

git clone https://github.com/polywock/globalSpeed.git
npm install
npm run build:devFf

Expected Behavior

build

Actual Behavior

npm run build:devFf

globalspeed@1.0.0 build:devFf
export NODE_ENV=development && npm run build:commonFf

'\wsl$\Ubuntu-20.04\home\tom\globalSpeed'
用作为当前目录的以上路径启动了 CMD.EXE。
UNC 路径不受支持。默认值设为 Windows 目录。
'export' 不是内部或外部命令,也不是可运行的程序
或批处理文件。

Diagnostic Logs

No response

Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Copy link

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information
.wslconfig found
appxpackage.txt not found
Found no WSL traces in the logs

Copy link

Diagnostic information
.wslconfig found
appxpackage.txt not found

@LifeJustDLC
Copy link
Author

 .\collect-wsl-logs.ps1
get-appxpackage: C:\Users\tom\collect-wsl-logs.ps1:54
Line |
  54 |  get-appxpackage MicrosoftCorporationII.WindowsSubsystemforLinux -Erro …
     |  ~~~~~~~~~~~~~~~
     | The 'get-appxpackage' command was found in the module 'Appx', but the module could not be loaded due to the
     | following error: [Operation is not supported on this platform. (0x80131539)] For more information, run
     | 'Import-Module Appx'.

@LifeJustDLC
Copy link
Author

didn't install node on wsl. running widows executables silently? what a cool feature I didn't expected at all

@LifeJustDLC
Copy link
Author

remove logs for potential personal info leakage

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