I'm building a secondary PC out of second-hand parts mainly for work. After assembling it, everything posts fine, but I'm stuck when trying to install Windows. I can't seem to get the installation wizard to show up when booting from the installation device. This is the first time I've encountered this issue, and I haven't found much help online. The PC was running Windows 10 before, so I'm considering cloning the original HDD to the new SSD for an upgrade if that doesn't work. Here are the main components I'm using:
- CPU: AMD Ryzen 7 1700
- Motherboard: Asus PRIME X370-A (BIOS version 3803)
- SSD: Kingston NV2 2TB
- RAM: DDR4 G.Skill Fortis, 2 x 8GB
- GPU: Gigabyte Radeon RX VEGA 56
I'd appreciate any ideas on what could be causing the Media Creation Tool issues!
3 Answers
Make sure to check if Secure Boot is enabled. And do you have a TPM module? It’s required for Windows 11—some older rigs need an extra module for the upgrade. You can bypass some CPU restrictions by using Rufus and enabling options to ignore these requirements.
Try switching the BIOS setting from UEFI to legacy or the other way around. Sometimes Windows 11 is set to boot in UEFI mode by default, and if your BIOS is still in legacy mode, you won’t be able to boot from the device. Also, your BIOS is a bit outdated (from 2018), so it might be a good idea to update it before attempting a fresh install—there have been many updates for Secure Boot and TPM since then.
Which version of Windows are you trying to install? Did you use the Media Creation Tool to make the boot device directly? You might want to consider downloading the ISO you need and using Rufus to create the bootable USB. Also, ensure you’ve arranged the boot preferences in your BIOS, and that the bootable device is formatted as FAT32 and set for UEFI. Oh, and make sure you’re using a proper USB port on the motherboard!
I used the Media Creation Tool for Windows 11, but I haven't tried Rufus yet. I did set the boot preferences and the USB is formatted in FAT32, plugged directly into the motherboard.
It turned out to be the TPM module, thanks a lot! 😀