Nov 24 2020 02:40 PM
Nov 24 2020 02:40 PM
Just getting involved with Insider Preview...upgraded 2019 Datacenter (latest official release) to 20262. After the upgrade, downloaded and ran the Linux Kernel update package. When running WSL commands from the command-line, almost every command I run returns the same output that wsl --help enumerates. If I run wsl --set-default-version 2, it enumerates the help context. Did I miss a step to get this to work or is this a known bug?
Feb 14 2021 03:23 AM
I see, but there wasn't any new LTSC version of server released since WS2019 (1809), so it is clear that WSL2 was released only in the SAC.
AFAIK the WS2022 is being developed in the same cycle as the Windows 10 and Windows Server 21H2.
If that is true, there is quite a big chance WSL2 will be part of the WS2022, when released.
Well, unless the product team decides to remove it, not include it or simply not support it.
If nothing goes wrong the WS2022 will be here in few months, so there isn't much time left for the decision to be made.
When it will be announced what will be part of the LTSC and what will be deprecated?
Feb 14 2021 12:48 PM
@Mary HoffmanWe need a proper desktop environment, and CUDA support on a command line (e.g. for tensorflow or Docker or other Linux command line applications that need GPU acceleration). So we need WSL2. Strangely, Microsoft offers this option on Windows 10 but not Windows Server. (At the same time, Windows 10 and Windows 10 Pro for Workstation do not allow multiple users to logon simultaneously, so we cannot use them). There was a glimmer of hope with WSL2 support in the early vNext versions of Windows Server 2022, so we started using it, tolerating all the bugs. Now, Microsoft appears to be dropping the ball again, by dropping WSL2 support from Windows Server LTSC entirely... I am not sure why such strange decisions are being made. If we want multiple users + a desktop environment + CUDA on a command line, we are out of luck. Microsoft is leaving us without any option here, other than a full Linux desktop.
Feb 16 2021 08:17 AM - edited Feb 16 2021 08:20 AM
IMHO it could be technically possible to release a patch of the Microsoft-Windows-Security-SPP-Component, where AFAIK the timebomb lives, specifically for this build, but don't put much hope on MS doing it.
To be honest I would be happier if they would rather fix it for the builds coming.
Feb 16 2021 08:25 AM
Feb 19 2021 11:25 AM
I don't think this is quite right. WSL(1) was indeed available in Windows Server 2019 LTSC and I was able to use it perfectly fine. WSL2 on the other hand wasn't, because it simply did not exist back then yet.
Also, WSL2 was backported to Windows 10 Versions 1903 and 1909 a while ago (WSL 2 Support is coming to Windows 10 Versions 1903 and 1909), but not the Windows Server 2019 LTSC, which is based on Windows 10 version 1809.
WSL2 then worked perfectly for the first early LTSC preview builds, but then suddenly stopped working once the flighting branch was changed to "fe_release[_server]" in build 20246 onwards. Main Windows 10 Insider Preview also switched branches there (Announcing Windows 10 Insider Preview Build 20246 | Windows Insider Blog). WSL1 however appears to continue to work just fine.
I had opened a GitHub issue about this a while ago: WSL 2 broken on Windows Server Preview (since change to fe_release branch) · Issue #6301 · microsoft...
Mar 21 2021 01:24 PM
@LubomirH I can verify that build 20313 it is still broken. I landed here trying to figure out what had gone wrong and what the triage was. I'm in the same boat as you as my working WSL2 compatible version expired on 1/31 and now won't start up.
This is frustrating as all get out.
Apr 02 2021 06:04 AM
If anybody hoped it is fixed in the build 20324, rest assured it isn't.
PS C:\Users\Administrator> wsl --set-default-version 2
still just outputs the same as the command bellow
and doesn't switch to mode 2
PS C:\Users\Administrator> wsl --status Default Version: 1 Windows Subsystem for Linux was last updated on 4/2/2021 The Windows Subsystem for Linux kernel can be manually updated with 'wsl --update', but automatic updates cannot occur due to your system settings. To receive automatic kernel updates, please enable the Windows Update setting: 'Receive updates for other Microsoft products when you update Windows'. For more information please visit https://aka.ms/wsl2kernel. Kernel version: 5.4.72
Apr 02 2021 08:24 AM