Windows Server 2016 AWS EC2实例启用WSL遇未知特性错误及咨询

Hey there, let's tackle this issue you're facing with enabling WSL on your AWS EC2 Windows Server 2016 instance. First, let's break down how to confirm support and walk through fixes for the error.

Step 1: Verify if your instance supports WSL #

Windows Server 2016 only supports WSL 1, and it has strict prerequisites. Here's how to check:

• Check your Windows Server version:
  Open PowerShell as admin and run winver. You need to be on Windows Server 2016 Anniversary Update (version 1607, OS build 14393) or later. WSL was first introduced in this update—older builds won't have the feature at all.

• Confirm virtualization support:
  Most modern AWS EC2 instance types (like t2, t3, m5, c5) support hardware virtualization, which is required for WSL 1. To double-check:

  1. Run systeminfo in PowerShell.
  2. Look for the "Hyper-V Requirements" section—ensure "Virtualization Enabled In Firmware" shows Yes.
     Alternatively, cross-reference your instance type details in the AWS EC2 console to confirm virtualization support.

• Check if the feature exists in your AMI:
  Some custom AWS AMIs might strip out optional Windows features. Run this command in admin PowerShell to list available Linux-related features:

  DISM /online /get-features | findstr /i linux
  

  If Microsoft-Windows-Subsystem-Linux doesn't appear in the results, your AMI likely doesn't include this feature.

Step 2: Methods to enable WSL (if supported) #

If your instance meets the prerequisites, here's how to get WSL up and running:

Option 1: Enable via PowerShell (online) #

1. Open PowerShell as Administrator.
2. Run the command:

   Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
   

3. When prompted, restart your EC2 instance.
4. After reboot, install a Linux distribution. Since Windows Server 2016 lacks the Microsoft Store, download the distro package manually (e.g., Ubuntu) using Invoke-WebRequest, then run the package to complete setup.

Option 2: Fix missing feature errors #

If you still get the "Feature name unknown" error on a supported build:

• Install Windows Updates: Ensure your Server 2016 has all cumulative updates installed, especially the Anniversary Update (KB3176936) and later patches. Missing updates can break feature detection.
• Repair system components: Run this command to fix corrupted system files, then retry enabling WSL:

  DISM /Online /Cleanup-Image /RestoreHealth
  

• Offline installation: If online enabling fails, download the WSL feature cab file for Windows Server 2016, then install it via DISM:

  DISM /online /add-package /packagepath:C:\path\to\Microsoft-Windows-Subsystem-Linux-Package.cab
  

Option 3: Switch to an official AMI #

If your custom AMI is missing the WSL feature entirely, spin up a new EC2 instance using the official Windows Server 2016 AMI (provided by AWS/Microsoft) instead of a third-party or modified AMI. This ensures all optional features are present by default.

Important Note #

Keep in mind that Windows Server 2016 only supports WSL 1. WSL 2 requires Windows Server 2019 or later, or Windows 10 1903+. If you need WSL 2 functionality, you'll need to upgrade your instance to a newer Windows Server version.

内容的提问来源于stack exchange，提问作者Anthony Kong