Which operating systems does this automation support?

Windows only. The first action exits immediately on macOS and Linux endpoints. It is intended for Windows 11 devices and most editions, excluding LTSC and Eval.

Will every machine download the full ISO?

No. Devices running 24H2 with a build number above 26100 can reach 25H2 through KB5054156 with no ISO download. The compatibility check determines which path a device qualifies for and deploys accordingly. Machines that do not qualify for the enablement package will download the full ISO, which is roughly 7GB.

Why do I have to supply my own Enterprise ISO?

Microsoft does not host a public version of the Enterprise 25H2 ISO. If you want to upgrade Enterprise machines, upload the ISO to your Level account and populate the "Download 25H2 Enterprise" repository file so that action has something to pull.

What happens if a device cannot be upgraded?

The automation creates an alert through the "Alert on Incompatible Upgrade" action and then exits for that device, so it does not attempt a download or install.

How do I know whether the upgrade actually worked?

After the reboot, the "25H2 Confirmation, Cleanup" action checks the result and cleans up downloaded files. If 25H2 is not confirmed, the "Windows 11 Upgrade Failed Alert" action raises an alert.

Does this automation come with a trigger or schedule?

The source snapshot lists no triggers and no monitors. Set the trigger or schedule you want after importing, and size each run against the bandwidth considerations above.

Windows 11 25H2 Upgrade Automation

Problem overview.

The challenge this resource is designed to solve.

Upgrading to Windows 11 25H2 from nearly any version and/or edition of Windows 11

About this resource.

What it does and how it fits into your workflow.

The Windows 11 25H2 Upgrade automation handles the branching logic for a 25H2 rollout so you do not have to pre-sort your fleet by build number or edition. It is intended for Windows 11 devices and is built to work with most editions, excluding LTSC and Eval.

The automation runs through these actions in order, with conditions controlling which ones apply to a given device:

Exit if macOS & Linux stops the run on non-Windows endpoints.
Check Windows Version, Compatibility is a shell action that determines the device's current version and which upgrade path, if any, applies.
Alert on Incompatible Upgrade creates an alert for devices that cannot be upgraded, followed by Exit If Incompatible to end the run cleanly.
Install KB5054156 (24h2 to 25h2) (No ISO) handles the lightweight path for 24H2 machines on a build above 26100. No multi-gigabyte download is needed here.
Download 25H2 Universal (Pro, Home, Edu) pulls the public ISO from a URL for devices that need the full image.
**Download 25H2 Enterprise pulls an ISO from a repository file you populate yourself, since Microsoft does not publish an Enterprise 25H2 ISO.
** Make sure to upload your own Enterprise 25H2 ISO and link it in this action you need to upgrade Enterprise devices!
Upgrade To 25H2 (using ISO) runs the "Upgrade to 25H2 (Using Win Update)" script against the downloaded image.
Prompt Reboot triggers the restart needed to finish the upgrade.
25H2 Confirmation, Cleanup verifies the resulting version and clears downloaded artifacts.
Windows 11 Upgrade Failed Alert raises an alert when the confirmation step does not find 25H2.

The important behavior to understand is the path selection. The compatibility check decides automatically whether a device qualifies for the KB5054156 route or needs the ISO route, so a mixed fleet can run the same automation. The practical consequence is that machines not already on a qualifying 24H2 build will pull roughly 7GB each. That single fact should shape how you schedule and batch this, more than anything else in the configuration.

This entry is part of Level's patch management library. For details on how conditions and action chaining work in general, see Automations.

Perform these actions...

Use cases.

Common ways to put this resource to work.

Upgrade a mixed Windows 11 fleet to 25H2 without manually sorting devices by build number, letting the compatibility check route each machine to either the enablement package or the full ISO.
Fast-track devices already on 24H2 with a build above 26100 using KB5054156, skipping the 7GB download entirely.
Roll out 25H2 to Enterprise edition devices by uploading your own Enterprise ISO to your Level account and populating the "Download 25H2 Enterprise" repository file.
Surface devices that cannot be upgraded through the "Alert on Incompatible Upgrade" alert, producing a working list of machines that need hardware review, edition changes, or exclusion.
Catch silent failures after reboot through the confirmation step and the "Windows 11 Upgrade Failed Alert", instead of discovering stragglers during your next audit.

Recommendations.

Practical guidance for a reliable rollout.

Batch your deployments. Most devices will download a roughly 7GB ISO, so be deliberate about how many machines you target in a single run and when that run happens.
Schedule outside business hours and away from peak network use, especially for sites sharing a single uplink.
Upload your Enterprise 25H2 ISO and populate the "Download 25H2 Enterprise" repository file before targeting any Enterprise devices. Microsoft does not host a public Enterprise 25H2 ISO, so that path will not work until you supply the file.
Scope out LTSC and Eval editions. The automation is built for most editions but not those two.
Pilot on a small group of each edition and build combination you have in production before widening the rollout, so you can see both the KB5054156 path and the ISO path complete end to end.
Plan for the reboot. The "Prompt Reboot" action is part of the sequence, so pick a window where users can accept a restart or where devices are expected to be unattended.
Watch both alert actions during the rollout. Incompatible devices and failed upgrades are reported through separate alerts, and they need different follow-up.