The new task is something that was started by one of the folks in the support group.
We have upgraded nearly all of our clients Windows 10 to Windows 11 using ImmyBot and the Windows Update task. The problem with the Windows Update task itself is that it relies solely on Windows Update to offer and install the upgrade properly–which works fine if the conditions are correct for its installation. The primary reason that the upgrade fails is simply lack of disk space, which Windows Update fails to consider before offering the update. Having discovered this some time ago, I wrote a task to simply audit disk space and provide a dashboard item to find machines failing to update that also had <20GB of disk space. After making sure old profiles and other non-obvious things were cleared up from these older machines, we saw a very significant improvement in the success rate of Windows Update upgrading Windows 10 to 11 successfully – probably > 90%. The majority of the remaining issues for Windows 10–>11 failing were things like machines that needed Windows Update to be repaired, and a pre-flight script modification that I made in my instance to prevent interruption of the upgrade during the reboot/boot up process–but I have not posted this pre-flight script modification because of a different issue that can cause machines to become unable to execute ImmyBot sessions due to certain other Windows Update issues–specifically (but generally) certain machines have “hung” windows update processes and I have not found a reliable way to distinguish between actual active windows update processes and those that are fully hung.
All of this said, the 10 to 11 upgrade that was recently added by one of the folks in the support group incorporates many of the aforementioned checks and is intended to give you reasons why the Windows Update/Upgrade process will fail, or why it may have failed (unsure as of yet which order this is being done).
Others have posted scripts to use the Windows Upgrade assistant and have reported success, but I can’t speak to its reliability or behavior because I have not used or tested it.