New tool to fix 21996.1 boot install and upgrades: 21996 Boot And Upgrade FiX KiT v1.1 https://forums.mydigitallife.net/th...nel-co_release-leak.83658/page-4#post-1666239
I have with both the 1.0 and 1.1 version only thing I can see is an issue, but was told that its not the script is you might have to repeat the OOBE twice before the desktop loads. Both my tests with both version I had to.
I tested the new version and it works well just the repeat OOBE only issue which is really not a big deal.
Working on the (hopefully) last major change for the Boot/Upgrade FiX Tool: - adding mixed win 10 ISO with 21996.1 install.* ISO creation Option 1: Code: ============================================================ 21996 Boot & Upgrade FiX KiT v1.3... ============================================================ ================================================================================ Select the desired FiX... ================================================================================ [ 1 ] - Put the 21996 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, 4334315520 bytes (4134 MiB) Extracting archive: Source_ISO\W10\Win10_1703_English_x64.iso -- Path = Source_ISO\W10\Win10_1703_English_x64.iso Type = Udf Physical Size = 4334315520 Comment = CCSA_X64FRE_EN-US_DV5 Cluster Size = 2048 Created = 2017-03-20 02:00:00 Everything is Ok Folders: 98 Files: 1710 Size: 4325792225 Compressed: 4334315520 Deleting W10 install.wim/esd Extracting 21996 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 (1500 files in 54 directories) Scanning source tree complete (1710 files in 99 directories) Computing directory information complete Image file is 4798447616 bytes (before optimization) Writing 1710 files in 99 directories to Win10_With_21996.1_x64_en-US_install.wim_2021-06-18.iso 100% complete Storage optimization saved 18 files, 133120 bytes (0% of image) After optimization, image file is 4802048000 bytes Space saved because of embedding, sparseness or optimization = 133120 Done. Press any key to continue . . . Option 2: Code: ============================================================ 21996 Boot & Upgrade FiX KiT v1.3... ============================================================ ================================================================================ Select the desired FiX... ================================================================================ [ 1 ] - Put the 21996 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: 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, 4874553344 bytes (4649 MiB) Extracting archive: Source_ISO\W11\21996.1.210529-1541.co_release_CLIENT_CONSUMER_x64FRE_en-us.iso -- Path = Source_ISO\W11\21996.1.210529-1541.co_release_CLIENT_CONSUMER_x64FRE_en-us.iso Type = Udf Physical Size = 4874553344 Comment = CCCOMA_X64FRE_EN-US_DV9 Cluster Size = 2048 Created = 2021-05-31 02:00:00 Everything is Ok Folders: 84 Files: 932 Size: 4868902748 Compressed: 4874553344 ============================================================ Adding Murphy78 Diskpart and Apply Image Script 1.28 To Boot.wim... ============================================================ Scanning "murphy78-DiskPart-Apply-v1.2.8\x64\" 80 KiB scanned (3 files, 4 directories) Using LZX compression with 1 thread Archiving file data: 80 KiB of 80 KiB (100%) done ============================================================ Optimizing boot.wim... ============================================================ "WORK\Sources\boot.wim" original size: 364839 KiB Using LZX compression with 8 threads Archiving file data: 937 MiB of 937 MiB (100%) done "WORK\Sources\boot.wim" optimized size: 357248 KiB Space saved: 7591 KiB ============================================================ Replacing the 21996.1 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 (933 files in 85 directories) Computing directory information complete Image file is 4866211840 bytes (before optimization) Writing 933 files in 85 directories to Win_11_21996.1_x64_en-US_2021-06-18.iso 100% complete Storage optimization saved 4 files, 24576 bytes (0% of image) After optimization, image file is 4868272128 bytes Space saved because of embedding, sparseness or optimization = 24576 Done. Press any key to continue . . .
I used win10 19041.xxx iso copied boot.wim ftom it & pasted it in 21996 iso . worked for me as before installation stuck at PC is incompatible but after boot wim is replaced it worked . this time enthousaist tool worked like a charm & is a better solution then mine.
Success with Upgrade. I tried other methods but got NO because of Hardware or No Upgrade. Option. Thank you
The idea behind the script was to use official Microsoft tools only. A lot of times people will make a custom program to serve the function, but then when a new operating system comes out it completely fails because it does not use the official operating system functions. You know how you used the dism /apply-image and bcdboot? Those are both official MS functions that are included in the Windows PE build. Even something like Wimlib could be iffy if they didn't use the official latest ADK functions for the build. Diskpart is also something that comes with the winpe environment. It's harder for a normie to tinker with so to integrate a script with it is a bit harder to encourage people to learn. You can actually do a hell of a lot with them. You can make variable compressed virtual disks and attach them to your operating system. In fact I used to do this when I would do sysprep/capture/virtual machine images. There is a process to compress them right inside diskpart after you are done removing superfluous files. It's actually a wonderful program that microsoft includes in every operating system and winpe that almost nobody uses.
That is pretty excellent, man. Thanks for taking the initiative on that. I may be blind, but I don't think I could find a link to this work on the original first few posts in the thread. Any chance you could link it up? or am I just that blind? I am blind in one eye, after all. There is a reason I chose the Plissken avatar.
I've seen some tweets that people are getting their Microsoft accounts suspended/terminated due to using the accounts with the leaked build. Is there any truth to this?