I did just that. Moved every thing to C:\Work Also changed the Win 10 ISO to this: en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483 Created the ISO with no warnings: Spoiler ============================================================ Win 11 Boot & Upgrade FiX KiT v1.4b... ============================================================ ================================================================================ Select the desired FiX... ================================================================================ [ 1 ] - Put the Win 11 install.wim/esd in a Win 10 ISO (Provide a Win 10 ISO in the "Source_ISO\W10\" Folder) This method is usefull for clean installs from boot, using the standard W10 setup. [ 2 ] - Integrate Diskpart & Apply Image script (v1.28) and replace "appraiserres.dll" with one from a 1703 ISO This method enables you to use the alternative Diskpart & Apply Image installation script and circumvent "TPM 2.0 is required" error when (inplace) upgrading. ================================================================================ * Type your option and press Enter: 1 Extracting Source ISO... 7-Zip 19.00 (x86) : Copyright (c) 1999-2018 Igor Pavlov : 2019-02-21 Scanning the drive for archives: 1 folder, 1 file, 3577901056 bytes (3413 MiB) Extracting archive: Source_ISO\W10\en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483.iso -- Path = Source_ISO\W10\en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483.iso Type = Udf Physical Size = 3577901056 Comment = CES_X64FREV_EN-US_DV5 Cluster Size = 2048 Created = 2016-07-17 0230 Everything is Ok Folders: 96 Files: 987 Size: 3572824357 Compressed: 3577901056 Deleting W10 install.wim/esd Extracting Win 11 install.wim/esd to work dir... ========================================================= 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 13 directories) Scanning source tree complete (987 files in 97 directories) Computing directory information complete Image file is 4764270592 bytes (before optimization) Writing 987 files in 97 directories to Win10_With_21996.1_x64_en-US_install.wim_2021-06-27.iso 100% complete Storage optimization saved 11 files, 667648 bytes (0% of image) After optimization, image file is 4765822976 bytes Space saved because of embedding, sparseness or optimization = 667648 Done. Press any key to continue . . . End result was still the same. Got to keyboard language chose english United Kindom, hit Shift + F10. Got the cmd prompt x:Sources; typed in Code: menu and once again was immediatelyinformed that: Code: menu' is not recognised as an internal or external command, operable program or batch file cheers postscript: fired up virtualbox, installed the latest Win10_With_21996.1_x64_en-US_install.wim_2021-06-27.iso and it failed at exactly the same place: x:\Sources. No command called menu is recognised. Ah well. I'm away for a while now. The only system that has worked for me so far has been to replace the dll and then upgrade in place of an earlier Windows 10 installation. I did so much want a clean install on my mbr legacy bios machine. Win10_With_21996.1_x64_en-US_install.wim_2021-06-27.iso
Forget said funny thinks i have get last days, on boot windows 11, i have get windows 10 start menu after it have execute fix disk durring boot, so i have thinks, is funny too see, winbsows 11 keep have windows 10 start menu inside Off course, after rebbot windows 11 start menu is back, and i have never re get this "bug"
I see where you are getting hung up. Option 1 only copies the install.wim from the leak and puts it in the win10 iso. It does not copy over my diskpart/apply image script at all. In fact if you read the instructions it tells you that. The shift-f10 and "menu" is to start my script. You can't start the script if there is no script copied.
Yea, seems like win 11 is just win 10 with a new UI and not so more. even programs like aida64 still reporting the OS name as "windows 10" Spoiler
Remember that this build is a leaked early version one. Programs like AIDA64 may state in early builds that these builds are from Windows 10. I remember that in the very first build of Windows 10 Technical Preview, programs like AIDA64 said that the OS was Windows 8.1. Let's give it some time in order to get everything updated.
I would be glad if we could throw a spanner in the works so that old devices could install Windows 11.