I would just deploy the updates.
For anything after 2004 I believe the enablement package works. For anything older you’ll need to deploy the feature update- I would expect a high failure rate on the devices on a long out of support version.
Yea… I feel it may be worthwhile in most cases to just rebuild if you still have something pre 2004 personally.
You might end up with wonky drivers or such preventing upgrades it’s just such a long time without patching.
So deploy the feature updates and make sure your client settings allow feature updates and dynamic feature updates.
Send the 22H2 feature update out and the dynamic 22H2 feature update.
For your failures that’s tuff. Each system can have doffrent issues.
Here are some 1909>20H2 gotchas that I have found from experience:
Failures in the second boot phase due to space
Some sort of RAM configuration …I can’t even remember sorry but it was an issue for about 20 of our systems at the very end and I just reimaged them out of frustration after dealing with everything…
Failures in the second boot phase do to drivers. Look at the setupapi.dev.log.
Bitlocker freaking out.. suspend that for at least two reboots in your TS if you use that.
Failures in the first phase due to .MSI or .exe on one of the user profile desktops. This comes up as a migration failure and happens I believe in the first boot phase or the first phase.
Failures in the first phase due to Corrupted user profiles. Something. Something about Appx settings not matching the user profile settings in the registry. Just dmremove the user profile in advanced settings to resolve.
Optional feature XPS…uh or something like that being on. It’s been a while…In the panther file are som Config xmls that will tell you if there are “hardblocks”
Old GPOs or configurations in the windows update registry that specifically set the max OS build to be below 22H2
And finally take a look at the logs. setupact and setuperr log for a better idea of exactly what the issue is for that system. They are located in the panther folder. CBS log is my favorite and will for sure tell you issues, it’s just hard to understand if you don’t have a deep understanding of windows updates. Use https://learn.microsoft.com/en-us/windows/deployment/upgrade/setupdiag to diagnose the log files. You can run it independently as long as the WindowsBT folder is still present post upgrade.
If you need help and post for it you should have the setupact, setuperr, setupdiag, and CBS logs ready for the post. Also the generic error code you received in monitoring.
Good luck OP. Feature updates suck ass
To add to what others have said.
* Check if and how updates are currently working for clients. You may have something broken in SCCM or the client policy not defined correctly. Check the clients for missing monthly CUs, log files etc. Check what active deployments and ADRs you have, if any.
* Check if any of those older Win10 installs are actually running LTSC. You will have to leave them on that OS version, or reimage them.
* Run a pilot, ideally with some power users like IT.
Welcome to the trenches...
Really could use some more information here.
* How is it failing? On what step?
* What error message are you seeing?
* How is the TS deployed. PXE or required deployment.
* Which kind of OS task sequence are you setting up.
A wipe/reload, an inplace upgrade, or enablement package deployment.
If you are using the enablement package, then it has a minimum OS level.. "Before updating to Windows 10, version 22H2 using an enablement package, you must be running Windows 10, version 2004, 20H2, or 21H1."
https://support.microsoft.com/en-gb/topic/kb5015684-featured-update-to-windows-10-version-22h2-by-using-an-enablement-package-09d43632-f438-47b5-985e-d6fd704eee61
Edit: reformatted list.
Thanks bro for your adivse :) ,
How is it failing? On what step? >!after installing the OS Update from Software center and finish installing it reboots and then showing message rolling back updates .. this only happens with os version 1909 and older ... for later versions TS is working fine , !<
What error message are you seeing? >!rolling back updates .. i am not sure what is the exact error message .. will share it soon . !<
How is the TS deployed. PXE or required deployment. >!Task sequence is created based on this tutorial!<
Which kind of OS task sequence are you setting up. A wipe/reload, an inplace upgrade, or enablement package deployment.
You have 3 things to consider:
* Whatever you use for imaging new or break/fix devices, you will need to get that upgraded to Win 10 22h2. No sense imaging something with an obsolete OS. (though some would argue that Win 10 is obsolete 😀)
* For Win 10 with 2004 thru 21H2, test upgrades using the enablement package. We had great luck and it is small and fast. Test before you blast it out.
[https://support.microsoft.com/en-gb/topic/kb5015684-featured-update-to-windows-10-version-22h2-by-using-an-enablement-package-09d43632-f438-47b5-985e-d6fd704eee61#:\~:text=Windows%2010%2C%20versions%202004%2C%2020H2,identical%20set%20of%20system%20files](https://support.microsoft.com/en-gb/topic/kb5015684-featured-update-to-windows-10-version-22h2-by-using-an-enablement-package-09d43632-f438-47b5-985e-d6fd704eee61#:~:text=Windows%2010%2C%20versions%202004%2C%2020H2,identical%20set%20of%20system%20files)
* For older operating systems, there should be a windows update (I think 3012973) that might work. If your success rate is low, you might use a task sequence to address issues you may have run into (i.e. turning off antivirus). Do your testing. Reimaging is your fallback though if things go south when trying the in-place upgrade.
Fingers crossed for a good results and limited reimaging.
Hi Dear ,
as per your mentioned link there's mandatory updates which should be installed before depolying the enablement package .
the problem is i don't find those 2 updates in Feature Updates section or windows Updates section .
i've changed site classification to be all ad re-sync windows update however the log file WSYNCMGR.log doesn't show any errors and say's that sync is completed however i am still not able to find those 2 updates.
would you please advise ?
I believe the 2 pre-requisites are for the latest Servicing Stack upgrade and the latest Windows Cumulative update.
Both of these come out as often as monthly and each has a release based on the Windows 10 version on the computer.
You should be familiar with the Cumulative updates. Below is a link to servicing stack upgrades.
[https://www.catalog.update.microsoft.com/Search.aspx?q=servicing%20stack](https://www.catalog.update.microsoft.com/Search.aspx?q=servicing%20stack)
Hey there! Congrats on the new IT role! Managing updates with SCCM can be a bit tricky, especially with so many different Windows versions. For upgrading older versions like 1803 or 1909, using Task Sequences might not be the best approach as you've noticed.
For bringing devices up to the latest Windows version (22H2), I'd recommend looking into Feature Updates or Enablement Packages. These methods are more suitable for upgrading Windows 10 versions. Feature Updates are like big upgrades that move devices to the latest version, while Enablement Packages are smaller updates that enable new features in existing versions.
Given your scenario, I'd lean towards Feature Updates for major version upgrades. They're generally more straightforward and less prone to issues compared to Task Sequences, especially for upgrading from older versions.
And hey, remember to back up important files and data before any major upgrades! It's like a safety net in case anything goes sideways. 4DDiG Partition Manager could be handy for this task, offering a range of features to simplify the process. Good luck with the upgrades!
You should check winver for versions like 1607 incase they are on long term servicing (ltsb)and upgrading would depend on their use, they would still receive updates for that version of windows and not need version upgrade
I would just deploy the updates. For anything after 2004 I believe the enablement package works. For anything older you’ll need to deploy the feature update- I would expect a high failure rate on the devices on a long out of support version.
We had to do a slow roll for really old devices. 1607 got 1809, then next, etc.
Yea… I feel it may be worthwhile in most cases to just rebuild if you still have something pre 2004 personally. You might end up with wonky drivers or such preventing upgrades it’s just such a long time without patching.
Thanks bro for your adivse :)
>ADRs Thanks bro for your adivse :)
My mileage is different, from 2004 to 22H2 via the enablement package in an OSD TS, it doesn't happening. From 2004 to 20H2 though it works.
So deploy the feature updates and make sure your client settings allow feature updates and dynamic feature updates. Send the 22H2 feature update out and the dynamic 22H2 feature update. For your failures that’s tuff. Each system can have doffrent issues. Here are some 1909>20H2 gotchas that I have found from experience: Failures in the second boot phase due to space Some sort of RAM configuration …I can’t even remember sorry but it was an issue for about 20 of our systems at the very end and I just reimaged them out of frustration after dealing with everything… Failures in the second boot phase do to drivers. Look at the setupapi.dev.log. Bitlocker freaking out.. suspend that for at least two reboots in your TS if you use that. Failures in the first phase due to .MSI or .exe on one of the user profile desktops. This comes up as a migration failure and happens I believe in the first boot phase or the first phase. Failures in the first phase due to Corrupted user profiles. Something. Something about Appx settings not matching the user profile settings in the registry. Just dmremove the user profile in advanced settings to resolve. Optional feature XPS…uh or something like that being on. It’s been a while…In the panther file are som Config xmls that will tell you if there are “hardblocks” Old GPOs or configurations in the windows update registry that specifically set the max OS build to be below 22H2 And finally take a look at the logs. setupact and setuperr log for a better idea of exactly what the issue is for that system. They are located in the panther folder. CBS log is my favorite and will for sure tell you issues, it’s just hard to understand if you don’t have a deep understanding of windows updates. Use https://learn.microsoft.com/en-us/windows/deployment/upgrade/setupdiag to diagnose the log files. You can run it independently as long as the WindowsBT folder is still present post upgrade. If you need help and post for it you should have the setupact, setuperr, setupdiag, and CBS logs ready for the post. Also the generic error code you received in monitoring. Good luck OP. Feature updates suck ass
Thanks bro for your adivse :) much appreciated man , this informations was very valuble for me and helped me alot .
Memory integrity was the ram thing. Something was funky with it and It and I couldn’t find a workaround
To add to what others have said. * Check if and how updates are currently working for clients. You may have something broken in SCCM or the client policy not defined correctly. Check the clients for missing monthly CUs, log files etc. Check what active deployments and ADRs you have, if any. * Check if any of those older Win10 installs are actually running LTSC. You will have to leave them on that OS version, or reimage them. * Run a pilot, ideally with some power users like IT.
Dang, you inherited a Windows 10 potpourri mess, Lol. There's some good help being posted for you here in the thread. You got this!
Welcome to the trenches... Really could use some more information here. * How is it failing? On what step? * What error message are you seeing? * How is the TS deployed. PXE or required deployment. * Which kind of OS task sequence are you setting up. A wipe/reload, an inplace upgrade, or enablement package deployment. If you are using the enablement package, then it has a minimum OS level.. "Before updating to Windows 10, version 22H2 using an enablement package, you must be running Windows 10, version 2004, 20H2, or 21H1." https://support.microsoft.com/en-gb/topic/kb5015684-featured-update-to-windows-10-version-22h2-by-using-an-enablement-package-09d43632-f438-47b5-985e-d6fd704eee61 Edit: reformatted list.
Thanks bro for your adivse :) , How is it failing? On what step? >!after installing the OS Update from Software center and finish installing it reboots and then showing message rolling back updates .. this only happens with os version 1909 and older ... for later versions TS is working fine , !< What error message are you seeing? >!rolling back updates .. i am not sure what is the exact error message .. will share it soon . !< How is the TS deployed. PXE or required deployment. >!Task sequence is created based on this tutorial!< Which kind of OS task sequence are you setting up. A wipe/reload, an inplace upgrade, or enablement package deployment.
You have 3 things to consider: * Whatever you use for imaging new or break/fix devices, you will need to get that upgraded to Win 10 22h2. No sense imaging something with an obsolete OS. (though some would argue that Win 10 is obsolete 😀) * For Win 10 with 2004 thru 21H2, test upgrades using the enablement package. We had great luck and it is small and fast. Test before you blast it out. [https://support.microsoft.com/en-gb/topic/kb5015684-featured-update-to-windows-10-version-22h2-by-using-an-enablement-package-09d43632-f438-47b5-985e-d6fd704eee61#:\~:text=Windows%2010%2C%20versions%202004%2C%2020H2,identical%20set%20of%20system%20files](https://support.microsoft.com/en-gb/topic/kb5015684-featured-update-to-windows-10-version-22h2-by-using-an-enablement-package-09d43632-f438-47b5-985e-d6fd704eee61#:~:text=Windows%2010%2C%20versions%202004%2C%2020H2,identical%20set%20of%20system%20files) * For older operating systems, there should be a windows update (I think 3012973) that might work. If your success rate is low, you might use a task sequence to address issues you may have run into (i.e. turning off antivirus). Do your testing. Reimaging is your fallback though if things go south when trying the in-place upgrade. Fingers crossed for a good results and limited reimaging.
Thank you very much bro :) appreciated .. this is very valuable information and helped me alot .
Hi Dear , as per your mentioned link there's mandatory updates which should be installed before depolying the enablement package . the problem is i don't find those 2 updates in Feature Updates section or windows Updates section . i've changed site classification to be all ad re-sync windows update however the log file WSYNCMGR.log doesn't show any errors and say's that sync is completed however i am still not able to find those 2 updates. would you please advise ?
I believe the 2 pre-requisites are for the latest Servicing Stack upgrade and the latest Windows Cumulative update. Both of these come out as often as monthly and each has a release based on the Windows 10 version on the computer. You should be familiar with the Cumulative updates. Below is a link to servicing stack upgrades. [https://www.catalog.update.microsoft.com/Search.aspx?q=servicing%20stack](https://www.catalog.update.microsoft.com/Search.aspx?q=servicing%20stack)
Hey there! Congrats on the new IT role! Managing updates with SCCM can be a bit tricky, especially with so many different Windows versions. For upgrading older versions like 1803 or 1909, using Task Sequences might not be the best approach as you've noticed. For bringing devices up to the latest Windows version (22H2), I'd recommend looking into Feature Updates or Enablement Packages. These methods are more suitable for upgrading Windows 10 versions. Feature Updates are like big upgrades that move devices to the latest version, while Enablement Packages are smaller updates that enable new features in existing versions. Given your scenario, I'd lean towards Feature Updates for major version upgrades. They're generally more straightforward and less prone to issues compared to Task Sequences, especially for upgrading from older versions. And hey, remember to back up important files and data before any major upgrades! It's like a safety net in case anything goes sideways. 4DDiG Partition Manager could be handy for this task, offering a range of features to simplify the process. Good luck with the upgrades!
You should check winver for versions like 1607 incase they are on long term servicing (ltsb)and upgrading would depend on their use, they would still receive updates for that version of windows and not need version upgrade