Enabling ObCaseInsensitive leads to Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureGpu/HCS/ERROR_PATH_NOT_FOUND

Open
#42,184 11 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp

Research direction

Start by reproducing the reported failure with WSL 2 and the ObCaseInsensitive registry setting enabled, then trace the CreateVm/ConfigureGpu path named in the error. The payload does not identify source files or tests, so locate the relevant WSL startup code and check whether the setting changes the path lookup. Done means WSL starts successfully with the setting enabled.

Written by the indexing model from the issue text.

Description

hypervisor-platform wsl2
Windows Version

10.0.26300.9818

WSL Version

3.0.3.0

Are you using WSL 1, WSL 2, or WSLC?
  • WSL 2
  • WSL 1
  • WSLC
Kernel Version

6.18.54.1-1

Distro Version

Current kali-linux

Other Software

WSL version: 3.0.3.0
Kernel version: 6.18.54.1-1
WSLg version: 1.0.79
MSRDC version: 1.2.7391
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26300.9818

Repro Steps
  1. On default configuration Windows 11, install optional Windows feature WSL
  2. Install kali-linux distribution
  3. Reboot
  4. From CMD, run WSL, and note all's well.
  5. Using REGEDIT, change registry HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\kernel dword:ObCaseInsensitive from 0 to 1
  6. Reboot
  7. From CMD, run WSL
Expected Behavior

WSL should start with no error, giving shell prompt.

Actual Behavior

The system cannot find the path specified.
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureGpu/HCS/ERROR_PATH_NOT_FOUND

Diagnostic Logs

No response

Dominant language
C++
Stars
34.4k
Forks
1.9k
Avg merge
1d 23h
Merged PRs (30d)
166

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/WSL

All issues in microsoft/WSL

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.