FWT

Upgrading to IoT LTSC 22H2

FWT
Apr 30th, 2025 (edited)
18,621
1
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.70 KB | None | 1 0
  1. UPDATE:
  2. 22H2 no longer receives updates so this is no longer recommended or useful.
  3. If you've done this previously, you should undo this to revert back to 21H2 which still gets support.
  4.  
  5. Follow the same steps as upgrading, but for the final step, run this instead:
  6. Dism /online /remove-package /packagepath:microsoft-windows-22h2enablement-package~31bf3856ad364e35~amd64~~10.0.19041.1799.mum /NoRestart
  7. Restart and you'll be back on IoT LTSC 21H2.
  8.  
  9.  
  10.  
  11. UPGRADING FROM 21H2 TO 22H2:
  12. Download this: https://catalog.s.download.windowsupdate.com/c/upgr/2022/07/windows10.0-kb5015684-x64_523c039b86ca98f2d818c4e6706e2cc94b634c4a.msu
  13. Extract it then look for this file: Windows10.0-KB5015684-x64_PSFX.cab
  14. Extract that into a folder, then open that extracted folder
  15. Start PowerShell as admin inside that folder
  16. (File > PowerShell > PowerShell as Admin)
  17. Paste and run this:
  18. Dism /online /add-package /packagepath:microsoft-windows-22h2enablement-package~31bf3856ad364e35~amd64~~10.0.19041.1799.mum
  19. Restart and you'll have IoT LTSC 22H2.
  20.  
  21. You can easily reverse this with /remove-package later if you want to for some reason.
  22.  
  23.  
  24.  
  25. DETAILS:
  26. (2004)/20H1, 20H2, 21H1, 21H2, and 22H2 all have completely identical code bases. The only differences is how the features were gradually tested and released (aka enabled by a tiny patch that flipped a switch). For 21H2 (build 19044) to 22H2 (build 19045) there were almost no changes besides a numerical increment because it was simply time for a yearly release. Most of the Windows development team had already moved to Windows 11 development by 22H2's release.
  27.  
  28. Microsoft has their own page explaining this:
  29. https://support.microsoft.com/en-us/topic/kb5015684-featured-update-to-windows-10-version-22h2-by-using-an-enablement-package-09d43632-f438-47b5-985e-d6fd704eee61
  30.  
  31. For end users, this might mean a game complaining you're not on 22H2 even though the game doesn't actually have any reason to need 22H2 and would run perfectly fine on even on 20H1.
  32. In the case of IoT LTSC 21H2, there are no problems as of yet, the only actual "problem" is that in the Xbox app it will give you a warning message that your version of Windows is no longer supported since the Xbox app is not normally available on LTSC and is only considering consumer editions where 21H2 is already EoL. It has no effect on functionality otherwise.
  33.  
  34. If you REALLY REALLY just want to be rid of that warning message, you can install the 22H2 update manually to change your edition to 22H2 and enable its last remaining "features."
  35. This will remove the warning from the Xbox app without even updating it, because the warning literally does nothing besides check your version number, and has never had any effect on functionality.
Advertisement
Add Comment
Please, Sign In to add comment