W10UI doesn't update WinRE.wim for 26100.1742. It appears it updates some files, but doesn't apply CU. NTLite does and WinRE.wim works well fully updated to 26100.2152.
26100 winre.wim will remain as 26100.1, it's not designed for LCU integration you should integrate SSU and SafeOSDU only proof https://forums.mydigitallife.net/posts/1856719
With using "W10UI_10.47r" only 4 of 7 updates integrated. Also cleanup stuck at %10 mean for me that component store corrupted. I am returning stable W10UI_10.44 build. It never disappoints me. Spoiler: log ============================================================ Running W10UI v10.47r ============================================================ ============================================================ Configured Options... ============================================================ Cleanup ResetBase ISO ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Extracting .cab files from .msu files... ============================================================ 1/2: windows10.0-kb5020683-x64.msu 2/2: windows10.0-kb5026037-x64.msu ============================================================ Extracting files from update containers (cab/wim)... *** This will require some disk space, please be patient *** ============================================================ 1/7: windows10.0-kb5003791-x64-ltscsurumlerEP.cab [Enablement] 2/7: Windows10.0-KB5020683-x64_PSFX.cab 3/7: Windows10.0-KB5026037-x64_PSFX.cab 4/7: Windows10.0-KB5043130-x64.cab [SSU] 5/7: Windows10.0-KB5044273-x64.cab [LCU] 6/7: Windows10.0-KB5044615-x64.cab [SafeOS DU] 7/7: Windows10.0-KB5045523-x64.cab [Setup DU] ============================================================ Mounting sources\install.wim - index 1/1 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_4950~31bf3856ad364e35~amd64~~19041.4950.1.5 [==========================100.0%==========================] The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.19041.1 Processing 1 of 3 - Adding package Package_for_KB5003791~31bf3856ad364e35~amd64~~10.0.1.2 [==========================100.0%==========================] Processing 2 of 3 - Adding package Package_for_KB5020683~31bf3856ad364e35~amd64~~19041.2304.1.3 [==========================100.0%==========================] Processing 3 of 3 - Adding package Package_for_KB5026037~31bf3856ad364e35~amd64~~19041.2845.1.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.5011.1.13 [==========================100.0%==========================] The operation completed successfully. ============================================================ Resetting OS image base... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.19044.5011 [===== 10.0% ] [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.19044.5011 [==========================100.0%==========================] The operation completed successfully. ============================================================ Unmounting sources\install.wim - index 1/1 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image File : D:\26100\sources\install.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Rebuilding sources\install.wim ... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Exporting image [==========================100.0%==========================] The operation completed successfully.
log is incomplete everything is ok in the provided part of the log p.s. you don't need OOBE updates at all in any case
I am working on 19044.1 image not on 19044.1288. Again no need? In here says also no need https://forums.mydigitallife.net/th...h1-22h2-vb_release.80763/page-16#post-1571109 but he is working with 19044.1288 build. Why he writes the updates then if no need does not need to write anywhere of the topic.
all OOBE updates will eventually be included in future LCUs these updates are for those who want to upgrade to the newest windows build at OOBE stage, which makes no sense at all for our use case these updates are dynamic and not needed for your install.wim, winre.wim or boot.wim it's a complete waste of time and resources MSFT ISO never include OOBE updates as well, nobody needs it in ISO
Thank you. I understood well. Do we need this ones for install.wim or just for winpe etc? Can you answer below too. windows10.0-kb5045523-x64_DU_Sources_5000.cab "It does not have update.mum in it. For to update dvd home folders? How to use? windows10.0-kb5044615-x64_DU_SafeOS_5000.1.0.cab
SafeOS DU is only for winre.wim 19041: SSU + SafeOS 22621: SSU + SafeOS + LCU 26100: SSU + SafeOS Sources DU is just a bunch of files inside the cab archive, it's for the sources folder in the ISO and for the sources folder in the 2nd index of boot.wim, W10UI integrates it correctly pre 26100 builds: setup.exe in the ISO sources folder should match the one in the sources folder of the 2nd index of boot.wim 26100 and later builds: setup.exe and setuphost.exe should match
That can't be true, can it? NTLite can update it fully without issues. Perhaps W10UI should allow for optional WinRE.wim LCU integration?
just check MSFT ISO and you'll see that you can't integrate LCU into winre.wim for 26100 builds we don't need frankenbuild options in W10UI
on english iso with .2033 update everything works. problem is with different language - search, explorer and right-clik context menu not working, menu start button not visible
Good evening, I have a small problem, my Windows 11 24 H2 LTSC 2024 was activated with KMS38, now it suddenly loses the activation, the Office Pro 2024 LTSC, remains activated. I know this does not belong here, program was M** 27 controlled via Powershell in online mode, and activated. Normally the KMS38 has always worked and never lost the activation server. Now I have installed the wlan antenna in my computer today, so Lan to Wlan, there was no problem. Suddenly, hours later, Windows is not activated, which shouldn't be related, should it? # Current Build Windows 11 EnterpriseS LTSC 24H2 26100.2033 Log, I'll add it, if the whole thing is unwanted please delete the thread. I used the M**27 for the first time for the KMS38 Code: ============================================================ === Windows Status === ============================================================ Name: Windows(R), EnterpriseS edition Description: Windows(R) Operating System, VOLUME_KMSCLIENT channel Activation ID: 32d2fab3-e4a8-42c2-923b-4bf4fd13e6ee Extended PID: 03612-04250-000-000002-03-1031-26100.0000-2862024 Product Key Channel: Volume:GVLK Partial Product Key: J462D License Status: Notification Notification Reason: 0xC004F056 Configured Activation Type: All Please activate the product in order to update KMS client information values. ____________________________________________________________ Client Licensing Check information: AppId=55c92734-d682-4d71-983e-d6ec3f16059f LastConsumptionReason=0xc004f056 LastNotificationId=VolumeUnlicensed LicenseState=SL_LICENSING_STATUS_NOTIFICATION PartialProductKey=J462D ProductKeyType=Volume:GVLK SkuId=32d2fab3-e4a8-42c2-923b-4bf4fd13e6ee ruleId=eeba1977-569e-4571-b639-7623d8bfecc0 uxDifferentiator=ENVIRONMENT volumeActivationOrder=normal LastActivationHResult=0xc004f074 IsWindowsGenuine=SL_GEN_STATE_INVALID_LICENSE IsDigitalLicense=FALSE SubscriptionSupportedEdition=FALSE SubscriptionEnabled=FALSE ____________________________________________________________ ============================================================ === Office Ohook Status === ============================================================ Ohook for permanent Office activation is installed. You can ignore the below mentioned Office activation status. ============================================================ === Office Status === ============================================================ Name: Office 24, Office24ProPlus2024VL_MAK_AE1 edition Description: Office 24, RETAIL(MAK) channel Activation ID: d77244dc-2b82-4f0a-b8ae-1fca00b7f3e2 Extended PID: 03612-05025-000-000000-03-1031-26100.0000-2862024 Product Key Channel: Volume:MAK Partial Product Key: TF8CP License Status: Initial grace period Time remaining: 37293 minute(s) (26 day(s)) Initial grace period ends 2024-11-11 05:43:34 ____________________________________________________________ Press any key to Go back... Unlocking it again probably shouldn't be a problem. I just left everything as it is in case I can pass on some information.
It's not allowed to discuss it in depth here, let alone supported. Go to the support discord (you can find it by searching for the info in my sig) and ask there. Changing (W)LAN most likely makes your system id different, kms38 is kinda hwid but vl.
now I wanted to know, so KMS_VL_ALL_AIO_v53 the first thing I do is uninstall 2.7, and fix first attempt did not work
Code: Installing Local KMS Emulator... Adding File and Windows Defender exclusion... C:\WINDOWS\System32\SppExtComObjHook.dll Adding Registry Keys... [HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\SppExtComObj.exe] [HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\osppsvc.exe] Adding Scheduled Task... \Microsoft\Windows\SoftwareProtectionPlatform\SvcTrigger ____________________________________________________________ Activation Mode: Auto Renewal Converting Office C2R Retail-to-Volume: ProPlus 2024 Suite Activating: Windows(R), EnterpriseS edition Product Activation Failed: 0x8007000D Remaining Period: 0 days (0 minutes) Installing Key: Office 24, Office24ProPlus2024VL_KMS_Client_AE edition Activating: Office 24, Office24ProPlus2024VL_KMS_Client_AE edition Product Activation Successful Remaining Period: 180 days (259200 minutes) No Installed Office 2010 Product Detected... ____________________________________________________________ Make sure to exclude this file in the Antivirus protection. C:\WINDOWS\System32\SppExtComObjHook.dll Press any key to continue . . . hmm hier the Debbug Log: https://krakenfiles.com/view/NuwpBulNnZ/file.html Code: Installing Local KMS Emulator... Adding File and Windows Defender exclusion... C:\WINDOWS\System32\SppExtComObjHook.dll Adding Registry Keys... [HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\SppExtComObj.exe] [HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\osppsvc.exe] Adding Scheduled Task... \Microsoft\Windows\SoftwareProtectionPlatform\SvcTrigger ____________________________________________________________ Activation Mode: Auto Renewal Converting Office C2R Retail-to-Volume: ProPlus 2024 Suite Activating: Windows(R), EnterpriseS edition Product Activation Failed: 0x8007000D Remaining Period: 0 days (0 minutes) Installing Key: Office 24, Office24ProPlus2024VL_KMS_Client_AE edition Activating: Office 24, Office24ProPlus2024VL_KMS_Client_AE edition Product Activation Successful Remaining Period: 180 days (259200 minutes) No Installed Office 2010 Product Detected... ____________________________________________________________ Make sure to exclude this file in the Antivirus protection. C:\WINDOWS\System32\SppExtComObjHook.dll Press any key to continue . . . ALL OK Code: ============================================================ === Windows Status === ============================================================ Name: Windows(R), EnterpriseS edition Description: Windows(R) Operating System, VOLUME_KMSCLIENT channel Activation ID: 32d2fab3-e4a8-42c2-923b-4bf4fd13e6ee Extended PID: 03612-04250-000-000002-03-1031-26100.0000-2902024 Product Key Channel: Volume:GVLK Partial Product Key: J462D License Status: Licensed Volume activation expiration: 6972894 minute(s) (4842 day(s)) Configured Activation Type: All Key Management Service client information: Client Machine ID (CMID): 1b5a1c50-b453-436b-bc6b-31c0670f8c0b Registered KMS machine name: 127.0.0.2:1688 KMS machine IP address: 127.0.0.2 KMS machine extended PID: Activation interval: 120 minutes Renewal interval: 10080 minutes KMS host caching: Enabled Volume activation will expire 2038-01-19 05:13:22 ____________________________________________________________ Client Licensing Check information: AppId=55c92734-d682-4d71-983e-d6ec3f16059f GraceEndDate=2038/01/19:03:14:06 LastConsumptionReason=0x00000000 LastNotificationId=VolumeRenewalRequired LicenseState=SL_LICENSING_STATUS_LICENSED PartialProductKey=J462D ProductKeyType=Volume:GVLK SkuId=32d2fab3-e4a8-42c2-923b-4bf4fd13e6ee ruleId=502ff3ba-669a-4674-bbb1-601f34a3b968 uxDifferentiator=ENVIRONMENT volumeActivationOrder=normal LastActivationHResult=0x8007000d IsWindowsGenuine=SL_GEN_STATE_IS_GENUINE IsDigitalLicense=FALSE SubscriptionSupportedEdition=FALSE SubscriptionEnabled=FALSE ____________________________________________________________ ============================================================ === Office Ohook Status === ============================================================ Ohook for permanent Office activation is installed. You can ignore the below mentioned Office activation status. ============================================================ === Office Status === ============================================================ Name: Office 24, Office24ProPlus2024VL_KMS_Client_AE edition Description: Office 24, VOLUME_KMSCLIENT channel Activation ID: 8d368fc1-9470-4be2-8d66-90e836cbb051 Extended PID: 03612-05024-000-000000-03-1031-26100.0000-2902024 Product Key Channel: Volume:GVLK Partial Product Key: GCVGB License Status: Licensed Volume activation expiration: 259190 minute(s) (180 day(s)) Configured Activation Type: All Key Management Service client information: Client Machine ID (CMID): 1b5a1c50-b453-436b-bc6b-31c0670f8c0b Registered KMS machine name: 172.16.0.2:1688 KMS machine IP address: 172.16.0.2 KMS machine extended PID: 03612-00206-603-751322-03-1031-26100.0000-2882024 Activation interval: 120 minutes Renewal interval: 10080 minutes KMS host caching: Enabled Volume activation will expire 2025-04-14 10:09:23 ____________________________________________________________ Press any key to continue . . .
Hello again friend, is there a place to find your latest Win11 personal tweaks batch file? THANK YOU. Still using your W10 tweaks.
@abbodi1406 Is there a tool (other than WinSxSv1) that can be used to capture Windows editions? For example, "Microsoft-Windows-EditionSpecific-EnterpriseS-Package"? I tried WinSxSv1 to capture a 26100.1 image but I'm not successful. I suppose there are alternatives. Thanks in advance.
@abbodi1406 Just an update for W10UI for 24H2 LCUmsuExpand = 1 works fine on Win 11 2024 Boring AI edition when tested on 23H2 with stock Dism version and much faster integration process taking under 1 hr including ESD conversion. There are few bugs and few of my drivers are on upgrade blocklist but its working without any issues. I did use Dism's hidden command line switches to remove Edge Browser and keep only WebView on Windows 11 which knocked off 2GB of WIM file size for all editions and managed to keep disk footprint of 9GB on Home edition and 11GB on Pro edition fresh installs on VM. ISO size is back to 4.4GB instead of 5.5-6.5GB Is there a possibility to add Edge and EdgeWebView removal settings in an ini file for W10UI.cmd?