Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-opus-4-20250514· AnthropicHugging Face LMArena Human Preference 140K

wsl: Mirrored networking mode is not supported: Windows version 19045.5965 does not have…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Claudeclaude-3-7-sonnet-20250219-thinking-32k’s answer.
  1. User

    wsl: Mirrored networking mode is not supported: Windows version 19045.5965 does not have the required features.

    How to fix that?

  2. Claude Assistant

    This error occurs because mirrored networking mode in WSL requires a newer version of Windows than what you currently have (build 19045.5965). Mirrored networking mode was introduced in Windows 11 build 22621 or later.

    Here are your options to fix this:

    Option 1: Update to Windows 11

    The most straightforward solution is to upgrade to Windows 11 if your hardware supports it. Mirrored networking mode requires Windows 11 version 22H2 (build 22621) or later.

    Option 2: Use NAT mode instead

    If you can't or don't want to upgrade to Windows 11, you can use the default NAT networking mode instead. In your .wslconfig file (located at %USERPROFILE%\.wslconfig), either remove the networking mode setting or explicitly set it to NAT:

    [wsl2]
    networkingMode=NAT
    

    Option 3: Update Windows 10 to the latest version

    While mirrored mode isn't available on Windows 10, you should still update to the latest Windows 10 version for other WSL improvements. Your current build (19045) is Windows 10 22H2, which is the latest major release of Windows 10.

    What is mirrored networking mode?

    Mirrored networking mode provides better network compatibility by mirroring the Windows network interfaces into WSL, allowing features like IPv6 support, better VPN compatibility, and localhost forwarding. However, NAT mode works fine for most use cases.

    If you specifically need the features that mirrored mode provides and can't upgrade to Windows 11, you might need to look for workarounds specific to your use case (like manual port forwarding for localhost access).

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.