WSL pre-release 2.6.2.0 breaks WSLDVCPlugin

[thendricks0]

WslLogs-2025-11-04_10-35-26.zip

Windows Version

Microsoft Windows [Version 10.0.26200.6901]

WSL Version

2.6.2.0

Are you using WSL 1 or WSL 2?

• [x] WSL 2
• [ ] WSL 1

Kernel Version

6.6.87.2-1

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

• Update WSL from 2.6.1.0 to 2.6.2.0 pre-release using wsl --update --pre-release
• Install any now .desktop file under /usr/share/applications (by uninstalling an app or installing a new app)
• Check startmenu shortcuts

Expected Behavior

• Working shortcuts

Actual Behavior

• WSLDVCPlugin doesn't create new shortcuts in the Startmenu nor does it remove old shortcuts if an application or rather .desktop file is removed from /usr/share/applications
• Taskbar icons are also falling back to the default Linux penguin icon
• Rolling back to 2.6.1.0 restores icons

Diagnostic Logs

If one will tell me where the WSLDVCPlugin logs are generated I will happily supply them.

[github-actions[bot]]

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 in Collect WSL logs for networking issues

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

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to [email protected] with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[github-actions[bot]]

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

Issue was edited and new log file was found: https://github.com/user-attachments/files/23328841/WslLogs-2025-11-04_10-35-26.zip
.wslconfig found
Detected appx version: 2.6.1.0
Found no WSL traces in the logs

[thendricks0]

I just manually updated the WSLg install to 1.0.71 pre-release (extracted system.vhd and WSLDVCPlugin.dll from the release zip to %ProgramFiles%/WSL) so we can rule out that it is a WSLg issue and the icons still work if WSLg is on 1.0.71 and WSL is on 2.6.1.0.

So this is definitely an issue with a change that was introduced in WSL 2.6.2.0.

[OneBlue]

Thank you for reporting this @thendricks0. WSL 2.6.2 indeed updated to wslg 1.0.71. Transferring to wslg for deeper investigation.

[thendricks0]

Yes but with WSL 2.6.1.0 and WSLg 1.0.71 it works fine, so the issue was introduced in the WSL update not in the WSLg update, shouldn't the issue then be located in the WSL repo where I created it?