Thanks @Enthousiast. My bad was not using option 1 first. I used 2 and 3. I will read carefully and attempt again. Thanks for the help.
I'm back. Sp I followed exactly what you did and I got the same results. I'm pretty sure that that Windows install has something blocking upgrade with software. I've used your tools many times without this problem.
Something that worked for me is in the Start Menu search Troubleshoot program, launch the app compatibility troubleshooter, and direct it to the setup.exe from the ISO and tell it that it used to work in previous versions of Windows, and then select that it worked in Windows 8. It will surprisingly work. If that doesn't work for some odd or strange reason, then the next thing you do is grab yourself a copy of Windows 10 and take the sources folder from the ISO you want and copy it into the Windows 10 ISO. Actually, that's option 5 in his script, so I would recommend Option 5 or App Compatibility. Some others have said you can use Win 8 or Win 7 but the upgrade mitigations and registry migrations are so different in those versions of Windows that you could end up with a partially broken Windows install. Which, actually, is something you could fix with another In-place Upgrade once the first one is done, but I still would highly recommend not using a Win 8 or Win 7 image.
I tested on a VM going from W7 Ultimate to W10 IoT LTSC 2021 and the upgrade went smoothly. After that, I ran Code: DISM /online /cleanup-image /restorehealth /source:WIM:D:\sources\install.wim:2 /limitaccess using the unmodified image and this is the result of sfc /scannow: Code: 2025-02-26 18:45:34, Info CSI 0000107c Hashes for file member [l:17]'UpgradeMatrix.xml' do not match. Expected: {l:32 ml:33 b:70b3a84e753b927ace0812f811b0bcd7cd1fb0e7cf6d06e9d8856927617a76aa}. Actual: {l:32 b:c0e8ac71239bc976181ebbb9edc8eeb086ff3a2f931a494462e81a4569fb4e35}. 2025-02-26 18:45:34, Info CSI 0000107d [SR] Repairing file \??\C:\WINDOWS\Servicing\Editions\\UpgradeMatrix.xml from store 2025-02-26 18:45:34, Info CSI 0000107e [SR] Repair complete 2025-02-26 18:45:34, Info CSI 0000107f [SR] Committing transaction 2025-02-26 18:45:34, Info CSI 00001080 Creating NT transaction (seq 8) 2025-02-26 18:45:34, Info CSI 00001081 Created NT transaction (seq 8) result 0x00000000, handle @0xa778 2025-02-26 18:45:34, Info CSI 00001082@2025/2/26:21:45:34.842 Beginning NT transaction commit... 2025-02-26 18:45:34, Info CSI 00001083@2025/2/26:21:45:34.842 CSI perf trace: CSIPERF:TXCOMMIT;3956 2025-02-26 18:45:34, Info CSI 00001084 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired So the system should be fine, right?
It says /restore-health fixed the problem. Run again to be sure. If it will give hash mismatch error again change C:\WINDOWS\Servicing\Editions\UpgradeMatrix.xml file with the original one from install.wim. Everything will be fine
Yes, I did run sfc /scannow after rebooting and once more after updating the system. Both times it didn't detect any file mismatches or other issues. So using /restore-health from a clean iso is the solution here
Hi, Does this tool support 27808 ? I've tried "Win_11_Boot_And_Upgrade_FiX_KiT_v5.1f" method 1 + 4 first option selected but no luck. I'm getting "UNSUPORTED PROCESSOR" after reboot.
It's VMware VM, I've disabled TPM in VM settings, applied "Skip_TPM_Check_on_Dynamic_Update" into Windows, "Quick_11_iso_esd_wim_TPM_toggle" into iso, no luck. Mo matter if I use WU or ISO method, the update fails.
What CPU is on the host? And i assume you are upgrading, considering skip tpm check is for upgrades. Quick ISO with tpm toggle is not mine (and really never needed to use it) so can't tell if it should work. What should work in running option 1 and keeping the install offline during upgrade or use option 2a to fix the ISO and on the install you want to upgrade you run 2b or the script added to the new ISO and run setup.exe. ALL my tests are in win 10 VMware VM's, so non supported at all. EDIT: this is not the Boot and upgrade fix tool thread, this is the upgradematrix fix thread,
CPU: Intel Core i713700K Mainboard: ASUS ROG Z690-F Okay, it's a VMware bug. I can't do a Windows Insider 27788 -> 27808 upgrade even using the default VM template, default ISO, and simply allowing Windows update to install Windows Insider 27808.
This is not the boot & upgrade fix thread, the subject of this thread only enables unsupported upgrade paths.
Used it to upgrade from Windows 8.1 Embedded Industry Enterprise to Windows 10 LTSB 2016. Worked perfectly other than: