Skip to content

SSH handshake failed on Windows 11 Hyper-V - VM receives only IPv6, network adapter not auto-configured #5000

@JJM-System

Description

@JJM-System

CRC fails to establish SSH connection on Windows 11 Hyper-V. VM is created and running but:

  • SSH connection fails: "handshake failed: wsarecv: An existing connection was forcibly closed"
  • VM receives only IPv6 link-local (fe80::...), no IPv4
  • Port 2222 listening but connection refused
  • Root cause: crc setup/start does NOT automatically create/configure network switch and adapter

Environment

Property Value
OS Windows 11 Pro 10.0.26200
CRC Version 2.55.1+6252bc
Hypervisor Hyper-V (HypervisorPlatform Enabled)
CPU Intel Core i7-13850HX
VM State Running (verified via Get-VM)

Actual Behavior

After crc setup and crc start:

  • Get-VMSwitch shows only "Default Switch" (switch "crc" never created)
  • VM has no IPv4 address, only IPv6 link-local

SSH error:

ssh: handshake failed: read tcp 127.0.0.1:50200->127.0.0.1:2222:
wsarecv: An existing connection was forcibly closed by the remote host

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions