Freshness review

Author: Pat Altimore

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

@@ -3,7 +3,7 @@ title: Troubleshoot your IoT Edge for Linux on Windows device
 description: Learn standard diagnostic skills for troubleshooting Azure IoT Edge for Linux on Windows (EFLOW) like retrieving component status and logs.
 author: PatAltimore
 ms.author: patricka
-ms.date: 06/10/2024
+ms.date: 07/22/2025
 ms.topic: troubleshooting-general
 ms.service: azure-iot-edge
 ms.custom: linux-related-content
@@ -14,41 +14,41 @@ services: iot-edge
 
 [!INCLUDE [iot-edge-version-all-supported](includes/iot-edge-version-all-supported.md)]
 
-If you experience issues running Azure IoT Edge for Linux on Windows (EFLOW) in your environment, use this article as a guide for troubleshooting and diagnostics. 
+If you run into issues with Azure IoT Edge for Linux on Windows (EFLOW), use this article to troubleshoot and diagnose the problem.
 
 You can also check [IoT Edge for Linux on Windows GitHub issues](https://github.com/Azure/iotedge-eflow/issues?q=is%3Aissue) for a similar reported issue.
 
 ## Isolate the issue
 
-Your first step when troubleshooting IoT Edge for Linux on Windows should be to understand which component is causing the issue. There are three main components an EFLOW solution:
-- Windows components: PowerShell module, WSSDAgent & EFLOWProxy
-- CBL Mariner Linux virtual machine
+Start troubleshooting IoT Edge for Linux on Windows by identifying which component causes the issue. An EFLOW solution has three main components:
+- Windows components: PowerShell module, WSSDAgent, and EFLOWProxy
+- Azure Linux virtual machine
 - Azure IoT Edge 
 
 For more information about EFLOW architecture, see [What is Azure IoT Edge for Linux on Windows](iot-edge-for-linux-on-windows.md).
 
-If your issue is installing or deploying the EFLOW virtual machine, make sure that all the prerequisites are met, and verify your networking and VM configurations. If your installation and deployment was successful and you're facing issues with the post VM management, the problems are generally related to VM lifecycle, networking, or Azure IoT Edge. Finally, if the issue is related to modules or IoT Edge features, check [Troubleshoot your IoT Edge device](troubleshoot.md).
+If you have trouble installing or deploying the EFLOW virtual machine, check that all prerequisites are met, and verify your networking and VM configurations. If installation and deployment succeed but you run into issues with post-VM management, problems are usually related to VM lifecycle, networking, or Azure IoT Edge. If the issue involves modules or IoT Edge features, see [Troubleshoot your IoT Edge device](troubleshoot.md).
 
 For more information about common errors related to *installation and deployment*, *provisioning*, *interaction with the VM*, and *networking*, see [Common issues and resolutions for Azure IoT Edge for Linux on Windows](troubleshoot-iot-edge-for-linux-on-windows-common-errors.md).
 
 ## Gather debug information
 
-When you need to gather logs from an IoT Edge for Linux on Windows device, the most convenient way is to use the `Get-EflowLogs` PowerShell cmdlet. By default, this command collects the following logs:
-- **eflowlogs-summary.txt**: contains the status of all log collection steps.
-- **EFLOW VM configuration**: includes the VM, networking, and passthrough configurations and additional information. 
-- **EFLOW Events** : Windows events related to the VM lifecycle and *EFLOWProxy* service.
+To gather logs from an IoT Edge for Linux on Windows device, use the `Get-EflowLogs` PowerShell cmdlet. By default, this command collects these logs:
+- **eflowlogs-summary.txt**: shows the status of all log collection steps.
+- **EFLOW VM configuration**: has the VM, networking, passthrough configurations, and other information.
+- **EFLOW Events**: Windows events related to the VM lifecycle and *EFLOWProxy* service.
 - **IoT Edge logs**: includes the output of `iotedge check` the IoT Edge runtime support bundle.
-- **WSSDAgent logs**: includes all the logs related to the *WSSDAgent* service.
+- **WSSDAgent logs**: includes all logs related to the *WSSDAgent* service.
 
-After the cmdlet gathers all the required logs, the files are compressed into a single file named *eflowlogs.zip* under the EFLOW installation path (For example, *C:\Program Files\Azure IoT Edge*).
+After the cmdlet gathers all required logs, it compresses the files into a single file named *eflowlogs.zip* in the EFLOW installation path (for example, *C:\Program Files\Azure IoT Edge*).
 
 ## Check your IoT Edge version
 
-If you're running an older version of IoT Edge for Linux on Windows, then upgrading may resolve your issue. To check the EFLOW version installed on your device, use the following steps:
+If you're running an older version of IoT Edge for Linux on Windows, upgrading can resolve your issue. To check the EFLOW version installed on your device, follow these steps:
 
 1. Open **Settings** on Windows.
 1. Select **Add or Remove Programs**.
-1. Depending on the EFLOW release train being used (Continuous Release or LTS), choose **Azure IoT Edge LTS** or **Azure IoT Edge**.
+1. Depending on the EFLOW release train you use (Continuous Release or LTS), select **Azure IoT Edge LTS** or **Azure IoT Edge**.
 1. Check the version under the EFLOW app name.
 
 For more information about specific versions release notes, check [Azure IoT Edge for Linux on Windows release notes](https://aka.ms/AzEFLOW-Releases). 
@@ -59,9 +59,9 @@ For instructions on how to update your device, see [Update IoT Edge for Linux on
 
 You can verify the EFLOW VM status and information by using the `Get-EflowVm` PowerShell cmdlet. If the EFLOW VM is running, the **VmPowerState** output should be *Running*. Whereas if the VM is stopped, the **VmPowerState** output is *Off*. To start or stop the EFLOW VM, use the `Start-EflowVm` and `Stop-EflowVm` cmdlet. 
 
-If the VM is *Running* but you can't interact or access the VM, there's probably a networking issue between the VM and the Windows host OS.  Also, make sure that the EFLOW VM has enough memory and storage available to continue with normal execution. Run the `Get-EflowVm` cmdlet to see the memory(*TotalMemMb*, *UsedMemMb*, *AvailableMemMb*) and storage(*TotalStorageMb*, *UsedStorageMb*, *AvailableStorageMb*) information. 
+If the VM is *Running* but you can't interact with or use the VM, there might be a networking issue between the VM and the Windows host OS. Also, check that the EFLOW VM has enough memory and storage available to continue normal execution. Run the `Get-EflowVm` cmdlet to see the memory (*TotalMemMb*, *UsedMemMb*, *AvailableMemMb*) and storage (*TotalStorageMb*, *UsedStorageMb*, *AvailableStorageMb*) information. 
 
-Finally, if the VM is *Off* and you can't start it using the `Start-EflowVm` cmdlet, there may be several reasons why the VM can't be started. 
+If the VM is *Off* and you can't start it using the `Start-EflowVm` cmdlet, there can be several reasons why the VM can't start. 
 
 First, the issue could be related to the VM lifecycle management service (*WSSDAgent*) not running. Ensure that the *WSSDAgent* service is running using the following steps: 
 
@@ -83,12 +83,15 @@ Second, the issue could be related to lack of resources. You can set the *EflowV
     ```powershell
     Get-CIMInstance Win32_OperatingSystem | Select FreePhysicalMemory
     ```
-1. Check the available CPU cores. Ensure that  *NumberOfLogicalProcessors* is greater than *EflowVmAssignedCPUcores*.
+1. Check the available CPU cores. Make sure that *NumberOfLogicalProcessors* is greater than *EflowVmAssignedCPUcores*.
+   ```powershell
+    wmic cpu get NumberOfLogicalProcessors
+    ```ssignedCPUcores*.
    ```powershell
     wmic cpu get NumberOfLogicalProcessors
     ```
 
-Finally, the issue could be related to networking. For more information about EFLOW VM networking issues, see [How to troubleshoot Azure IoT Edge for Linux on Windows networking](./troubleshoot-common-errors.md).
+Finally, the issue might be related to networking. For more information about EFLOW VM networking issues, see [How to troubleshoot Azure IoT Edge for Linux on Windows networking](./troubleshoot-common-errors.md).
 
 ## Check the status of the IoT Edge runtime
 
@@ -119,38 +122,38 @@ If you're using TPM provisioning by following the guide [Create and provision an
     ```powershell
     Start-Service -Name EFLOWProxy
     ```
-   If the service won't start, check the *EFLOWProxy* logs. Go to **Apps** > **Event Viewer** > **Applications and Services Logs** > **Microsoft** > **EFLOW** > **EFLOWProxy** and check the logs. 
+   If the service doesn't start, check the *EFLOWProxy* logs. Go to **Apps** > **Event Viewer** > **Applications and Services Logs** > **Microsoft** > **EFLOW** > **EFLOWProxy** and review the logs.
 
-1. If the service is **Running** then check the EFLOW VM proxy services. Start by connecting to the EFLOW VM.
+1. If the service is **Running**, check the EFLOW VM proxy services. Start by connecting to the EFLOW VM.
    ```powershell
    Connect-EflowVm
     ```
-1. From inside the EFLOW VM, check the TPM services are up and running.
+1. From inside the EFLOW VM, check that the TPM services are running.
    ```bash
    sudo systemctl status tpm*
    ```
-   You should see the status and logs of four different services. The four services should be up and running.
+   You see the status and logs of four different services. All four services need to be running.
     1. **tpm2-netns.service** - TPM2 Network Namespace
     1. **[email protected]** - TPM2 Sandbox Service on Port 2322
     1. **[email protected]** - TPM2 Sandbox Service on Port 2321
     1. **tpm2-abrmd.service** - TPM2 Access Broker and Resource Management Daemon
 
-   If any of these services is **stopped** or **failed**, restart all services using the following command:
+   If any of these services is **stopped** or **failed**, restart all services with the following command:
 
    ```bash
    sudo systemctl restart tpm*
    ```
 
-1. Check the communication between the EFLOW VM and the *EFLOWProxy* service. If communication is working, you should see the *RegistrationId* and the TPM *Endorsement Key* as output from the following command: 
+1. Check the communication between the EFLOW VM and the *EFLOWProxy* service. If communication works, you see the *RegistrationId* and the TPM *Endorsement Key* as output from the following command:
    ```bash
    sudo /usr/bin/tpm_device_provision
    ```
 
 ## Check GPU Assignment
 
-If you're using GPU passthrough, ensure to follow all the prerequisites and configurations outlined in [GPU acceleration for Azure IoT Edge for Linux on Windows](./gpu-acceleration.md). If you experience issues using GPU passthrough feature, check the following steps:
+If you're using GPU passthrough, make sure you follow all the prerequisites and configurations in [GPU acceleration for Azure IoT Edge for Linux on Windows](./gpu-acceleration.md). If you have issues with the GPU passthrough feature, follow these steps:
 
-First, start by checking your device is available on the Windows host OS.
+First, check that your device is available on the Windows host OS.
 
 1. Open **Apps** > **Device Manager**.
 1. Go to **Display Adapters** and check that your GPU is in the list.
@@ -163,25 +166,25 @@ Second, if the GPU is correctly assigned, but still not being able to use it ins
     ```powershell
     Connect-EflowVm
     ```
-1. If you're using a **NVIDIA GPU**, check the passthrough status using the following command:
+1. If you're using a **NVIDIA GPU**, check the passthrough status with this command:
     ```bash
     sudo nvidia-smi
     ```
-   You should be able to see the GPU card information, driver version, CUDA version, and the GPU system and processes information. 
+   You see the GPU card information, driver version, CUDA version, and GPU system and process information.
 
-1. If you're using an **Intel iGPU** passthrough, check the passthrough status using the following command:
+1. If you're using an **Intel iGPU** passthrough, check the passthrough status with this command:
     ```bash
     sudo ls -al /dev/dxg
     ```
-    The expected output should be similar to:
+    The expected output looks like:
     ```Output
     crw-rw-rw- 1 root 10, 60  Sep  8 06:20 /dev/dxg
     ```
-    For more Intel iGPU performance and debugging information, see [Witness the power of Intel® iGPU with Azure IoT Edge for Linux on Windows(EFLOW) & OpenVINO™ Toolkit](https://community.intel.com/t5/Blogs/Tech-Innovation/Artificial-Intelligence-AI/Witness-the-power-of-Intel-iGPU-with-Azure-IoT-Edge-for-Linux-on/post/1382405).
+    For more about Intel iGPU performance and debugging, see [Witness the power of Intel® iGPU with Azure IoT Edge for Linux on Windows(EFLOW) & OpenVINO™ Toolkit](https://community.intel.com/t5/Blogs/Tech-Innovation/Artificial-Intelligence-AI/Witness-the-power-of-Intel-iGPU-with-Azure-IoT-Edge-for-Linux-on/post/1382405).
 
 ## Check WSSDAgent logs for issues
 
-The first step before checking *WSSDAgent* logs is to check if the VM was created and is running. 
+Before you check the *WSSDAgent* logs, make sure the VM is created and running.
 
 1. Start an elevated *PowerShell* session using **Run as Administrator**.
 1. On Windows Client SKUs, check the [HCS](https://techcommunity.microsoft.com/t5/containers/introducing-the-host-compute-service-hcs/ba-p/382332) virtual machines.
@@ -209,7 +212,7 @@ The first step before checking *WSSDAgent* logs is to check if the VM was create
     NUC-EFLOW          Running 0           1024              00:01:34.1280000 Operating normally 9.0
     ```
 
-If for some reason the VM isn't listed, that means that VM isn't running or the *WSSDAgent* wasn't able to create it. Use the following steps to check the *WSSDAgent* logs:
+If the VM isn't listed, it isn't running or the *WSSDAgent* can't create it. Follow these steps to check the *WSSDAgent* logs:
 
 1. Open **File Explorer**.
 1. Go to `C:\ProgramData\wssdagent\log`
@@ -218,7 +221,7 @@ If for some reason the VM isn't listed, that means that VM isn't running or the
 
 ## Reinstall EFLOW
 
-Sometimes, a system might require significant special modification to work with existing networking or operating system constraints. For example, a system could require complex networking configurations (firewall, Windows policies, proxy settings) and custom Windows OS configurations. If you tried all previous troubleshooting steps and still have EFLOW issues, it's possible that there's some misconfiguration that is causing the issue. In this case, the final option is to uninstall and reinstall EFLOW. 
+Sometimes, a system needs special changes to work with existing networking or operating system constraints. For example, a system might need complex networking settings, like firewall, Windows policies, proxy settings, or custom Windows OS settings. If you've tried all previous troubleshooting steps and still have EFLOW issues, a misconfiguration might be causing the problem. In this case, the last option is to uninstall and reinstall EFLOW. 
 
 ## Next steps