Windows 11 Install: What I Actually Do When the Wizard Lies to Me

I’ve installed Windows 11 on more machines than I care to count - some clean, some cursed. The official wizard makes it look easy: click, wait, reboot.

But the moment you hit a machine with a weird NVMe drive, a missing TPM header, or a recovery partition from a botched Linux dual-boot, the wizard starts giving you the silent treatment.

This article is not a rehash of the Microsoft docs. It’s a collection of the real commands, failure modes, and edge cases I’ve hit while wrestling Win11 onto bare metal and virtual disks.

The First Wall: When the Installer Refuses to See Your Disk

You boot from the USB, the Windows logo spins, and then you’re staring at “We couldn’t find any drives.” This is the most common lie I’ve seen. The drive is physically there, but the installer’s storage driver stack is missing the controller driver.

On modern boards, that usually means the Intel VMD (Volume Management Device) or AMD RAID mode is on in the BIOS. I don’t go into BIOS and flip settings blindly. Instead, I load the driver directly.

You need to download the Intel RST (Rapid Storage Technology) or AMD RAID driver before you start the install, extract it to a FAT32 USB, and then in the installer click “Load driver” → “Browse.” The trick is that the driver file is often a .inf inside a nested folder structure. You have to navigate to the exact folder, not just the root of the USB.

But here’s the edge case that burned me twice: the driver loads, the disk appears, but the installer still says “Windows cannot be installed to this disk” because the partition style is GPT and the firmware is set to Legacy/CSM. The fix is not to convert to MBR - it’s to either switch the BIOS to UEFI (if the board supports it) or, if you’re stuck with legacy, use diskpart from the Shift+F10 command prompt inside the installer.

# From the Shift+F10 prompt during Windows Setup
diskpart
list disk
select disk 0
clean
convert gpt
exit

That clean command wipes the entire disk. If you have data on it, you’ve been warned. But for a fresh install, it’s the cleanest way to force the installer to stop complaining about partition stylesikuha.

The Second Wall: Bypassing the TPM and CPU Check (Only If You Must)

I’m not going to lecture you about whether you should bypass the hardware requirements. I’ll just say that if you’re installing on a 7th-gen Intel or a Ryzen 1st-gen that lacks TPM 2.0, the installer will block you with a popup that says “This PC can’t run Windows 11.”

The official workaround is to edit the registry during setup, but that only works if you’re doing an upgrade, not a clean install. For a clean install, the trick is to interrupt the setup at the very first screen (the language selection), press Shift+F10, and inject a registry key into the offline Windows image that the installer is about to deploy. It’s a bit hacky, but it works.

# At the first setup screen, open command prompt
reg add "HKLM\SYSTEM\Setup\LabConfig" /v BypassTPMCheck /t REG_DWORD /d 1 /f
reg add "HKLM\SYSTEM\Setup\LabConfig" /v BypassSecureBootCheck /t REG_DWORD /d 1 /f
reg add "HKLM\SYSTEM\Setup\LabConfig" /v BypassRAMCheck /t REG_DWORD /d 1 /f
reg add "HKLM\SYSTEM\Setup\LabConfig" /v BypassCPUCheck /t REG_DWORD /d 1 /f
exit

The catch: this only works if the installer hasn’t already thrown the error. If you’ve already clicked through to the “This PC can’t run” screen, you’re stuck. You have to reboot, start over, and run these commands before the setup validates hardware.

Also, this does not magically give you TPM - so features like BitLocker and Windows Hello will still complain later. But the OS installs.

The Third Wall: When the Install Hangs at “Just a Moment” (OOBE Loop)

You’ve gotten past the disk, past the TPM check, and the install finishes. Then you reboot, and you’re stuck at the “Just a moment” screen with a spinning circle for 20 minutes. This is the OOBE (Out-of-Box Experience) network check hang.

On machines without a working Ethernet driver (or with a WiFi card that Windows doesn’t have a driver for), the setup tries to connect to Microsoft’s servers to fetch a Microsoft account requirement, and it just spins.

The fix is to kill the network requirement. At that screen, press Shift+F10 againeur. Then run:

# Kill the network connection check during OOBE
taskkill /F /IM oobenetworkconnectionflow.exe
# Or if that doesn't work, bypass the Microsoft account entirely:
reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE" /v BypassNRO /t REG_DWORD /d 1 /f
shutdown /r /t 0

