Problem overview.
The challenge this resource is designed to solve.
Feature updates are the slowest part of most Windows fleets. Some devices are eligible for a small enablement-style patch, others need a full ISO, Enterprise editions are licensed and sourced differently from Pro, Home, and Education, and a few machines are not compatible at all. Done by hand, that means checking each device's current build and edition, finding the right media, staging an 8 GB download across sites that may share a single uplink, running setup with the correct switches, chasing reboots, and then verifying that the machine actually landed on the target build. Without a consistent process, you end up with partial rollouts, unexplained failures, and no record of which devices were skipped and why.
About this resource.
What it does and how it fits into your workflow.
The Windows 11 26H2 Upgrade automation handles the branching work of a feature update rollout in one sequence. It is Windows-only. The first action exits immediately on macOS and Linux endpoints, so you can scope it against a mixed group without special filtering.
After that, a shell action checks the Windows version and compatibility. If the device is not a candidate, the automation creates an Alert on Incompatible Upgrade and exits, which leaves you a worklist of machines that need hardware review or replacement instead of a silent failure.
For eligible devices, there are two upgrade paths. If the device qualifies for the KB5121794 patch, the automation installs that patch and skips media entirely, which avoids the large download. If the device needs media, the automation downloads the universal image for Pro, Home, and Education editions from a URL, or pulls a stored Enterprise file for Enterprise devices, then runs the Upgrade to 26H2 (Using ISO) script.
Once the upgrade work is done, the automation prompts a reboot, runs a confirmation and cleanup shell action to verify the result and remove leftover files, and raises a Windows 11 Upgrade Failed alert if the device did not end up where it should be.
The snapshot of this automation has no triggers configured, so you decide how it launches: run it on demand against a device group, or add your own schedule or condition in Automations. Most of the action steps are conditional, so a device only runs the branch that applies to it. Pair the rollout with your normal patch management policy so monthly updates keep flowing during and after the upgrade window.
Use cases.
Common ways to put this resource to work.
- Move a pilot ring of Windows 11 Pro devices to 26H2 and confirm the resulting build before expanding to the rest of the fleet.
- Upgrade Enterprise-edition endpoints using an Enterprise image you supply and stage yourself, rather than a public download URL.
- Let eligible devices take the KB5121794 patch path so you only burn the large ISO download on machines that actually need media.
- Produce a list of incompatible devices from the Alert on Incompatible Upgrade action and turn it into a hardware refresh plan.
- Catch upgrades that did not complete through the Windows 11 Upgrade Failed alert instead of discovering them weeks later during an audit.
- Schedule the run against a site or group during a maintenance window so the reboot prompt lands when users expect it.
Recommendations.
Practical guidance for a reliable rollout.
- Plan for bandwidth. Per the automation author, the ISO is roughly 8 GB. Stage rollouts site by site rather than firing at an entire fleet on a shared uplink.
- If you run Enterprise edition, source and stage your own 26H2 Enterprise ISO before enabling the automation. Pro, Home, and Education devices use the universal download path.
- Run against a small pilot group first and check the confirmation step's result before widening scope.
- Review the Enterprise download action in your copy of the automation. In this snapshot it is labeled "Download 25H2 Enterprise", so verify the file it points at matches the 26H2 media you intend to deploy.
- Add a trigger or schedule that fits your change window. This automation ships with no trigger configured, so nothing runs until you decide how it starts.
- Tell users a reboot prompt is coming. The restart step is the one part of the sequence that is visible to them.
- Treat the incompatible alert as a real queue. Those devices will not upgrade no matter how many times the automation runs.