Forum Discussion
Upgrading OLD windows 10 versions
I have some old unsupported version of windows in the environment 1511 1607 and 1703. I would like to upgrade them using the feature upgrade through Servicing model and not an IPU using setup.exe and a task sequence.
Will the servicing update process upgrade these old versions to 1909? Or is there documentation on the limitations of the servicing model?
Karen, You mean using the enablement package, which isn't the question John is asking.
Looking for documentation on supported jumps to 1909 from previous versions running Servicing (in place upgrade).
Enablement Package 1903 -> 1909
https://support.microsoft.com/en-us/help/4517245/feature-update-via-windows-10-version-1909-enablement-package
Servicing: (Previous Windows 10 -> Newer Version of Windows 10)
https://docs.microsoft.com/en-us/mem/configmgr/osd/deploy-use/manage-windows-as-a-service
10 Replies
- KevinMineweaser_MSFT
Microsoft
John_Dahl while the team is leaning on the how and why to your question, can you help us understand what scenarios, issues, or business reasons led to being so far behind? As noted, get current and stay current is the shortest putt but we are always listening for opportunities to improve process or reduce friction.
Thanks,
-Kevin
Complex environment, currently with 18 different domains and different configurations, passwords etc. And more to come.
Inheritance of different states of machines, users connected and not connected to networks.
Project of getting machines off of windows 7 still continuing.
Now with many working remotely, the IPU is so complex to upgrade and standardize the configuration, that it will never work through Cisco Anyconnect VPN. Best thing is to implement the Service Model.
- Hi John, you can do either servicing updates, or image ( setup) , however, often, customers I have worked with that find themselves in your situation, on very old versions, end up deciding that the fastest route forward is to reinstall to the latest. The update technology and experience has improved dramatically, and depending on the HW, you may be looking at a multi-hour + update from 1511, plus any additional apps/driver updates. So, if you have practices like cloud based storage, etc, a simple repave may the faster route for you in this case. Current versions can see servicing updates sub-20 mins, so the story is very different when your staying current, and we like to call out, one of the key designs and benefits of staying current.
crys_lis I have tested the behaviour 1-1,5 years ago. But eventually stopped it, after finding that the process worked well
Releases of Windows Client 10 1507, 1511, 1607, 1703, 1709, 1803, 1809 will fetch the upgrade bits via Windows Update. In some cases it did not right away downloaded to the latest version in one step like 1507 to 22H2. There may be limitations.Using ISO / setup the upgrade should work / "offline" directly from 1507 to the latest 22H2.
older versions could be in fact stuck on a release as they did not receive SSUs correctly or running out of space. Reserved Space and WU health updates got introduced later.
Offline Updates:
Offline Updates through ISOs bear risks! Without the ability to connect to the internet, setup will not be able to fetch dynamic updates, which are smaller bits to smooth the upgrade process, updating the setup itself or integrating smaller updates, or finding blockers / drivers etc.
Make sure to always use a patched ISO so some of these fixes are included.
In any case without dynamic update you are loosing abilities to update multi language systems, esp. with Windows Core OS and dotnet. Only with dynamic updates it will retain and upgrade optional features.
Flipside I have seen "online" upgrades failing as the drivers fetched with the updates, causes more issues than they solved, but that was a smaller percentage.
OT:
For Windows Server the supported maximum is 2 major releases, unlike Windows Client
With Windows Server 2025 this will be extended from 2 major releases to 4. So one could directly upgrade from N-4 (2025 > 2022 > 2019 > 2016 > 2012R2) in one approach using ISO.
- Thank you. I will keep this in mind during testing.
- Karen_SimpsonHi John - To answer your immediate question, the 1903 to 1909 update via servicing is ONLY applicable for the upgrade from 1903 to 1909. It won't work with ANY other combination.
Karen, You mean using the enablement package, which isn't the question John is asking.
Looking for documentation on supported jumps to 1909 from previous versions running Servicing (in place upgrade).
Enablement Package 1903 -> 1909
https://support.microsoft.com/en-us/help/4517245/feature-update-via-windows-10-version-1909-enablement-package
Servicing: (Previous Windows 10 -> Newer Version of Windows 10)
https://docs.microsoft.com/en-us/mem/configmgr/osd/deploy-use/manage-windows-as-a-service- Thank you Gary. I appreciate the info. 🙂
Just so I fully understand you, all previous version before 1903 must be upgraded using the setup.exe method to get to 1909?
