-
Notifications
You must be signed in to change notification settings - Fork 822
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
These group policies prevent WSL installation for some reason #12300
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done. If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here Once completed please upload the output files to this Github issue. Click here for more info on logging View similar issuesPlease 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:
|
I am attaching the logs, but you would do better to recreate the situation yourself. We are talking about a clean system immediately after installation after all. |
Diagnostic information
|
Windows Version
Microsoft Windows [Version 10.0.19044.5131]
WSL Version
0.0.0.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.10.102.1
Distro Version
Ubuntu
Other Software
No response
Repro Steps
wsl --install
Expected Behavior
WSL is installed
Actual Behavior
Disabling each of these policies individually does not cause installation problems. I tried disabling them in pairs (I didn't check all combinations) and they also don't caused installation problems. Only blocking all 6 (Configure Windows Defender SmartScreen occurs 4 times) leads to this problem.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: