Skip to content

Docker Desktop WSL Engine fails to start due to /dev/sdd being in use #748

Open

Description

@ishuwahane

Bug report

Description

Docker Desktop is unable to start the Linux/WSL engine on my Windows computer.

When I start Docker Desktop, I get the error "Docker Engine stopped unexpectedly."

The main error message is:

/dev/sdd is apparently in use by the system; will not make a filesystem here!

The error occurs while Docker Desktop is bootstrapping its WSL environment and provisioning the data disk.

Steps I tried

  1. Restarted Docker Desktop.
  2. Ran wsl --shutdown in PowerShell.
  3. Restarted Windows.
  4. Ran wsl --update; it reported that WSL is already up to date.
  5. Checked wsl --list --verbose and wsl --status.
  6. Collected Docker diagnostics, but the engine still fails to start.

Expected behavior

Docker Desktop should start its Linux/WSL engine successfully.

Actual behavior

Docker Desktop stops unexpectedly during WSL initialization because the data disk appears to be in use.

Diagnostic ID

49087A8F-6AA7-4827-92D3-BBBBC8078CD8/20261015153810

Please help me resolve this issue without losing my Docker data.

Platform

Windows

Version information

Windows OS with WSL 2.
Docker Desktop version: 29.8.2 (Docker CLI reported version).
Docker Engine fails to start.
Error: `/dev/sdd is apparently in use by the system; will not make a filesystem here!`

Commands tried:
`docker version`
`docker info`
`wsl --version`
`wsl --list --verbose`
`wsl --status`

Docker diagnostics completed, but the engine still fails to start.

Diagnostics ID

49087A8F-6AA7-4827-92D3-BBBBC8078CD8/20261015153810

Activity

  1. added theissue type on Oct 15, 2026
  2. voonyee commented on Oct 20, 2026

    @voonyee
    Collaborator

    Hi, and thanks for sending the diagnostics.

    The likely underlying cause is that your C: drive is almost full, with only about 200 MB free. Docker keeps its data on that drive, and when it runs out of room the Docker engine stops responding, and restarting it afterwards gets stuck.

    To rule out the issue is not due to low disk space. Can you close Docker Desktop, free up several GB on your C drive (ideally 10 GB or more). Then, start Docker Desktop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions