Intermittent Crashes with Error 0xd0000225 During Buildbot Operations (tar Extraction, etc.)

[mendax0110]

Windows Version

Microsoft Windows [Version 10.0.19045.4474]

WSL Version

2.4.13.0

Are you using WSL 1 or WSL 2?

• [ ] WSL 2
• [x] WSL 1

Kernel Version

4.4.0-19041-Microsoft

Distro Version

Ubuntu 22.04

Other Software

WSL version: 2.4.13.0 Kernel version: 5.15.167.4-1 WSLg version: 1.0.65 MSRDC version: 1.2.5716 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.19045.4474 tar (GNU tar) version: 1.34 buildbot-worker version is 4.2.1 Twisted version is 24.3.0

Repro Steps

We’re encountering increasingly frequent issues with WSL1 on our Windows-based build infrastructure. While I cannot share logs due to restrictions from my employer, I can describe the problem in detail.

In the past few weeks, we've seen intermittent failures in our Buildbot CI system that appear to be caused by WSL1. The failures occur during common operations such as:

Cleaning up environments Cloning Git repositories Extracting .tar archives

The affected build steps crash with the following error:

Error: 0xd0000225
Error code: Wsl/Service/0xd0000225

We've verified disk and memory health — no underlying hardware issues. There’s no clear pattern, but frequency seems to be increasing. WSL2 is currently not an option due to compatibility constraints in our environment.

I attempted to locate this error code/message (0xd0000225 / Wsl/Service/0xd0000225) in both the WSL codebase and broader documentation or developer forums, but found no references or documentation on what this error code means or what might trigger it.

If anyone on the team recognizes this error code or can point to its meaning or origin, that would be incredibly helpful for narrowing down the root cause.

Expected Behavior

There should be no random error code while we are extracting or doing other operations.

Actual Behavior

Error occurs in different steps of the process, but most frequently during tar extraction.

Always produces the same error code (0xd0000225) regardless of the failing step.

Happens intermittently, not every build.

Diagnostic Logs

No response

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

[mendax0110]

/question

[github-actions[bot]]

Diagnostic information

Found '/question', adding tag 'question'

[OneBlue]

/logs

[microsoft-github-policy-service[bot]]

Hello! Could you please provide more logs to help us better diagnose your issue?

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 scipt will output the path of the log file once done.

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.

Thank you!

[microsoft-github-policy-service[bot]]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!