This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 69%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAT%3C/text%3E%3C/svg%3E)
Hello All,
I would like to know if we can directly upgrade 1809 version systems to 20H1 skipping 1909. Is this technically possible ? or do we need to first migrate to 1909 and then to 20H1. If we can directly moved systems from 1809 to 20H1 it will save lot of time.
Please provide your inputs ?
Yes. This is supported as 1809 is still a supported OS. Note that this is not directly related to ConfigMgr though and is specific to Windows (thus, I've added the appropriate Windows tag to this thread).
@Jason Sandys Hi Jason sorry my question was for corporate systems doing upgrade via SCCM. Can you confirm we can skip 1909 and move to 20H1 via SCCM upgrades (TS)
Yes, same answer and still independent of the delivery mechanism (ConfigMgr in this case). All an upgrade task sequence does today is run Windows Setup from the supplied media/image to perform the upgrade.
You can upgrade all your windows 10 build to latest using task sequence method, refer the below blog,