Would be nice to understand why when M$ updates the OS, suddenly problems appears... @abbodi1406 For offline images, your scripts are nothing less than perfect. I can't understand the errors on live systems... On Win10, all updates are flawlessly, online and offline, but in W11-24h2 all oddities happens
And i never ever have problems updating whatever OS i run, and the options you say are causing problems are not used on 26100, and also no problems on my tests: Script settings: Code: :: 1 = do not install EdgeChromium with Enablement Package or Cumulative Update :: 2 = alternative workaround to avoid EdgeChromium with Cumulative Update only set SkipEdge=1 :: do not install Edge WebView with Cumulative Update set SkipWebView=1 Progress: Code: ====================== W10UI v10.53 ======================= [1] Target (x64): Current OS [2] Updates: "E:\26100.4061" [3] DISM: "Host OS" [4] Enable .NET 3.5: YES [5] Cleanup System Image: YES [6] Reset Image Base: YES [E] Extraction Directory: "E:\W10UItemp_25564" ============================================================ Change a menu option, press 0 to start the process, or 9 to exit: Code: ============================================================ Running W10UI v10.53 ============================================================ ============================================================ Configured Options... ============================================================ Net35 LCUmsuExpand 1 Cleanup ResetBase ============================================================ Extracting .cab files from .msu files... ============================================================ 1/3: windows11.0-kb5043080-x64_LCU_1742.1.10.msu [Combined UUP] 2/3: windows11.0-kb5056579-x64-ndp481_a062e62bdedd9a2a4b0cbf4e26ff1652a240f1ee.msu 3/3: windows11.0-kb5058411-x64_LCU_4061.1.18.msu [Combined UUP] ============================================================ Extracting files from update containers (cab/wim)... *** This will require some disk space, please be patient *** ============================================================ 1/3: Windows11.0-KB5056579-x64-NDP481.cab [NetFx] 2/3: Windows11.0-KB5043113-x64_inout.cab [SSU] 3/3: Windows11.0-KB5058523-x64_inout.cab [SSU] ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.3775 Processing 1 of 1 - Adding package Package_for_ServicingStack_4060~31bf3856ad364e35~amd64~~26100.4060.1.2 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_4060 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.3775 Processing 1 of 1 - Adding package Package_for_DotNetRollup_481~31bf3856ad364e35~amd64~~10.0.9310.1 [==========================100.0%==========================] The operation completed successfully. 01742-windows11.0-kb5043080-x64_LCU_1742.1.10.msu Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.3775 Processing 1 of 1 - The operation completed successfully. 04061-windows11.0-kb5058411-x64_LCU_4061.1.18.msu Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.3775 Processing 1 of 1 - [==========================100.0%==========================] [==========================100.0%==========================] The operation completed successfully. ERROR: Access is denied. ============================================================ Adding .NET Framework 3.5 feature... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.3775 Enabling feature(s) [==========================100.0%==========================] The operation completed successfully. ============================================================ Reinstalling cumulative update(s)... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.3775 Processing 1 of 1 - Adding package Package_for_DotNetRollup_481~31bf3856ad364e35~amd64~~10.0.9310.1 [==========================100.0%==========================] The operation completed successfully. 01742-windows11.0-kb5043080-x64_LCU_1742.1.10.msu Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.3775 Processing 1 of 1 - The operation completed successfully. 04061-windows11.0-kb5058411-x64_LCU_4061.1.18.msu Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.3775 Processing 1 of 1 - [==========================100.0%==========================] [==========================100.0%==========================] The operation completed successfully. ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Finished ============================================================ ============================================================ System restart is required to complete installation ============================================================ Press 9 or q to exit. Lately (or actually since win 10 was released for the first time) most problems are caused by the users themselves, not keeping up with the info/changes, not using the latest scripts or tinkering to much with the installs/ISOs (but blame MSFT anyway) and so on... And another evening entirely wasted...
They started to put in the appx files in the LCU a few updates ago. The machine speed is not really affected by this, they are not used at updating atm.
I am still not understanding why put the appx files inside the update files, seems useless when you think on IoT LTSC... And about machine speed, if you compare 3775 version, with 4061 version, the first is lighter on aged machines and thin clients. I'm still not tested with the update released yesterday, but I should give a try. About boot times, in my thin client, version 3775 gives 5 spins and boot, while 4061 gives 32 spins to boot... I don't know if have something related with hyper-v problem or not... Something to investigate.
The LCU can be used on either of the two, the non ltsc and ltsc, let's not make separate updates again They probably are planning to update/integrate the appx on the ISO/Install by the included appx in the LCU. There is a reason that MSFT doesn't want people to run 11 on aging systems. My seconf machine supports 11 (i7 8700) but it runs better on 10. And the including of the appx inside the LCU has not really something to do with booting the system. I have set my BIOS post time to 20 seconds, to be able to press the function key in time
@Enthousiast - I agree with you, W10 runs much better in any machine, is a fact! And my thin client is not aged, but you know, Thin clients are way back in hardware configurations, even being not aged. I don't know if you agree with me, but, Windows IA, or AI features must be clearly optional, and not forced; like Microsoft do right now. I've discovered the error 770 cause on the last update, was Roxio product that made a mess in Windows codecs files. Thanks for being a gentleman, as you usually are!
Same way I found and installed Win 11 IoT LTSC ISO 26100.4061 en-us and could confirm that full localization via PowerShell works at the moment.