Code: ============================================================= Channel : DogfoodDevMain ============================================================= ============================================================= Checking available version . . . ============================================================= ============================================================= ERROR: could not check available version online, possible reasons: - internet connection not working - Windows Powershell is disabled - .NET Framework is not updated to support TLS 1.2 connection protocol ============================================================= Press any key to exit. There are no issues with the items listed; they were working normally yesterday. What could be the reason for this?
Maybe DNS? or temporary error? no issue here: Code: ============================================================= Channel : DogfoodDevMain ============================================================= Selected channel offer different builds per OS level: 1. build: 16.0.19218.20000 [Windows 11/10] 2. build: 16.0.16207.20000 [Windows 8.1] 3. build: 16.0.12525.20000 [Windows 7] ============================================================= > Enter Build option number, and press "Enter":
W10UI v10.53u - Minor update to fix detecting EKB version and branch for latest Windows 11 24H2/25H2 LCU thanks to @Enthousiast for debugging
WHD-W81UI v7.8 - WHD-W7UI v7.0 - Add "QualityCompat" registry to fix Windows Update supersedence chain metadata - Implement "DIR2ISO" function by AveYo to create iso (if oscdimg/cdimage are not detected) - WHD-W7UI: Fix rebuilding boot.wim - WHD-W7UI: Delete ei.cfg if install.wim have multiple images - WHD-W81UI: Create ei.cfg if not exist, or replace it if install.wim have multiple images thanks to @Windows_Addict for reporting and suggestions
uup-converter v116 - W10UI v10.54 - Change non-insider 26200 iso label to 25h2_ge_release - Move Enablement package installation order before .NET updates - Fix for 25H2 .NET Rollup mistakenly detected as .NET feature pack
Question: For Windows 11 LTSC 2024, why did W10UI not choose to skip the Enablement package like Windows 10 LTSC 2021.
EnterpriseS is on the applicability list of that Enablement, probably by accident. As a result, it is installed, and W10UI is not to blame.
Code: ============================================================ Running W10UI v10.54 ============================================================ ============================================================ Configured Options... ============================================================ LCUmsuExpand 1 UpdtBootFiles WinRE ============================================================ Extracting dpx.dll file... ============================================================ ============================================================ Extracting .cab files from .msu files... ============================================================ 1/2: windows11.0-kb5043080-x64.msu [Combined UUP] 2/2: windows11.0-kb5064081-x64.msu [Combined UUP] ============================================================ Extracting files from update containers (cab/wim)... *** This will require some disk space, please be patient *** ============================================================ 1/8: defender-dism-x64.cab 2/8: windows11.0-kb5064097-x64.cab [SafeOS DU] 3/8: windows11.0-kb5064401-x64.cab [NetFx] 4/8: windows11.0-kb5065378-x64.cab [Setup DU] 5/8: Windows11.0-KB5043113-x64_inout.cab [SSU] 6/8: Windows11.0-KB5064531-x64_inout.cab [SSU] 7/8: Windows11.0-KB5043080-x64.wim [LCU] 8/8: Windows11.0-KB5064081-x64.wim [LCU] ============================================================ Mounting sources\install.wim - index 1/1 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.5074 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.5074 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_5074~31bf3856ad364e35~amd64~~26100.5074.1.7 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_5074 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.5074 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package Package_for_DotNetRollup_481~31bf3856ad364e35~amd64~~10.0.9316.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.5074 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.5074 Image Version: 10.0.26100.1742 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.5074.1.36 [==========================100.0%==========================] Package_for_RollupFix: The specified image is no longer serviceable and may be corrupted. Discard the modified image and start again. Error: 0x80073713 Error: 14099 The specified image is no longer serviceable and may be corrupted. Discard the modified image and start again. The DISM log file can be found at C:\windows\Logs\DISM\DismLCU.log Code: 2025-09-01 03:59:44, Error DISM DISM Package Manager: PID=9340 TID=11676 Discard this Windows image and try the operation again on a new Windows image. - GetCbsErrorMsg 2025-09-01 03:59:44, Error DISM DISM Package Manager: PID=9340 TID=11676 The specified image is no longer serviceable. Unmount the image and discard your changes. Mount the original image to try the operation again. - CPackageManagerCLIHandler::ReportFailedPackage Well, Any idea? Usually had no such errors. Net35 is already enabled in the source. Maybe that's the culprit?
Tried a source without Net35 beeing enabled: Code: ============================================================ Running W10UI v10.54 ============================================================ ============================================================ Configured Options... ============================================================ Net35 LCUmsuExpand 1 UpdtBootFiles WinRE ============================================================ Extracting dpx.dll file... ============================================================ ============================================================ Extracting .cab files from .msu files... ============================================================ 1/2: windows11.0-kb5043080-x64.msu [Combined UUP] 2/2: windows11.0-kb5064081-x64.msu [Combined UUP] ============================================================ Extracting files from update containers (cab/wim)... *** This will require some disk space, please be patient *** ============================================================ 1/8: defender-dism-x64.cab 2/8: windows11.0-kb5064097-x64.cab [SafeOS DU] 3/8: windows11.0-kb5064401-x64.cab [NetFx] 4/8: windows11.0-kb5065378-x64.cab [Setup DU] 5/8: Windows11.0-KB5043113-x64_inout.cab [SSU] 6/8: Windows11.0-KB5064531-x64_inout.cab [SSU] 7/8: Windows11.0-KB5043080-x64.wim [LCU] 8/8: Windows11.0-KB5064081-x64.wim [LCU] ============================================================ Mounting sources\install.wim - index 1/11 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.5074 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.5074 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_5074~31bf3856ad364e35~amd64~~26100.5074.1.7 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_5074 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.5074 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package Package_for_DotNetRollup_481~31bf3856ad364e35~amd64~~10.0.9316.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.5074 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.5074 Image Version: 10.0.26100.1742 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.5074.1.36 [==========================100.0%==========================] The operation completed successfully. And, if I try the previous source without adding KB5064081 then add KB5064081 later, looks like it works fine, too.
Code: ============================================================ Running W10UI v10.54 ============================================================ ============================================================ Configured Options... ============================================================ Net35 Net35Source LCUmsuExpand 1 Cleanup ResetBase UseWimlib WimCreateTime WinRE ISO ============================================================ Extracting dpx.dll file... ============================================================ ============================================================ Extracting .cab files from .msu files... ============================================================ 1/1: windows11.0-kb5064081-x64_a1096145ded3adfc26f8f23442281533429f0e38.msu [Combined UUP] ============================================================ Extracting files from update containers (cab/wim)... *** This will require some disk space, please be patient *** ============================================================ 1/6: Windows11.0-KB5054156-x64.cab [Enablement] 2/6: windows11.0-kb5064097-x64_28d59d08562e574b336ca9523f6e2e0fc965687e.cab [SafeOS DU] 3/6: Windows11.0-KB5064402-x64-NDP481.cab [NetFx] 4/6: windows11.0-kb5065378-x64_ce10558e75e6d2e90cfe75d2c08a9f40fd0958dc.cab [Setup DU] 5/6: Windows11.0-KB5064531-x64_inout.cab [SSU] 6/6: Windows11.0-KB5064081-x64.wim [LCU] ============================================================ Mounting sources\install.wim - index 1/1 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.5733 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.5733 Image Version: 10.0.26100.1742 Processing 1 of 1 - Adding package Package_for_ServicingStack_5074~31bf3856ad364e35~amd64~~26100.5074.1.7 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_5074 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.5733 Image Version: 10.0.26100.1742 Processing 1 of 2 - Adding package Package_for_KB5054156~31bf3856ad364e35~amd64~~26100.5503.1.1 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_DotNetRollup_481~31bf3856ad364e35~amd64~~10.0.9317.2 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.5733 Image Version: 10.0.26100.1742 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.5074.1.36 [==========================100.0%==========================] The operation completed successfully. ============================================================ Resetting OS image base... ============================================================ [ Press 9 or q to exit.
Office Scrubber v14 - Detect if the script is launched from inside zip archive directly - Detect if WMI service is disabled - Improve detection for Office UWP - Add AIO script with embedded files (require Windows Powershell to work)
dotNetFx48-1507_1511 v4 - Add support to install .NET packages from current online OS Spoiler - this is done by patching servicing stack to allow modified mum files - you must restore servicing stack afterwards (after restart) to avoid problems with OS integrity or installing other updates - repeat the steps for each new .NET 4.8 cumulative updates thanks to @asdddsa101 for suggesting and testing
Great work but is there a script to bypass the Windows password? I need script to put it in winpe to bypass forgotten password in windows>