--import-in-place does not invoke plugin WSLPluginAPI_OnDistributionRegistered

[jxy-s]

Windows Version

Microsoft Windows [Version 10.0.22631.4460]

WSL Version

2.3.24.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1-2

Distro Version

No response

Other Software

No response

Repro Steps

1. Run wsl --import-in-place Ubuntu C:\Users\User\Desktop\Ubuntu-24.04-LTS-x86_64.vhdx
   • Observe that WSLPluginAPI_OnDistributionRegistered is not invoked
2. Check and observed that the distribution is in fact registered: wsl --list
3. Run wsl --distribution Ubuntu (checking if the distribution registration callout is invoked later)
   • Observe that the WSLPluginAPI_OnDistributionRegistered is not invoked
   • Observe that WSLPluginAPI_OnDistributionStarted is invoked without any prior WSLPluginAPI_OnDistributionRegistered
4. Run wsl --unregister Ubuntu
   • Observed that the OnDistributionUnregistered is invoked

In contrast, using --import invokes the distribution registered plugin callout immediately. This behavior means that using --import-in-place does not provide visibility of a distribution being registered to the plugin. The plugin is only informed of a distribution being unregistered when --import-in-place is used. Also note that --import invokes the plugin callout immediately, it does not require the distribution be started.

Expected Behavior

The --import-in-place command should result in WSLPluginAPI_OnDistributionRegistered being invoked just as --import does.

Actual Behavior

The --import-in-place command never notifies the plugin of distribution registration.

Diagnostic Logs

No response

[github-actions]

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 [email protected] 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:

• wsl --import-in-place doing nothing (#9576), similarity score: 0.71

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

[jxy-s]

/emailed-logs

[github-actions]

Diagnostic information

Found '/emailed-logs', adding tag 'emailed-logs'