Dear @abbodi1406 , first thank you very much for your amazing work I hope in the future would be a Bypass for Windows 10 22H2 to receive the (IoT) LTSC updates (until 2032-01). I know one can install and use Win10 (IoT) LTSC, but sometimes is easier to deploy a Windows installation with Default UWP Apps for people that are not tech-savvy. Because in a LTSC installation, one have to install the Store (with its dependencies), then the App Installer (Win-Get), and finally some apps they use (like Snip & Sketch, Calculator, Sticky Notes, Camera, Voice Recorder) is a lot more work; instead of having a Bypass (Enabler), apply it to Win10 22H2, and just install the latest (LTSC) updates having all the default apps. The best of both worlds. Have a very nice day, dear friend.
After ESU period ends, it may not be possible. Updates are based around the edition package, so it is likely that post-ESU updates will only be made for the LTSC editions (EnterpriseS/IoTEnterpriseS), and it would cause servicing to reject them as not applicable for other editions.
Thanks for your comments. It's true that the LTSC updates could be restricted to that edition. But what about the Bypass for Windows 7 (that uses updates from Server, until 2026), and the Bypass for Windows 8.1 (using the same method to receive updates until 2026). So, it's possible to adapt LTSC updates to "normal" editions; I mean, if Server editions updates were adapted to very different versions (like Win7 or Win8), it could be easier to adapt LTSC, being almost the same base.
Windows 7 and Windows Server 2008 R2 are the same Windows build (6.1.7601), and Windows 8.1 and Windows Server 2012 R2 are likewise the same Windows build (6.3.9600). So it is not surprising that security updates for Windows Server 2008 R2 and Windows Server 2012 R2 can be applied to Windows 7 x64 and Windows 8.1 x64 with minimum effort, and Microsoft seems to be not doing anything to block the installation of the current security updates on Windows 7 and Windows 8.1. Windows 10 IoT LTSC 2021 (10.0.19044) and Windows 10 22H2 (10.0.19045) are NOT the same Windows build. At present the security updates made for LTSC 2021 and 22H2 are the same updates, and can be applied to both of them. We can expect this to be true through October 2028, when the three year ESU for Windows 10 22H2 will end. After that Microsoft can, and I think they will, restrict future updates to just the LTSC edition. I think Microsoft is already doing this on older LTSB and LTSC editions. For example, current security updates for Windows 10 LTSC 2019 (10.0.17763) cannot be installed on Windows 10 1809 (which is out of support), even though they are based on the same build.
Yes, plus everything is signed, so, fooling around with the files themselves will probably not work. If at all, there would not be an easy option.
I have issue of updating ISO of Windows 10 IoT Enterprise LTSC 2021. I don't have full W10UI log but I can find: Spoiler Code: 2025-03-08 03:46:41, Error CSI 000003d0@2025/3/7:18:46:41.609 (F) onecore\base\wcp\sil\ntsystem.cpp(3044): Error STATUS_DELETE_PENDING originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null) [gle=0x80004005] 2025-03-08 03:46:41, Error CSI 000003d1 (F) STATUS_DELETE_PENDING #4598439# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0, name= ("null")}, da = (DELETE|SYNCHRONIZE|FILE_READ_ATTRIBUTES|FILE_WRITE_ATTRIBUTES), oa = @0x9cc877bae0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[132]'\??\C:\W10UImount_30737\Windows\WinSxS\Temp\InFlight\7ed2db3c918fdb014279000070334816\00e1f13c918fdb01b879000070334816_sihclient.exe'; a:(OBJ_CASE_INSENSITIVE)}, iosb [gle=0xd0000056] 2025-03-08 03:46:41, Error CSI = @0x9cc877bd30, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid) [gle=0xd0000056] 2025-03-08 03:46:41, Error CSI 000003d2 (F) STATUS_DELETE_PENDING #4598435# from Windows::Rtl::SystemImplementation::CDirectory::Internal_DeleteRecursively(...)[gle=0xd0000056] 2025-03-08 03:46:41, Info CSI 000003d3 Direct SIL provider: Number of files opened: 11. 2025-03-08 03:46:41, Error CSI 000003d4 (F) HRESULT_FROM_WIN32(ERROR_INVALID_DATA) #4510377# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x8007000d] 2025-03-08 03:46:41, Error CSI 000003d5 (F) HRESULT_FROM_WIN32(ERROR_INVALID_DATA) #4478505# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_AddFiles(Flags = 16, a = @0x1d25edd14e0, fn = @0x1d25edd1ce0, fp = @0x1d25edd24e0, disp = 0, op = 0)[gle=0x8007000d] 2025-03-08 03:46:41, Info CBS Failed to add to transaction package: Microsoft-Windows-Printing-PMCPPC-FoD-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 [HRESULT = 0x8007000d - ERROR_INVALID_DATA] 2025-03-08 03:46:41, Error CBS Failed to stage execution package: Microsoft-Windows-Printing-PMCPPC-FoD-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1 [HRESULT = 0x8007000d - ERROR_INVALID_DATA] 2025-03-08 03:46:41, Info CBS CommitPackagesState: Started persisting state of packages 2025-03-08 03:46:41, Info CBS CommitPackagesState: Completed persisting state of packages 2025-03-08 03:46:41, Info CSI 000003d6@2025/3/7:18:46:41.781 CSI Transaction @0x1d265779060 destroyed 2025-03-08 03:46:41, Info CBS Perf: Stage chain complete. 2025-03-08 03:46:41, Info CBS Failed to stage execution chain. [HRESULT = 0x8007000d - ERROR_INVALID_DATA] 2025-03-08 03:46:41, Error CBS Failed to process single phase execution. [HRESULT = 0x8007000d - ERROR_INVALID_DATA] 2025-03-08 03:46:41, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.5440.1.15, status: 0x8007000d, failure source: Stage, start state: Resolved, target state: Installed, client id: DISM Package Manager Provider
The log would provide so much easier to read info, like the used updates, the used source build, the used settings and the real W10UI progress
Installed Security Updates: KB5049621 - Microsoft Windows security update KB5034232 - Microsoft Windows security update KB5019180 - Microsoft Windows security update KB5011071 - Microsoft Windows security update KB5011048 - Microsoft Windows security update KB5007401 - Microsoft Windows security update KB5003791 - Feature Update to Windows 10 21H2 via Enablement Package Servicing Stack Updates: Servicing Stack 10.0.19041.5547 Servicing Stack 10.0.19041.3745 Servicing Stack 10.0.19041.3562 Servicing Stack 10.0.19041.3025 Servicing Stack 10.0.19041.2300 Servicing Stack 10.0.19041.1704 Servicing Stack 10.0.19041.1371 Servicing Stack 10.0.19041.1220