[BUG] Linux Node cannot be found after reboot host machine

[jinrongchi]

Describe the bug
The Linux node cannot start running after the machine reboot (due to Windows updates)
Start-AksEdgeNode error states the network interface is missing
Error: rpc error: code = Unknown desc = Endpoint Name Interface not found]

To Reproduce
Steps to reproduce the behavior:

1. Deploy a Single Machine Cluster
2. Reboot (for Windows Updates)
3. Run Command Start-AksEdgeNode -NodeType Linux
4. Exception Caught - The endpoint not found

Expected behavior
The node should restart successfully.
kubectl command should be able to connect the cluster and check resources.

Screenshots
AksEdge cmdlet errors:

kubectl cmdlet error:

The config file that I used to deploy the cluster:

{
  "SchemaVersion": "1.9",
  "Version": "1.0",
  "DeploymentType": "SingleMachineCluster",
  "Init": {
    "ServiceIPRangeSize": 1
  },
  "Network": {
    "NetworkPlugin": "flannel",
    "Ip4AddressPrefix": "192.168.0.0/24",
    "SkipAddressFreeCheck": true,
    "DnsServers": [
      "10.140.103.250",
      "10.145.103.250"
    ],
    "InternetDisabled": true,
    "SkipDnsCheck": false,
    "Proxy": {
      "Http": null,
      "Https": null,
      "No": "localhost,127.0.0.0/8,192.168.0.0/16,172.17.0.0/16,10.42.0.0/16,10.43.0.0/16,10.96.0.0/12,10.244.0.0/16,.svc"
    },
    "Ip4PrefixLength": 24
  },
  "User": {
    "AcceptEula": true,
    "AcceptOptionalTelemetry": true,
    "VolumeLicense": {
      "EnrollmentID": null,
      "PartNumber": null
    },
    "Force": null
  },
  "Machines": [
    {
      "LinuxNode": {
        "CpuCount": 8,
        "MemoryInMB": 16384,
        "LogSizeInGB": 10,
        "DataSizeInGB": 30,
        "TimeoutSeconds": 300,
        "TpmPassthrough": false,
        "SecondaryNetworks": [
          {
            "VMSwitchName": null,
            "Ip4Address": null,
            "Ip4GatewayAddress": null,
            "Ip4PrefixLength": null
          }
        ],
        "ControlPlane": true
      },
      "NetworkConnection": {
        "AdapterName": null,
        "Mtu": 0
      }
    }
  ]
}

Environment (please complete the following information):

• AKS Edge Essentials Version [AksEdge-K3s-1.27.6-1.6.384.0.msi]
• Kubernetes version [1.26.10]
• Windows Host OS (please complete the following information):
  • Edition: [W11 Enterprise]
  • Version: [10.0.26100 Build 26100]
  • Virtual Machine: [Local]

Additional context
None

[namalu]

I'm having the same issue on multiple host machines. For me, this occurred when the host machines were restarted to apply a Windows update. I restarted one of the host machines several times during the day and the AKS Edge Essentials cluster always started with no issue. Overnight an update was applied to the host machine and now the node will not start. Looking at the update history, an AKS Edge Essentials update was applied.

AKS Edge Essentials k3s-1.29.9 (Version 1.10.868.0) Applied 6/26/2025
2025-06 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5060842) Applied 6/25/2025
2025-06 .NET 8.0.17 Security Update for x64 Client (KB5061935) Applied 6/25/2025

[jinrongchi]

I'm having the same issue on multiple host machines. For me, this occurred when the host machines were restarted to apply a Windows update. I restarted one of the host machines several times during the day and the AKS Edge Essentials cluster always started with no issue. Overnight an update was applied to the host machine and now the node will not start. Looking at the update history, an AKS Edge Essentials update was applied.

AKS Edge Essentials k3s-1.29.9 (Version 1.10.868.0) Applied 6/26/2025 2025-06 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5060842) Applied 6/25/2025 2025-06 .NET 8.0.17 Security Update for x64 Client (KB5061935) Applied 6/25/2025

@namalu Thanks for the additional proof, I completely overlooked the “Windows Update” condition as we don't usually reboot our machines so I didn't think that could be a factor. My situation was also caused by applying Windows updates, although in my case there was no AKS Edge Essentials related changes, but like in your case I have KB5060842 and KB5061935: