Skip to content

Commit 958ac36

Browse files
Merge pull request #302589 from PatAltimore/patricka-freshness
Freshness review
2 parents b72b3fe + 42e2c4d commit 958ac36

File tree

1 file changed

+20
-20
lines changed

1 file changed

+20
-20
lines changed

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

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -6,53 +6,53 @@ ms.service: azure-iot-edge
66
ms.custom: linux-related-content
77
services: iot-edge
88
ms.topic: concept-article
9-
ms.date: 06/05/2024
9+
ms.date: 07/11/2025
1010
ms.author: patricka
1111
---
1212

1313
# Update IoT Edge for Linux on Windows
1414

1515
[!INCLUDE [iot-edge-version-all-supported](includes/iot-edge-version-all-supported.md)]
1616

17-
As the IoT Edge for Linux on Windows (EFLOW) application releases new versions, you want to update your IoT Edge devices for the latest features and security improvements. This article provides information about how to update your IoT Edge for Linux on Windows devices when a new version is available.
17+
When a new version of the IoT Edge for Linux on Windows (EFLOW) application is released, update your IoT Edge devices to get the latest features and security improvements. This article explains how to update your IoT Edge for Linux on Windows devices when a new version is available.
1818

1919

20-
With IoT Edge for Linux on Windows, IoT Edge runs in a Linux virtual machine hosted on a Windows device. This virtual machine is preinstalled with IoT Edge, and has no package manager, so you can't manually update or change any of the VM components. Instead, the virtual machine is managed with Microsoft Update to keep the components up to date automatically.
20+
With IoT Edge for Linux on Windows, IoT Edge runs in a Linux virtual machine hosted on a Windows device. This virtual machine comes preinstalled with IoT Edge and doesn't have a package manager, so you can't manually update or change any of the VM components. Instead, Microsoft Update manages the virtual machine to keep the components up to date automatically.
2121

22-
The EFLOW virtual machine is designed to be reliably updated via Microsoft Update. The virtual machine operating system has an A/B update partition scheme to utilize a subset of those to make each update safe and enable a roll-back to a previous version if anything goes wrong during the update process.
22+
The EFLOW virtual machine is designed for reliable updates through Microsoft Update. The virtual machine operating system uses an A/B update partition scheme to make each update safe and lets you roll back to a previous version if something goes wrong during the update process.
2323

