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

Warning 1946 from WSL update to 2.4.13.0 #12759

Closed
1 of 2 tasks
patheikkinen opened this issue Mar 30, 2025 · 6 comments
Closed
1 of 2 tasks

Warning 1946 from WSL update to 2.4.13.0 #12759

patheikkinen opened this issue Mar 30, 2025 · 6 comments

Comments

@patheikkinen
Copy link

Windows Version

Microsoft Windows [Version 10.0.26100.3476]

WSL Version

2.4.13.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

No response

Distro Version

No response

Other Software

No response

Repro Steps

wsl --update

Checking for updates.
Updating Windows Subsystem for Linux to version: 2.4.13.
Warning 1946.Property 'System.AppUserModel.ID' for shortcut 'WSL.lnk' could not be set.

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

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 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
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'.

@patheikkinen
Copy link
Author

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...

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
Appx package is not installed
Found no WSL traces in the logs

@patheikkinen
Copy link
Author

How do you get past that log bot with an install time bug?

@OneBlue
Copy link
Collaborator

OneBlue commented Apr 1, 2025

Thank you @patheikkinen. This is unfortunately a powertoys issue. Fixed by microsoft/PowerToys#37654

@OneBlue OneBlue closed this as completed Apr 1, 2025
@patheikkinen
Copy link
Author

@OneBlue How could it possibly be? I don't have PowerToys installed, as I mentioned in the description.

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

2 participants