WSL: Active directory and/or Group policy not compatible with WSL 1/2 in 2004 release

Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.

If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.

Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues. Please direct all Windows crashes and security issues to secure@microsoft.com. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".\

See our contributing instructions for assistance.

Please fill out the below information:

  • Your Windows build number: (Type ver at a Windows Command Prompt) Microsoft Windows [Version 10.0.19041.264]
  • What you’re doing and what’s happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)

PS C:\WINDOWS\system32> wsl --set-default-version 2 WSL 2 måste uppdateras enligt kernelkomponenten. Mer information finns på https://aka.ms/wsl2kernel PS C:\WINDOWS\system32> wsl --list --verbose NAME STATE VERSION Ubuntu-18.04 Running 1 PS C:\WINDOWS\system32> wsl --set-version Ubuntu-18.04 2 Conversion in progress, this may take a few minutes… For information on key differences with WSL 2 please visit https://aka.ms/wsl2 Det går inte att hitta sökvägen. ‘(unable to find path)’

  • What’s wrong / what should be happening instead: The Ubuntu-18.04 instance is a WSL 1 installation from Windows 1909 and installed via the server method outside of the system disk on its own disk. It has been working perfectly for a year as far as I can tell and it is working now in Windows 2004. Is the upgrade procedure using a hardcoded path? Is there a way to specify an alternative path?

  • Strace of the failing command, if applicable: (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here).

  • For WSL launch issues, please collect detailed logs.

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 17 (1 by maintainers)

Most upvoted comments

Confirmed after a second clean install of Windows 2004. I had a hope that the WSL 2 upgrade package was prerelease and introduced telemetry dependencies. Unfortunately this isn’t the case. Even if I avoid installing the WSL 2 upgrade, I cannot create new WSL 1 or WSL 2 instances as an AD user. However, now I can continue to use WSL 1 with my local dummy install-account even after joining the computer to AD, which somewhat resembles my original upgraded Windows 1909 with an Ubuntu-1804 instance. I shouldn’t have touched it as I now have to login to a local temporary account to use WSL.