I recently used your AIO 1 option on your latest toolkit the past month and it worked good from W10 to W11 Ent which now it's updated to 24H2 (26100.7019). WU won't prompt me to update to 25H2 (26200.7019) as I know my processor doesn't meet spec (6700k). I do have a TPM module. I have access to KB5054156 enablement which should work though haven't ran it to test...is there something I'm missing or a better method to enable the 25H2 feature update ? You noted on post#2 For WU upgrades use BAU/AveYo's script tpm upgrade script, but also note obsolete, so wasn't sure about it. Thanks for the great work and response.
I tried a UUDUMP ISO of 26H1 (x64) on a Surface laptop SE. (UEFI + TPM active) When I select "IoT Enterprise" during the setup, I keep ending up with Windows SE Insider Preview + watermark and cant create an offline account, as it keeps loosing connection. (Ice Cream Cone Oops) Installing Pro installs as Pro, has not a problem creating an offline account. Installing Enterprise installs as Enterprise, has not a problem creating an offline account. I guess installing "IoT Enterprise" might be the culprit here? Maybe I am missing something here?
Updates don't check for the windows 11 system requirements, once you're on 26100 the updates will be installed fine, including the small 25H2 EP.
Thanks for the response and your time. I wonder why the machine is staying at 26100.7019 instead of 26200.7019 using WU. From understanding, MS rolled out slowly 25H2 but that was awhile ago...figured it would be available for me by this point...my machine is left at 24H2 with no WU showing at this point. "get updates as soon as they are available is checked". Any suggestion or comments for me to explore?
Because iot enterprise are oem only , after install windows use key from motherboards To avoid this and keep iot enterprise advantage use iot enterprise k ( subscription ) because this edition have oem and retail license Retail = force windows to use key from iso
What is this about? Setup from an oem/retail iso checks for the MSDM key, that can be circumvented by using a pid or ei.cfg, after setup is finished then the install should not change anymore, only when you insert a key for another sku. Specific hardware deliverd with a certain locked OS can give problems when installing another SKU. But again, this is not related to the subject of this thread. @itsmemario1 what indexes does the used ISO contain and does the ISO include the (generic) ei.cfg*? * generic ei.cfg Code: [Channel] _Default [VL] 0 Put this in the "ISO:\Sources" folder, it will enable you to select any of the available SKUs on the ISO, with 24H2+ setup use the "legacy/previous setup" option else the ei.cfg will probably be ignored.
Code: ============================================================= Win 11 Boot & Upgrade FiX KiT v6.1 By Enthousiast @MDL... ============================================================= =================================== Fixes ==================================== [ 1 ] {*} AIO 1 : UFWS + setup.cfg (2022/2025) [ 2 ] { } AIO 2a: boot.wim Registry + winsetup.dll [ 3 ] { } AIO 2b: Current OS Registry =================================== Extras =================================== [ 6 ] {*} Replace ISO appraiserres.dll [ 7 ] {*} Integrate Diskpart & Apply Image script [ 8 ] {*} Add the generic EI.CFG file [ 9 ] {*} Optimize boot.wim [ A ] {*} Add 22621 Autorun.dll to 26100 (And higher) Boot.wim (Only use this option when the ISO is already updated!) ============================================================================== Select desired option(s), then press 0 to start the process: 0 ========================================================= Extracting Win 11 Source ISO... ========================================================= 7-Zip 21.07 (x86) : Copyright (c) 1999-2021 Igor Pavlov : 2021-12-26 Scanning the drive for archives: 1 file, 5680465920 bytes (5418 MiB) Extracting archive: E:\Crappy_Tools\Win_11_Boot_And_Upgrade_FiX_KiT_v6.1f2\Source_ISO\28000.1.251103-1709.BR_RELEASE_CLIENTMULTI_X64FRE_EN-US_DaRT_11_2025_11_14.ISO -- Path = E:\Crappy_Tools\Win_11_Boot_And_Upgrade_FiX_KiT_v6.1f2\Source_ISO\28000.1.251103-1709.BR_RELEASE_CLIENTMULTI_X64FRE_EN-US_DaRT_11_2025_11_14.ISO Type = Udf Physical Size = 5680465920 Comment = Win_11_28000_x64_en-US Cluster Size = 2048 Created = 2025-11-15 01:00:00 Everything is Ok Folders: 91 Files: 969 Size: 5674852125 Compressed: 5680465920 ============================================================= Copying the generic ei.cfg to the work dir... (If exists, the original file will be renamed to EI.CFG.Ori) ============================================================= 1 file(s) copied. ============================================================= Applying UFWS v1.4 to install.wim (Circumvent CPU-Disksize-RAM-TPM-Secureboot checks) ============================================================= ============================================================= Replacing setup.cfg for ISO dir & boot.wim (The original file will be renamed to setup.cfg.bak) ============================================================= 1 file(s) copied. Scanning "Files\setup2025.cfg" (loading as WIM path: "\sources\inf\setup.cfg")... 1936 bytes scanned (1 files, 0 directories) Updating "\sources\inf\setup.cfg" in WIM image Using LZX compression with 1 thread Archiving file data: 1936 bytes of 1936 bytes (100%) done ============================================================= Replacing Win11 appraiserres.dll with Win10 15063 (The original file will be renamed to appraiserres.dll.bak) ============================================================= 1 file(s) copied. ============================================================= Adding Murphy78 Diskpart and Apply Image Script 1.4.3 To Boot.wim... ============================================================= Scanning "Files\murphy78-DiskPart-Apply-v1.4.3\x64\" 10 MiB scanned (164 files, 15 directories) Using LZX compression with 16 threads Archiving file data: 10 MiB of 10 MiB (100%) done ============================================================= Optimizing boot.wim... ============================================================= "WORK\Sources\boot.wim" original size: 556997 KiB Using LZX compression with 16 threads Archiving file data: 1431 MiB of 1431 MiB (100%) done "WORK\Sources\boot.wim" optimized size: 553705 KiB Space saved: 3292 KiB ============================================================= Adding 22621 Autorun.dll to 26100 (or later) boot.wim... ============================================================= Scanning "Files\autorun_22621.dll" (loading as WIM path: "\sources\autorun.dll")... 169 KiB scanned (1 files, 0 directories) Updating "\sources\autorun.dll" in WIM image Using LZX compression with 1 thread Archiving file data: 169 KiB of 169 KiB (100%) done ========================================================= Creating x64 ISO... ========================================================= OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2012. All rights reserved. Licensed only for producing Microsoft authorized content. Scanning source tree (500 files in 47 directories) Scanning source tree complete (986 files in 96 directories) Computing directory information complete Image file is 5740101632 bytes (before optimization) Writing 986 files in 96 directories to 28000.1.251103-1709.BR_RELEASE_CLIENTMULTI_X64FRE_EN-US_DaRT_11_2025_11_14_FIXED_2025_11_14.ISO 100% complete Storage optimization saved 5 files, 28672 bytes (0% of image) After optimization, image file is 5742288896 bytes Space saved because of embedding, sparseness or optimization = 28672 Done. Press 9 or q to exit.
Every Windows 11 ISO I've tried results in "no iso file detected". I've tried 23H2, 24H2, and 25H2 iso files. What the heck am I doing wrong?
Seems you have 2 ISOs in the folder, never a good idea The ISO selection option can find specific ISOs but i never tested with more then 1 iso in the source_iso folder.
Whoops. I deleted the other one and kept "Win11_25H2_English_x64.iso"...it still shows the same message and asks to quit. D: What am I doing wrong, oh master of altering ISOs?