Check what option 1 does, but option 1 is not the best option to use, when the win 10 ISO used is of a lower build than the install to be upgraded it won't upgrade.
Well, you finally figured it out This will save you from problems with any installation method, both with a clean installation and with an in-place update (system requirements for win10 will apply) Actually, I don't use these settings in the builds I make for myself, since I always install using WinNTSetup, which immediately unpacks installl.wim during installation, although I have long tested the full Bypass tweak on an old PC, and then suggested adding a setting for the CPU (I had already tested by that time that it doesn't work when updating in place). And if I need an ISO for other purposes, then I create a Win11 ISO using the Win10 installer - build 21390.2025 ISO, which I suggested to you.
I ask if it is better to just make the replacement of the "install.vim" file in manual way by opening the ISO, it would be faster for me. Or using the "Win 11 Boot and Upgrade Fix Kit tool" Thanks.
I don't know what's more convenient for you, it's up to you. And that's exactly what I do - I replace MANUAL install.wim, I've already written it to you several times) I generally work with install.wim in Toolkit anyway, as I don't use the original images for installations, so there is no need to use additional tools. After processing the install.wim, I apply the changes and save to Toolkit and create a new ISO UPD. I want to add, although these details do not directly relate to your question, but to make it clearer, it is probably better to explain. The fact is that my tasks, as you probably already understood, are not limited to adding Workarounds for installing win11. ISO at this stage is created as a backup. Then I close the Toolkit, and I specify the Toolkit\DVD folder as the source in NTLite (free), where I have additional tasks: removing some system components that cannot be removed using DISM and ToolkitHelper, some System apps whose removal does not yet support Toolkit, adding several small essential programs to post-setup, RuntimePack_Lite_x86_x64, .NET Core 3.1 Desktop Runtime, RegOrganzer, and so on..., adding commands to SetupComplete.cmd to delete some system Services, commands to delete Scheduler tasks, autounattend.xml, WinPE removal, saving the result, installation test. And if the assembly meets all the requirements - remounting the source, converting install.wim to install.esd, and only after that I save the final result to ISO, which is supposed to be used or stored. In principle, it is not so important for me at what stage to replace the installer, to do it first, or at the final stage, since with this configuration of tasks, I do not mount boot.wim and winre.wim (winre.wim is also removed earlier, while working with install.wim in the Toolkit). But still, I think it's more convenient to do it first. And what is best for you, you will be able to decide based on your tasks. The main thing is that you have caught the meaning.
Now, Rufus 3.16 offers a patch for "w11 boot.wim" file. This is the fastest way if you do not want to customize your ISO. Then go to USB Stick "\sources" and delete or rename the "appraiserres.dll" file. So before you do InPlace Upgrade, disable Internet connections. This last part is just to summarize what was spoken, just disregard.
I've used it a few times too, but about 2 years ago. Some very large difference from version 3 to version 5?
Brother Please Cross Check WSIM 22000.1 & Do click on WinPE Setup RunSyncronous Command there you are good to go. Please test my suggestion its running synchronous commands inside WinPE via using Path not commandline tag everything is different in different scenarios. & If commands are executed successfully that means its working like a charm For Specialize : Known as Pre OOBE doesnt matter to WinPE setup it matters just before system user creation.
MSMG, I think we could also add the inclusion of the classic context menu for Windows 11 in Apply Tweaks: Enable Classic Context Menu (win11): reg.exe add "HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32" /f /ve
I think I did not translate right, what you said before. Then I supposed something that was not needed. If this is already tested and working ... So all right! But "AllowUpgradesWithUnsupportedTPMOrCPU" only works on Live Windows (after installation - on the first run), so I put it in settings pass="oobeSystem". It is not necessary in the WinPE session (making a reference to the direct change at boot.wim), as it must be performed, in the case, on the first startup (making a reference to the direct change at Install.wim). It's just that I'm out of time for the tests, I'm also late to finalize the merge tests with all the changes that MSMG has made available and, make available to Custom Toolkit. I think Custom Toolkit will be released only with 11.9.
Are you sure about that? It needs at least TPM 1.2 and is meant for WU upgrades, afaik: https://forums.mydigitallife.net/th...grade-fix-kit-v2-0.83724/page-25#post-1694922
Yes, I think it can be applied after the first startup, through autounattend, in a clean installation with a untouched ISO. So it will be ready for when you need to do an InPlace Update. I may be mistaken in some aspect ... But in addition to renaming or deleting the file "appraiserres.dll", for this case of untouched image, in which the tweak has not been applied directly on the indexes of install.wim, it would be one more step done. However, in this case, we are putting the focus on the autounattend. Even Rename or Delete could be implemented, since the media was present, then at WinPE (AuditMode) would be the best choice. But it would be interesting only in a future installation media prepared for InPlace Update, not in this case of clean installation.
Yes, and even when it is useless, it will not make a difference if it is applied, and the "autounttend.xml" will already be ready, even then, as a generic file to be used with any image.