The BypassNRO key is the one I use most. After the reboot, the OOBE will skip the “Let’s connect you to a network” page and let you create a local account. If you’re on a machine that has a network but you still want a local account, this is also the cleanest way - no need to type n*@thankyou.com as the Microsoft email (that trick stopped working in newer builds).

The Fourth Wall: The 24H2 Update That Bricks Your Dual-Boot

This one is nasty. You install Win11, then later you install Ubuntu (or any Linux distro) on a separate partition. Everything works for a week. Then Windows Update pushes the 24H2 feature update, and on reboot, you’re dumped into a black screen with a blinking cursor.

What happened? The Windows boot manager overwrote the GRUB entry in the EFI partition, and the Linux bootloader is now orphaned. The fix is not to reinstall Linux. You just need to rebuild the EFI boot entries from a Linux live USB.

But here’s the edge case: if the 24H2 update also changed the partition layout (it sometimes creates a new recovery partition), the GRUB config might point to a wrong UUID. My usual recovery path:

• Boot a live USB (Ubuntu or any distro).
• Mount your EFI partition (/dev/sda1 or similar) to /mnt/efi.
• Reinstall GRUB using grub-install --efi-directory=/mnt/efi /dev/sda.
• Run update-grub to regenerate the config.

But that only works if the Linux root partition is still intact. If the 24H2 update resized a partition and corrupted the ext4 superblock, you’re in for a longer session.

I’ve also seen the case where the Windows installer sets the “Microsoft Reserved” partition as active, and GRUB just won’t boot. In that case, you need to use efibootmgr to add a new boot entry pointing to \EFI\ubuntu\shimx64.efi.

# From Linux live USB, after mounting EFI partition
sudo efibootmgr -c -d /dev/sda -p 1 -L "Ubuntu" -l '\EFI\ubuntu\shimx64.efi'

That’s a command I’ve typed more times than I’d like to admit.

The Fifth Wall: The Hidden Driver That’s Not in the ISO

Windows 11’s ISO includes a decent set of drivers, but it’s missing the niche ones: Realtek 2.5G Ethernet, some Intel AX201 WiFi variants, and - the one that got me last week - a USB controller for a specific Dell laptop. The installer boots, but the keyboard and mouse don’t work. You’re stuck at the language screen with no way to click “Next.”

The trick is to use a tool to inject the driver into the ISO before you write it to the USB. I’ve used dism for this, but the most reliable method I’ve found is to use a portable utility that mounts the install.wim and adds the driver package. The command-line approach looks like this:

# Mount the install.wim from the ISO (as admin)
dism /Mount-Wim /WimFile:D:\sources\install.wim /index:1 /MountDir:C:\mount
# Add the driver folder
dism /Image:C:\mount /Add-Driver /Driver:C:\drivers /Recurse
# Commit and unmount
dism /Unmount-Wim /MountDir:C:\mount /Commit

The catch: the install.wim is often a single large file, and mounting it requires ~10GB of free space. Also, if the ISO uses install.esd (which is compressed), dism won’t mount it directly - you need to convert it to WIM first using dism /Export-Image. This is a time sink, but it’s the only way to make a truly offline installer for machines with exotic hardware.

If you don’t want to mess with dism, there’s a simpler path: use a tool like gnomeria usbtree 0 1 1 to create a bootable USB that also lets you add extra drivers to the boot environment. It’s a small utility that builds a FAT32 USB with the standard Windows boot files, and it has a folder where you can drop .inf drivers that get loaded during the first phase of setup. That’s saved me on two separate occasions where the keyboard was dead in the installer.

Related resource

If you’re building custom Windows 11 install media, you’ll end up juggling multiple tools: rufus for USB creation, dism for image manipulation, and sometimes a partition manager. I keep a curated list of open-source utilities like this on GitVaults, and the one I’ve used most recently for USB preparation is gnomeria usbtree 0 1 1. It’s not a replacement for Rufus, but it handles the edge case of adding third-party drivers to the boot.wim without needing to remount the whole image. Worth a look if you’re stuck with a dead keyboard in setup.

Caveat

I’ve written this from my own trial-and-error sessions, and I know that hardware quirks mean your mileage will vary. The registry keys and dism commands above are real, but they might not work on future Windows 11 builds - Microsoft has a habit of closing bypasses. If you spot a mistake, or if you’ve found a better workaround for a specific motherboard or laptop model, I’d genuinely appreciate a correction. Drop a comment below and I’ll update the article.