[ANNOUNCEMENT] WSL Issue spam - We're on it!

[benhillis]

I'm working through closing the huge influx of spam issues we received in the last day. GitHub does not have the best tools to do this, so my script is taking a while to close each issue.

Thank you for your patience.

[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-wsl-logs.ps1 -LogProfile networking instead, 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 wsl-gh-logs@microsoft.com 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]

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-wsl-logs.ps1 -LogProfile networking instead, 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 wsl-gh-logs@microsoft.com 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'.

[kldhsh123]

Crazy

[benhillis]

eh, it is what it is. not the worst thing in the world to have to write a little python with my coffee on Sunday morning :)

[MoYuan-CN]

If deletion is acceptable, could the script delete the issues entirely instead of just closing them? Closed issues still clutter the list and create unnecessary noise.

[xlionjuan]

Consider this search query as filter?

https://github.com/search?q=%22%E3%80%90%E6%89%A3%3A+63923%E3%80%91%22+OR+%22%E3%80%90%E6%89%A3%3A+78034%E3%80%91%22+OR+%22%E3%80%90%E5%BE%AE%EF%BC%9ABYD9991%E3%80%91%22+OR+%22%E5%94%AE%E5%90%8E%E5%8F%97%E7%90%86%E5%AE%A2%E6%9C%8D%E4%B8%AD%E5%BF%83%282026%29%22+OR+%22%E3%80%905902-869%E3%80%91%22+OR+%22AM882.VIP%22&type=issues&s=created&o=desc&p=3

[Fgaoxing]

@benhillis Please hold on a moment. I'm working on the corresponding script, though I can't guarantee it will work. As a Chinese developer, I just want to do my part, even if it might not be that useful.

[VanillaNahida]

I'm working through closing the huge influx of spam issues we received in the last day. GitHub does not have the best tools to do this, so my script is taking a while to close each issue.

Thank you for your patience.

Good job. 👍

[Fgaoxing]

@benhillis https://api.github.com/search/issues?q=repo:microsoft/WSL%20%22%E6%89%A3%EF%BC%9A63923%22%20OR%20%22%EF%BC%98%20%EF%BC%97%20%EF%BC%92%20%EF%BC%96%20%C2%B7%20%EF%BC%A3%20%EF%BC%A3%22%20OR%20%223764%20%C2%B7%20CC%22%20OR%20%22%EF%BC%92%EF%BC%90%EF%BC%92%EF%BC%96%E4%B8%96%E7%95%8C%E6%9D%AF%EF%BC%8C%E7%90%83%E8%BF%B7%E7%8B%82%E6%AC%A2%EF%BC%81%22%20OR%20%22%E6%89%A3:%2063923%22%20created:2026-03-27..2026-03-29 Use it to retrieve all the issues that have been hacked.

[benhillis]

If deletion is acceptable, could the script delete the issues entirely instead of just closing them? Closed issues still clutter the list and create unnecessary noise.

yep I will be deleting the issues in a second pass, just closing them for now to make sure the script does the right thing.

[VanillaNahida]

eh, it is what it is. not the worst thing in the world to have to write a little python with my coffee on Sunday morning :)

If deletion is acceptable, could the script delete the issues entirely instead of just closing them? Closed issues still clutter the list and create unnecessary noise.

GitHub allows the deletion of Issues. Please refer to the https://docs.github.com/zh/issues/tracking-your-work-with-issues/administering-issues/deleting-an-issue for details.