Computer Hkey_local_machine System Setup Mosetup
Leysan Torri
Use the SetupDiag tool before you begin manually troubleshooting an upgrade error. SetupDiag automates log file analysis, detecting and reporting details on many different types of known upgrade issues.
Briefly, the upgrade process consists of four phases that are controlled by Windows Setup: Downlevel, SafeOS, First boot, and Second boot. The computer will reboot once between each phase. Note: Progress is tracked in the registry during the upgrade process using the following key: HKLM\System\Setup\mosetup\volatile\SetupProgress. This key is volatile and only present during the upgrade process; it contains a binary value in the range 0-100.
Downlevel phase: Because this phase runs on the source OS, upgrade errors aren't typically seen. If you do encounter an error, ensure the source OS is stable. Also ensure the Windows setup source and the destination drive are accessible.
Since the computer is booted into Windows PE during the SafeOS phase, a useful troubleshooting technique is to boot into Windows PE using installation media. You can use the media creation tool to create bootable media, or you can use tools such as the Windows ADK, and then boot your device from this media to test for hardware and firmware compatibility issues.
If you attempt to use the media creation tool with a USB drive and this fails with error 0x80004005 - 0xa001a, this is because the USB drive is using GPT partition style. The tool requires that you use MBR partition style. You can use the DISKPART command to convert the USB drive from GPT to MBR. For more information, see Change a GUID Partition Table Disk into a Master Boot Record Disk.
Don't proceed with the Windows 10 installation after booting from this media. This method can only be used to perform a clean install, which won't migrate any of your apps and settings, and you'll be required reenter your Windows 10 license information.
If the computer doesn't successfully boot into Windows PE using the media that you created, this is likely due to a hardware or firmware issue. Check with your hardware manufacturer and apply any recommended BIOS and firmware updates. If you're still unable to boot to installation media after applying updates, disconnect or replace legacy hardware.
If the computer successfully boots into Windows PE, but you are not able to browse the system drive on the computer, it's possible that non-Microsoft disk encryption software is blocking your ability to perform a Windows 10 upgrade. Update or temporarily remove the disk encryption.
First boot phase: Boot failures in this phase are relatively rare, and almost exclusively caused by device drivers. Disconnect all peripheral devices except for the mouse, keyboard, and display. Obtain and install updated device drivers, then retry the upgrade.
Second boot phase: In this phase, the system is running under the target OS with new drivers. Boot failures are most commonly due to anti-virus software or filter drivers. Disconnect all peripheral devices except for the mouse, keyboard, and display. Obtain and install updated device drivers, temporarily uninstall anti-virus software, then retry the upgrade.
If the general troubleshooting techniques described above or the quick fixes detailed below don't resolve your issue, you can attempt to analyze log files and interpret upgrade error codes. You can also Submit Windows 10 upgrade errors using Feedback Hub so that Microsoft can diagnose your issue.
The Windows Setup application is used to upgrade a computer to Windows 10, or to perform a clean installation. Windows Setup starts and restarts the computer, gathers information, copies files, and creates or adjusts configuration settings.
When performing an operating system upgrade, Windows Setup uses phases described below. A reboot occurs between each of the phases. After the first reboot, the user interface will remain the same until the upgrade is completed. Percent progress is displayed and will advance as you move through each phase, reaching 100% at the end of the second boot phase.
Here's how you can install Windows 11 without TPM 2.0. If you want to install it on your computer using either official or unofficial ISOs, you may be out of luck if your computer does not support Trusted Platform Module 2.0 or TPM 2.0. An attempt to install Windows 11 on a PC lacking TPM 2.0 will end up with the following error: "This PC can't run Windows 11. The PC must support TPM 2.0." Fortunately, it is easy to bypass the stumbling block. This article will show you how to install Windows 11 on a computer that does not support TPM 2.0.
To upgrade an existing Windows setup to Windows 11, you can use either Windows Upgrade Assistant or Windows Media Creation Tool, which both Microsoft made available on October 5, 2021. You can also use the official ISO image by mounting it and running the setup.exe app from the ISO file. However, if you hardware is not supported, the setup will stop.
In order to allow users to install Windows 11 on such devices under their own responsibility, Microsoft allows adding a special Registry key that makes Windows 11 ignore the CPU and TPM 2.0 requirement. By default, at least TPM 1.2 is required.
If you don't have the UltraISO app, you can use Microsoft's official tool oscdimg, which is part of Windows ADK. Here's how you can use it to put the install.esd file with Windows 11 over the existing Windows 10 file in the ISO image.
As you may already know, modern Windows version load a minimal OS version, earlier known as "MiniOS", now know as Windows Preinstallation Environment. It loads the required set of drivers and starts the main Windows setup program.
1. Just make a USB drive using Windows 10 ISO (English)
2. Mount the Windows 11 ISO with Windows Explorer, and go to sources folder and copy install.wim.
3. Paste the file in the USB drive, inside sources folder.
Hello!
Thank you for sharing these methods, very useful!
Just wonder, installing WIN 11 this way, will the OS receive the updates afterwards?
Or the only way is to download and install the build each time?
Thank you!
did not follow your rather complicated method, but
I downloaded W11 ISO and installed it in Virtual Box.
working fine
this on an old notebook from 2012 with intel core 15-460M processor, it is running just on 2GB RAM because of low RAM on the notebook and though it runs slow, W11 does run.
I recently did a trial Win 10 to 11 upgrade on an ancient unsupported laptop, using the Win10 21H1 installer, and ran into the reported issue where Windows Defender UI is missing and the Security Center screen is blank. Even after manually installing the Security-Health service and Defender using PowerShell, they would refuse to run. The only solution that worked was an in-place reinstall but that was a major hassle as I will outline below.
After experimenting extensively with this for several days, I reached the conclusion that the oft-promoted Win10 installer method is at fault and really should not be used for Win11 upgrades, if ever at all:
Ultimately I unpacked and copied a virgin Win11 ISO to a temp directory on my C: drive, renamed appreiserres.dll, and proceeded with a smooth in-place Win11 reinstall after which everything worked again, as it is supposed to. YMMV.
Tip: Winaero Twеaker is essential software for every Windows 10, Windows 8 and Windows 7 user. It allows you to customize the appearance and behavior of the operating system in a flexible way.
Try Winaero Twеaker now!
My pc is very old, its a gygabyte GA-Z270-HD3P. I want to use it again since i7 is quite decent even for 2022. The issue is i stopped using it because of some unkown issue no one ever helped me with, now when i restarted it, it keeps giving me this error: exception scope invalid or Kmode exception not handled after saying "preapring for automatic repair".
I have not found ANY issue stating that windows 10 cant be installed on my CPU, and even though there are many vids and threads helping install on unsuported CPUs, i cant even do that since i cant get out of bios.....Its in a constant loop of restarting itself, entering repair, and giving the error.
@VonLuciffYou could use Rufus 3.x ( LINK ) to bypass the Memory / CPU / TPM check, as well as the forced requirement to use an online account, etc, other various things. All that does is modify the registry hive ( you could apply a fix like this yourself even, if you didn't want to use Rufus or another 3rd-party program. )
You could do the same thing without Rufus, by just using an answer file with Sysprep ( requires the ADK,) or loading the registry hive on a mounted ISO image (using DISM + REG / REGINI, or even a PowerShell Cmdlet.) Rufus is way easier, but both ways are legitimate ( make sure to install the latest drivers and cumulative updates, including the ones for the .NET Framework. )
NOTE: One of my backup PCs is far far older ( 5+ years old,) runs Windows 11, has the latest drivers, etc (it meets the requirements obviously, TPM, 64-bit processor, etc, it's just listed as unsupported by Microsoft, even though I can still get new drivers for it.) Most desktop computer motherboards from maybe 2005-2006 ( 2009 for some OEMs,) would support Windows 11. Of course laptops are different, typically a laptop from 2009-2010 has a TPM, anything older than 2008 is probably not going to have a TPM or even basic AES acceleration. With other operating systems, not just Windows 11, it would be just as useless if you wanted to use SHA3, TLS 1.3, or even AES-256 support.
Most of the time, if you don't have supported hardware, it doesn't contain a Trusted Platform Module (TPM) 2.0.
As you can check by opening the device manager. This Trusted Platform Module (TPM) 2.0 should have been in a "Security devices" section which is not present here.
If you install the "PC Health Check" application and click the "Check Now" button, the error "This PC doesn't currently meet Windows 11 system requirements" will appear.
Most of the time, you will see in particular the "TPM: TPM not detected" line.