i hope this script will still works on windows 11 rtm.. i really want to migrate to win 11 but ill not buy a new computer for the sake of tpm cr$p..
I always use _ instead of space because of these problems, but it shouldn't be needed. That was the point I was making. It has been 26 years, there shouldn't still be problems with spaces in filenames or paths.
I have already installed Windows 11 22000.51 on a MBR with secure boot disabled , if Im trying to upgrade to 22000.65 build version it will start to download and install but after a couple restarts the install will fail , I think the install is detecting the computer doesnt have the right configuration , is this Tool make the upgrade possible ? Thank you
There might be something else going on. I installed 22000.51 on an 11 year old laptop - MBR, TPM 1.2 - and it upgraded to 22000.65 just fine.
ditto - I have a 12 year old clang banger laptop and it upgraded no problems too. If the download started then its some other problem.
I am now testing Windows 11 on my computers, one is a Core 2 with only 4G of RAM. I used this fix kit and RUFUS to build Windows to Go on external USB drives (not thumb dives). As expected they are twitchy but everything I tested so far works. I tested both methods but option 1 is my prefered choice.
Because when already on 22000.xxx no need for any fix, the updates don't do any of the requirement checks, nor is the dev channel enrollment needed for 22000.51 > 22000.65.
Option 1 is not really needed, i only added it because people weren't able to do the install.wim/esd switching. Option 2 covers all scenario's, clean install using default setup or the diskpart and apply image script and (inplace) upgrades are fixed by the appraiserres.ddl replacement.
Testing v1.8, containing murphy78-DiskPart-Apply-v1.3.0 Code: ============================================================ Win 11 Boot & Upgrade FiX KiT v1.8... ============================================================ ================================================================================ Select the desired FiX... ================================================================================ [ 1 ] - Puts 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. A generic EI.CFG file will be copied to the sources folder. [ 2 ] - Integrate Diskpart & Apply Image script (v1.3.0), modify boot.wim to skip the SB, RAM and TPM 2.0 check and replace "appraiserres.dll" with one from a 1703 ISO This method enables you to: - Use the standard Win 11 setup for clean installs on devices without Secure Boot and TPM 2.0 and low amount of RAM. - Use the alternative Diskpart & Apply Image installation script for clean installs. - Circumvent "TPM 2.0 is required" error when (inplace) upgrading. ================================================================================ * Type your option and press Enter: 2 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, 4789108736 bytes (4568 MiB) Extracting archive: Source_ISO\W11\Win10_22000.65_x64_2021-07-12_US.iso -- Path = Source_ISO\W11\Win10_22000.65_x64_2021-07-12_US.iso Type = Udf Physical Size = 4789108736 Comment = 22000.65_GiGA_AiO_x64_US Cluster Size = 2048 Created = 2021-07-12 03:17:48 Everything is Ok Folders: 84 Files: 930 Size: 4797913809 Compressed: 4789108736 ============================================================ Adding Murphy78 Diskpart and Apply Image Script 1.3.0 To Boot.wim... ============================================================ Scanning "murphy78-DiskPart-Apply-v1.3.0\x64\" 524 KiB scanned (5 files, 4 directories) Using LZX compression with 1 thread Archiving file data: 524 KiB of 524 KiB (100%) done Calculating integrity table for WIM: 428 MiB of 428 MiB (100%) done ============================================================ Modding Boot.wim to disable Secure Boot, RAM and TPM 2.0 check... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Mounting image [==========================100.0%==========================] The operation completed successfully. The operation completed successfully. The operation completed successfully. The operation completed successfully. The operation completed successfully. The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22000.65 [=========== 20.0% ] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.844 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Optimizing boot.wim... ============================================================ "WORK\Sources\boot.wim" original size: 445402 KiB Using LZX compression with 8 threads Archiving file data: 1160 MiB of 1160 MiB (100%) done "WORK\Sources\boot.wim" optimized size: 436934 KiB Space saved: 8468 KiB ============================================================ Replacing the Win 11 appraiserres.dll with one from a 1703 (15063) ISO... (The original file will be renamed to appraiserres.dll.bak) ============================================================ 1 file(s) copied. ========================================================= 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 42 directories) Scanning source tree complete (931 files in 85 directories) Computing directory information complete Image file is 4801789952 bytes (before optimization) Writing 931 files in 85 directories to Win_11_22000.65_x64_en-US_2021-07-12.iso 100% complete Storage optimization saved 24 files, 14217216 bytes (1% of image) After optimization, image file is 4789671936 bytes Space saved because of embedding, sparseness or optimization = 14217216 Done. Press any key to continue . . .
Updated the OP to Win 11 Boot And Upgrade FiX KiT v1.8 https://forums.mydigitallife.net/threads/win-11-boot-and-upgrade-fix-kit-v1-8.83724/ Changelog: Code: v1.8 Added the latest Diskpart & Apply Image v1.3.1 (@murphy78 removed the options for recovery, they are no longer supported by MSFT)
@Enthousiast I hope you're keeping the old versions somewhere - the code and resources. Just in case we end up using some weird upgrade path like installing an old version of Windows and then upgrading it. No telling what restrictions might be implemented by M$ in the future.
This script currently only supports a normal windows install format with the \sources\setup structure. If an AIO you are using has the MCT dual image structure like \x86\sources\ and \x64\sources\ then it will error out. I've added this MCT dual image support for my diskpart/apply image script and custom modified version of enthusiast's script, but I haven't added any of his other stuff. I just use it as a method of installing my script. It is included by default now since 1.3.0 and you can find it in my script thread here: https://forums.mydigitallife.net/threads/murphy78-diskpart-and-apply-image-script.53532/ Scroll down to "Get the file" to download the package. Bear in mind that you have to actually use the script to bypass the hardware checks in win11 if you use this method. @Enthousiast 's script is much easier because it allows you to use Windows' own installer without any further mods.
My tool is only meant specifically for Win 11 21996.1 and 22000.xxx+, and it only modifies boot.wim and replaces a file in the ISO sources folder, so it will work for multiple index ISOs. @murphy78 Given the above, Win 11 is x64 only, so MCT style Multi-arch ISO for Win 11 won't be released.
Yep, good point. Any AIO that includes Win11 probably wouldn't include x86 versions. Guess it's only crazy people like me who did stuff like that.
@Enthousiast - Created Windows 11 ISO from the UUP Dump, ran your 1.8 tool, selected option 2, did a clean install (I have a Xeon quad-core CPU, unsupported by Win11, no TPM and no SB), everything went well and it's running like a top, thank you so much for the tool. Quick question, when they release the final Win11, do you think I will be able to update to it? My main question is, are they checking compatibility when upgrading to newer builds?
There will be unlikely another build of co_release until October, only CUs. CUs so far don't check for the requirements (besides the basic stuff like disk space etc.). Newer builds will be co_refresh.