Wsl/Service/CreateInstance/0xd0000034

[mohilmakwana31]

Windows Version

Microsoft Windows [Version 10.0.26100.7171]

WSL Version

2.6.1.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2-1

Distro Version

No response

Other Software

Docker Desktop version: 4.51.0

Yesterday I tried opening Docker Desktop and it failed to start. After checking online, I found that WSL seems to be crashing. Running WSL shows this error:

Error: 0xd0000034
Error code: Wsl/Service/CreateInstance/0xd0000034

What I’ve tried

I found suggestions mentioning that Virtual Machine Platform and Windows Hypervisor Platform must be enabled.

• Virtual Machine Platform was already enabled
• I enabled Windows Hypervisor Platform manually
• Restarted the system → Issue still persists

Next, I tried:

• Deregistering the WSL distribution
• Uninstalling WSL
• Reinstalled WSL
• Reinstalling Ubuntu
• Reinstalling Docker Desktop

But I am still facing the same error whenever WSL tries to start.

Logs

I’ve attached the WSL logs for reference:
WslLogs-2025-12-04_16-24-37.zip

Repro Steps

wsl -d Ubuntu

Or

Start the Ubuntu Terminal application

Expected Behavior

Ubuntu terminal open and presents running terminal

Actual Behavior

Error: 0xd0000034
Error code: Wsl/Service/CreateInstance/0xd0000034

Diagnostic Logs

No response

[github-actions]

Diagnostic information

Detected appx version: 2.6.1.0
Detected user visible error: Wsl/Service/CreateInstance/0xd0000034

[Dev4YM]

First, are u sure Virtualization is enabled in ur BIOS?

To check, open Task Manager, go to Performance Tab, then CPU, u should see the Virtualization down there and should say "Enabled"

[mohilmakwana31]

Thanks for the response @YousefTurky
I checked in task manager as you suggested and it is enabled.

[Dev4YM]

Thanks, i just wanna check if ur device have things like:

1. 3rd-party antivirus (Norton, Kaspersky, Avast, etc.)
2. Backup tools that snapshot .vhdx files in real time
3. Disk encryption beyond BitLocker

If so, Try temporarily disabling them and starting Ubuntu again.

If it didn't solve, then this suggests a physical disk or WSL data disks issue.

[OneBlue]

@mohilmakwana31: This is the root cause of the failure:

Microsoft.Windows.Lxss.Manager	Error	12-04-2025 02:56:39.347	"code: 	
failurecount: 	11
file: 	C:\__w\1\s\src\windows\common\filesystem.cpp
function: 	
hr: 	0xD0000034
linenumber: 	983
message: 	Path: \Device\P9Rdr
threadid: 	21828
type: 	0"	C:\__w\1\s\src\windows\common\filesystem.cpp			5996	21828	2		00000000-0000-0000-0000-000000000000		

Usually this is caused by AV / security software so indeed disabling antivirus should solve this.

[mohilmakwana31]

Thanks, i just wanna check if ur device have things like:

1. 3rd-party antivirus (Norton, Kaspersky, Avast, etc.)
2. Backup tools that snapshot .vhdx files in real time
3. Disk encryption beyond BitLocker

If so, Try temporarily disabling them and starting Ubuntu again.

If it didn't solve, then this suggests a physical disk or WSL data disks issue.

Hi @Dev4YM,
Thanks for the response, and apologies for the delayed reply. I was away from my system for a few days.

I can confirm that I am not using any third-party antivirus.
The same applies to the second and third points you mentioned.

Regarding the last point, I wanted to check if there is any possibility of a WSL disk related issue.

[mohilmakwana31]

@mohilmakwana31: This is the root cause of the failure:

Microsoft.Windows.Lxss.Manager	Error	12-04-2025 02:56:39.347	"code: 	
failurecount: 	11
file: 	C:\__w\1\s\src\windows\common\filesystem.cpp
function: 	
hr: 	0xD0000034
linenumber: 	983
message: 	Path: \Device\P9Rdr
threadid: 	21828
type: 	0"	C:\__w\1\s\src\windows\common\filesystem.cpp			5996	21828	2		00000000-0000-0000-0000-000000000000		

Usually this is caused by AV / security software so indeed disabling antivirus should solve this.

Thanks for the response @OneBlue
I don’t have any external antivirus on my device except Windows Defender.

[Dev4YM]

@mohilmakwana31 Thanks for confirming that none of the antivirus, backup tools, or extra disk-encryption scenarios apply. Since those are clear, it’s looking more likely that the problem may be related to the WSL virtual disks themselves or the storage layer underneath.

To move forward, could you let GPT guide you through checking the health of your disk and verifying whether your WSL VHDX files are repairable or need to be recreated? This will help narrow down whether the issue is with the virtual disks or the actual drive.

Before proceeding, please make sure to mention to GPT if any of the following apply, because they can be important:

1. Your WSL distro is stored on a non-default drive
2. You’re using OneDrive, Dropbox, or any sync service on your user profile
3. You have BitLocker enabled on the drive
4. You recently had power loss, blue screens, or unexpected shutdowns
5. The disk is showing unusual behavior (slow I/O, freezes, SMART warnings)

These details can change the recommended steps.

Let GPT walk you through the diagnostic steps so we can pinpoint the exact cause. If ur unsure or need help on any step, I'll be happy to help u.