24-
Each update consists of two main components that may get updated to latest versions. The first one is the EFLOW virtual machine and the internal components. For more information about EFLOW, see [Azure IoT Edge for Linux on Windows composition](./iot-edge-for-linux-on-windows.md). This also includes the virtual machine base operating system. The EFLOW virtual machine is based on [Microsoft CBL-Mariner](https://github.com/microsoft/CBL-Mariner) and each update provides performance and security fixes to keep the OS with the latest CVE patches. As part of the EFLOW Release notes, the version indicates the CBL-Mariner version used, and users can check the [CBL-Mariner Releases](https://github.com/microsoft/CBL-Mariner/releases) to get the list of CVEs fixed for each version.
24+
Each update has two main components that can be updated to the latest versions. The first is the EFLOW virtual machine and its internal components. For more information about EFLOW, see [Azure IoT Edge for Linux on Windows composition](./iot-edge-for-linux-on-windows.md). This also includes the virtual machine base operating system. The EFLOW virtual machine is based on [Microsoft CBL-Mariner](https://github.com/microsoft/CBL-Mariner), and each update provides performance and security fixes to keep the OS up to date with the latest CVE patches. The EFLOW release notes show the CBL-Mariner version used, and you can check the [CBL-Mariner Releases](https://github.com/microsoft/CBL-Mariner/releases) for the list of CVEs fixed for each version.
2525

2626
The second component is the group of Windows runtime components needed to run and interop with the EFLOW virtual machine. The virtual machine lifecycle and interop is managed through different components: WSSDAgent, EFLOWProxy service, and the PowerShell module.
2727

28-
EFLOW updates are sequential and you need to update to every version in order. In order to get to the latest version, you have to either do a fresh installation using the latest available version, or apply all the previous servicing updates up to the desired version.
28+
EFLOW updates are sequential, and you need to update to every version in order. To get to the latest version, either do a fresh installation using the latest available version or apply all previous servicing updates up to the version you want.
2929

3030
> [!IMPORTANT]
31-
> Upgrading from EFLOW 1.4 LTS to EFLOW 1.5 LTS is supported using any of the methods described in this article. No special steps are needed to upgrade from EFLOW 1.4 LTS to EFLOW 1.5 LTS.
31+
> You can upgrade from EFLOW 1.4 LTS to EFLOW 1.5 LTS using any of the methods described in this article. No special steps are needed to upgrade from EFLOW 1.4 LTS to EFLOW 1.5 LTS.
3232
3333
To find the latest version of Azure IoT Edge for Linux on Windows, see [EFLOW releases](https://aka.ms/AzEFLOW-Releases).
3434

3535
## Update using Microsoft Update
3636

37-
To receive IoT Edge for Linux on Windows updates, the Windows host should be configured to receive updates for other Microsoft products. By default, Microsoft Updates is turned on during EFLOW installation. If custom configuration is needed after EFLOW installation, you can turn this option On/Off with the following steps:
37+
To get IoT Edge for Linux on Windows updates, configure the Windows host to get updates for other Microsoft products. By default, Microsoft Updates is on during EFLOW installation. If you need a custom configuration after EFLOW installation, turn this option on or off with these steps:
3838

3939
1. Open **Settings** on the Windows host.
4040

4141
1. Select **Updates & Security**.
4242

4343
1. Select **Advanced options**.
4444

45-
1. Toggle the *Receive updates for other Microsoft products when you update Windows* button to **On**.
45+
1. Turn the *Receive updates for other Microsoft products when you update Windows* option to **On**.
4646

4747

4848
## Update using Windows Server Update Services (WSUS)
4949

50-
On premises updates using WSUS is supported for IoT Edge for Linux on Windows updates. For more information about WSUS, see [Device Management Overview - WSUS](/windows/iot/iot-enterprise/device-management/device-management-overview#windows-server-update-services-wsus).
50+
On-premises updates using WSUS are supported for IoT Edge for Linux on Windows updates. For more information about WSUS, see [Device Management Overview - WSUS](/windows/iot/iot-enterprise/device-management/device-management-overview#windows-server-update-services-wsus).
5151

5252

5353
## Offline manual update
5454

55-
In some scenarios with restricted or limited internet connectivity, you may want to manually apply EFLOW updates offline. This is possible using Microsoft Update offline mechanisms. You can manually download and install an IoT Edge for Linux on Windows updates with the following steps:
55+
If you have restricted or limited internet connectivity, you can manually apply EFLOW updates offline. Use Microsoft Update offline mechanisms to manually download and install IoT Edge for Linux on Windows updates. Follow these steps:
5656

5757
1. Check the current EFLOW installed version. Open **Settings** then select **Apps** -> **Apps & features**. Search for *Azure IoT Edge*.
5858

@@ -64,11 +64,11 @@ In some scenarios with restricted or limited internet connectivity, you may want
6464

6565
## Managing Microsoft Updates
6666

67-
As explained before, IoT Edges for Linux on Windows updates are serviced using Microsoft Update channel. To change receiving EFLOW updates, you have to manage Microsoft Updates. The following list includes ways to automate turning on or off Microsoft updates. For more information about managing OS updates, see [OS Updates](/windows/iot/iot-enterprise/os-features/updates#completely-turn-off-windows-updates).
67+
IoT Edge for Linux on Windows updates are serviced using Microsoft Update channel. To change receiving EFLOW updates, you have to manage Microsoft Updates. The following list includes ways to automate turning on or off Microsoft updates. For more information about managing OS updates, see [OS Updates](/windows/iot/iot-enterprise/os-features/updates#completely-turn-off-windows-updates).
6868

69-
- **CSP Policies** - By using the **Update/AllowMUUpdateService** CSP Policy - For more information about Microsoft Updates CSP policy, see [Policy CSP - MU Update](/windows/client-management/mdm/policy-csp-update#update-allowmuupdateservice).
69+
- **CSP Policies** - Use the **Update/AllowMUUpdateService** CSP policy. For more information about the Microsoft Updates CSP policy, see [Policy CSP - MU Update](/windows/client-management/mdm/policy-csp-update#update-allowmuupdateservice).
7070

71-
- **Manually manage Microsoft Updates** - For more information about how to Opt-In to Microsoft Updates, see [Opt-In to Microsoft Update](/windows/win32/wua_sdk/opt-in-to-microsoft-update).
71+
- **Manually manage Microsoft Updates** - To opt in to Microsoft Updates, see [Opt-In to Microsoft Update](/windows/win32/wua_sdk/opt-in-to-microsoft-update).
7272

7373
## Migration between EFLOW 1.1LTS and EFLOW 1.4LTS
7474

@@ -84,7 +84,7 @@ Migration between EFLOW 1.1LTS to EFLOW 1.4LTS was introduced as part of EFLOW 1
8484
To migrate between EFLOW 1.1LTS to EFLOW 1.4LTS, use the following steps.
8585

8686
1. Get the latest Azure EFLOW 1.1LTS [(1.1.2212.12122)](https://aka.ms/AzEFLOWMSI-Update-1_1_2212_12122) update. If you're using Windows Update, *Check Updates* to get the latest EFLOW update.
87-
1. For auto-download migration (needs Internet connection), skip this step. If the EFLOW VM has limited/no internet access, download the necessary files before starting the migration.
87+
1. For auto-download migration (needs internet connection), skip this step. If the EFLOW VM has limited/no internet access, download the necessary files before starting the migration.
8888
- [1.4.2.12122 Standalone MSI](https://aka.ms/AzEFLOW-Update-1_1-to-1_4_SA)
8989
- [1.4.2.12122 Update MSI](https://aka.ms/AzEFLOW-Update-1_1-to-1_4_Update)
9090
1. Open an elevated PowerShell session
@@ -97,7 +97,7 @@ To migrate between EFLOW 1.1LTS to EFLOW 1.4LTS, use the following steps.
9797
```powershell
9898
Start-EflowMigration
9999
```
100-
1. If you download the MSI on **Step 2**, use the downloaded files to apply the migration
100+
1. If you downloaded the MSI in **Step 2**, use the downloaded files to apply the migration.
101101
```powershell
102102
Start-EflowMigration -standaloneMsiPath "<path-to-folder>\AzureIoTEdge_LTS_1.4.2.12122_X64.msi"
103103
```
@@ -106,19 +106,19 @@ To migrate between EFLOW 1.1LTS to EFLOW 1.4LTS, use the following steps.
106106
```powershell
107107
Confirm-EflowMigration
108108
```
109-
1. If you download the MSI on **Step 2**, use the downloaded files to apply the migration
109+
1. If you downloaded the MSI in **Step 2**, use the downloaded files to apply the migration.
110110
```powershell
111111
Confirm-EflowMigration -updateMsiPath "<path-to-folder>\AzureIoTEdge_LTS_Update_1.4.2.12122_X64.msi"
112112
```
113113
114114
>[!WARNING]
115-
> If for any reason the migration fails, the EFLOW VM will be restored to its original 1.1LTS version.
116-
> If you want to cancel the migration or manually restore the EFLOW VM to prior state, you can use the following cmdlets `Start-EflowMigration` and then `Restore-EflowPriorToMigration`.
115+
> If the migration fails for any reason, the EFLOW VM is restored to its original 1.1LTS version.
116+
> To cancel the migration or manually restore the EFLOW VM to its prior state, run the `Start-EflowMigration` cmdlet and then `Restore-EflowPriorToMigration`.
117117
118118
For more information, check `Start-EflowMigration`, `Confirm-EflowMigration` and `Restore-EflowPriorToMigration` cmdlet documentation by using the `Get-Help <cmdlet> -full` command.
119119
120120
## Next steps
121121
122122
View the latest [IoT Edge for Linux on Windows releases](https://github.com/Azure/iotedge-eflow/releases).
123123
124-
Read more about [IoT Edge for Linux on Windows security premises](./iot-edge-for-linux-on-windows-security.md).
124+
Learn about [IoT Edge for Linux on Windows security premises](./iot-edge-for-linux-on-windows-security.md).

0 commit comments

Comments
 (0)