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

**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

Start with the Start-AksEdgeNode -NodeType Linux entry point and investigate the missing network interface error after a Windows host reboot. Reproduce the SingleMachineCluster setup, reboot the host, and verify that the Linux node starts successfully and kubectl can connect and check resources.

Written by the indexing model from the issue text.