The ESU is determined by the Win10-ClipESU-Enabled value defined in the License. [AC] Win10-ClipESU-Enabled 1 (enabled) [LTSC and EnterpriseG] Win10-ClipESU-Enabled 0 (disabled)
Of course, so far the index of this thread contains Starter builds such as: Windows 10 Starter 14393.0 (1607) x86/x64 with LTSB style versions (somewhat cleaner) or Official Style versions (somewhat similar to an official Starter client system). Windows 10 Starter 10586.0, which is also built with official Starter packages. Windows 10 Starter 15063.0 currently has limited functionality, as its Language Packs (LPs) were in UUPDUMP and Microsoft discontinued them. For now, only the English LP has been recovered; I don't have access to the other LPs. I invite you to view the current index of the thread to be sure: https://forums.mydigitallife.net/th...-editions-reconstructions.88605/#post-1850491
Spoiler: 19044.6809 Failed, CBS.log Code: 2026-01-13 22:38:42, Error CSI 00000085@2026/1/13:13:38:42.195 (F) onecore\base\wcp\componentstore\csd_locking.cpp(95): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null) [gle=0x80004005] 2026-01-13 22:38:42, Error CSI 00000086 (F) STATUS_SXS_ASSEMBLY_MISSING #831618# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c] 2026-01-13 22:38:42, Error CSI 00000087 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #831473# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = MSMQ-Driver-Deployment, version 10.0.19041.5678, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'MSMQ-Driver-Package~31bf3856ad364e35~amd64~~10.0.19041.5678.0639b5bc8e01ca7708c434aaf16c8df3', rah = (null), manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701] 2026-01-13 22:38:42, Info CBS Failed to pin deployment while resolving Update: MSMQ-Driver-Package~31bf3856ad364e35~amd64~~10.0.19041.5678.0639b5bc8e01ca7708c434aaf16c8df3 from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING] 2026-01-13 22:38:42, Info CBS Failed to bulk stage deployment manifest and pin deployment for package:Microsoft-Windows-MediaPlayer-Payload-Package~31bf3856ad364e35~amd64~~10.0.19041.6691 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING] Also, I didn't reconstructed, I used official LTSC 2021 ISO
I also realized Windows 11 EnterpriseG 23H2 aren't getting updates from WU, I need to install manually. Is there any fix for WU?
Q: gailium119 shares 19045 SSU ESUpatch for "amd64". How to do "x86" and "arm64"? Code: ------------------------------------------------------------ Add Servicing Stack update to IoTEnterpriseS image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_6575~31bf3856ad364e35~arm64~~19041.6575.1.4 [==========================100.0%==========================] An error occurred - Package_for_ServicingStack_6575 Error: 0x800736cc Error: 14028 A component's file does not match the verification information present in the component manifest. The DISM log file can be found at C:\windows\Logs\DISM\dism.log
Maybe I was dualbooting with Windows 11 24H2 IoTEnterpriseS, also I used 24H2's bootloader that the boot partition maybe caused... Offline Integration with W10UI had no issues
Monthly rebuild of 26h1 winpe.wim 28000.1 to professional 28000.1450 with sku winosr25 Code: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Mount image :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Deployment Image Servicing and Management tool Version: 10.0.28000.1 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Clean Microsoft-Windows-EditionPack-Core-WOW64-Package ============================================================ 1 fichier(s) copié(s). 1 fichier(s) copié(s). remove Microsoft-Windows-WinPE-SKU-Foundation-WOW64-merged-Package remove Microsoft-Windows-WinPE-SKU-Foundation-merged-Package :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: convert 28000.1 :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1 Removing package Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.28000.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Applying image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1450 Processing 1 of 1 - Adding package Microsoft-Windows-Defender-Removal-Package~31bf3856ad364e35~amd64~~10.0.32767.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1450 Applying package servicing unattend [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1450 Set SKU default settings for: fr-fr The operation completed successfully. ============================================================ clean image ============================================================ :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: add Winosr25 :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Deployment Image Servicing and Management tool Version: 10.0.28000.1 Applying image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1450 Starting to install product key... Finished installing product key. The operation completed successfully. 1 fichier(s) copié(s). Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1450 The operation completed successfully. ============================================================ reset base ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image Version: 10.0.28000.1450 [==========================100.0%==========================] The operation completed successfully. ============================================================ Save and Unmount image ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Image File : C:\winosr25\winpe.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Export image ============================================================ Deployment Image Servicing and Management tool Version: 10.0.28000.1 Exporting image [==========================100.0%==========================] The operation completed successfully.
installed 19045.6456 enterpriseeval constructed by MUCS, then audit mode and unfortunately still .6456 after installing .6809 msu i can't figure it out how xinso did that (without esu bypass/patch) https://forums.mydigitallife.net/th...s-reconstructions.88605/page-209#post-1902250
[About 19041 Evaluation] It seems that iamaHUN once reverted 19041.1288 Eval packages to 19041.1, and we had tested it. [About 19045 ESU] I had told you that it is controlled by AC License Product Policy "Win10-ClipESU-Enabled" value 1. So: Firstly, you temporarily add LTSC License and Key. Then restart. Its ESU Product Policy value will be "0" (disabled). You can install CU now. Lastly, change Key back to AC and restart, it is up-to-date AC. [Recommendation for install.wim] gailium119's SSU solution which allows offline CU integration to install.wim. https://forums.mydigitallife.net/th...s-reconstructions.88605/page-209#post-1902565