-
Notifications
You must be signed in to change notification settings - Fork 871
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
Warning 1946 from WSL update to 2.4.13.0 #12759
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 |
WslLogs-2025-03-30_15-21-20.zip Probably useless but required by policy. btw it looks like the lnk file was updated and everything works so far, so the bug is probably that it emits a warning for no good reason... |
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
|
How do you get past that log bot with an install time bug? |
Thank you @patheikkinen. This is unfortunately a powertoys issue. Fixed by microsoft/PowerToys#37654 |
@OneBlue How could it possibly be? I don't have PowerToys installed, as I mentioned in the description. |
Windows Version
Microsoft Windows [Version 10.0.26100.3476]
WSL Version
2.4.13.0
Are you using WSL 1 or WSL 2?
Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
wsl --update
Unlike a previous issue with similar symptoms, no PowerToys install is involved.
Expected Behavior
Clearly a successful install shouldn't spit out warning 1946.
Actual Behavior
See above.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: