Frequent ERROR_SHARING_VIOLATION on vhdx

[ScoutmanPt]

Windows Version

Microsoft Windows [Version 10.0.26100.2605]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps

The issue can be reproduced like this :

• Using window terminal , start the wsl distribution
• In another window in PowerShell type "wsl --export .\export.vhdx --vhd"

Expected Behavior

a .\export.vhdx file should be created

Actual Behavior

An error pop's up "The process cannot access the file because it is being used by another process. Error code: Wsl/Service/ERROR_SHARING_VIOLATION" and the export simply dont work

For the export to work we need to wsl --shutdown

I've tried this in 4 machines and the behavior is always the same

Diagnostic Logs

export in Tar doesnt have any issue

Im building a software that is using WSL2 and recently got blocked with this ( cant export instances to vhdx).

Im changing my software to do export vhdx... by actualy copying the original file.

This is kind of ... ridiculous, but it works .
... and i dont need to wsl --shutdown

[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:

• ERROR_SHARING_VIOLATION with --export --vhd (#10737), similarity score: 0.86
• wsl tar export gets stuck at 21GB. VHD export fails with 0x80070017 (#8917), similarity score: 0.73
• WSL Export Failure. Error code: Wsl/Service/WSL_E_EXPORT_FAILED (#9382), similarity score: 0.72
• Error code 0x800704d4 when export WSL (#10058), similarity score: 0.72
• unmounted WSL instance, cannot remount. (#9883), similarity score: 0.71

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

[microsoft-github-policy-service]

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!

[crramirez]

There is no need for logs, the issue is perfectly reproducible, and shouldn't be closed