Merge pull request #300651 from minorutsuchida/patch-1

Update troubleshoot-iot-edge-for-linux-on-windows-common-errors.md

Author: prmerger-automator[bot]

articles/iot-edge/troubleshoot-iot-edge-for-linux-on-windows-common-errors.md

@@ -84,6 +84,7 @@ This section covers common errors when you interact with the EFLOW virtual machi
 > | Unknown feature '$feature' is provided. | The *Set-EflowVmFeature* cmdlet supports _DpsTpm_ and _Defender_ as the two features that can be enabled or disabled. | For more information about `Set-EflowVmFeature` PowerShell cmdlet, see [PowerShell functions for IoT Edge for Linux on Windows](./reference-iot-edge-for-linux-on-windows-functions.md). | 
 > | Unsupported DDA Type: $gpuName | Currently, GPU DDA is only supported for _NVIDIA Tesla T4_ and _NVIDIA A2_. If the user provides another GPU name, the GPU passthrough fails. | Verify all the GPU prerequisites are met. For more information about EFLOW GPU support, check [Azure IoT Edge for Linux on Windows GPU passthrough](https://aka.ms./azeflow-gpu). 
 > | Invalid GPU configuration requested, <br/> Passthrough enabled but requested gpuCount == $gpuCount <br/> GPU PassthroughType '$gpuPassthroughType' not supported by '$script:WssdProviderVmms' WssdProvider <br/> Requested GPU configuration cannot be supported by Host, <br/> GPU '$gpuName' not available <br/> Requested GPU configuration cannot be supported by Host, <br/> not enough GPUs available - Requested($gpuCount), Available($($selectedGpuDevice.Count)) <br/> Requested GPU configuration cannot be supported by Host, <br/> GPU PassthroughType '$gpuPassthroughType' not supported <br/> Invalid GPU configuration requested, Passthrough disabled but gpuCount > 0" | These errors are generally related to one or more the GPU dependencies not being met. | Make sure all the GPU prerequisites are met. For more information about EFLOW GPU support, check [Azure IoT Edge for Linux on Windows GPU passthrough](https://aka.ms./azeflow-gpu). |
+> | Failed to Connect to EFLOW VM | When attempting to connect to the EFLOW VM using the Connect-EflowVm PowerShell cmdlet, the connection fails with an "authentication handshake failed" error. | The cause is that the WSSDAgent certificate has expired. The WSSDAgent certificate expires one year after a new installation of EFLOW. Please execute updateWssdCert.ps1 to extend the certificate validity period. Note that updating EFLOW does not extend the validity period of the WSSDAgent certificate, check [updateWssdCert.ps1](https://github.com/Azure/iotedge-eflow/blob/main/eflow-util/updateWssdCert.ps1).|
 
 ## Networking