Windows Could Not Prepare the Computer to Boot into the Next Phase of Installation: Reset BIOS Settings to Bypass Error

When you see "Windows could not prepare the computer to boot into the next phase of installation," it’s usually a BIOS hiccup or a corrupted file stalling your fresh setup—even on high-end gaming rigs.

Secure Boot or TPM settings conflict with the installer. The fix isn’t always obvious, but the most reliable first step is resetting BIOS to defaults, which clears misconfigured firmware that Windows setup can’t override.

The root causes run the gamut: outdated BIOS, incompatible storage drivers, or even a failing RAM module masquerading as a software issue. I’ve debugged this error on machines where the problem was as simple as a loose SATA cable or as deep as a corrupted EFI partition.

The good news? Over 80% of cases resolve with BIOS adjustments or a clean disk check—no advanced hardware skills required. You’ll need just a few minutes and access to your system’s BIOS menu (usually pressed during boot via Del, F2, or F12).

Here’s what you’ll achieve: a working installation path that bypasses the error, whether you’re setting up a new PC or recovering an existing one. We’ll start with the quickest fix—resetting BIOS—before moving to deeper diagnostics like disk checks and boot repair tools.

The process is methodical, not magical, but it’s saved countless hours for users stuck in this loop. Let’s get your system booting again.

This approach works for modern UEFI systems (Windows 10/11) and older BIOS setups, though the steps vary slightly. If you’re dual-booting or using RAID, we’ll note those edge cases upfront. No special tools beyond what’s built into Windows—just patience and a methodical approach.

Confession: I’ve bricked more systems than I’d like to admit trying to fix this, but the fixes here are the ones that actually work the first time.

Root Causes of Boot Errors

When Windows fails to prepare your system for installation, it’s usually due to hardware or firmware conflicts that disrupt the boot process. Below, we break down the most common reasons—each with a clear, technical explanation—so you can pinpoint the issue and take action.

🔌 Corrupted or misconfigured BIOS/UEFI settings

The BIOS/UEFI firmware is the first software your PC runs when powered on. If its settings are corrupted or improperly configured—especially for Secure Boot, boot order, or legacy vs. UEFI mode—Windows Setup can’t proceed.

• Secure Boot Enabled: If Secure Boot is on but your boot media (USB/ISO) isn’t signed with a trusted key, Windows Setup will block the installation. This is a security feature that prevents unauthorized or tampered bootloaders from running.
• Incorrect Boot Mode: If your BIOS is set to Legacy (CSM) mode but you’re trying to install Windows in _UEFI_ mode (or vice versa), the installer won’t recognize the storage device, triggering the error.
• Outdated BIOS: Older BIOS versions may lack support for modern storage protocols (like NVMe drives) or Windows features, causing compatibility gaps.

Why it matters: The BIOS/UEFI acts as a bridge between hardware and the OS. If this bridge is broken, Windows Setup can’t "handshake" with your system to begin installation.

💾 Faulty or incompatible boot media

A corrupted, improperly formatted, or incompatible USB drive can derail Windows Setup before it starts. This isn’t just about the drive’s health—it’s also about how the boot files are written to it.

• Incorrect ISO or Media Creation Tool: Downloading a corrupted Windows ISO or using an outdated version of the Media Creation Tool can result in broken boot files.
• Insufficient or Slow USB Drive: Drives under 8GB or with high latency (e.g., cheap USB 2.0 sticks) may fail to load critical files fast enough, causing timeouts during boot.
• Improper Write Method: Writing the ISO to USB using tools like Rufus or BalenaEtcher requires specific settings (e.g., GPT partitioning, FAT32 formatting, or UEFI mode). Skipping these steps leaves the drive unreadable by Windows Setup.

Why it matters: The boot media is your PC’s first point of contact with Windows. If it’s damaged or misconfigured, the installer can’t even begin loading.

🖥️ Hardware conflicts or limitations

Modern PCs rely on complex hardware interactions during boot. If a component isn’t properly detected or supported, Windows Setup will fail with this error.

• Unsupported Storage Controller: Some motherboards use proprietary RAID or NVMe controllers that aren’t fully compatible with Windows Setup. For example, older Intel Rapid Storage Technology (RST) drivers may conflict with the installer.
• Missing or Outdated Drivers: If your system lacks drivers for essential hardware (e.g., SATA/AHCI controllers, USB 3.0 ports, or network adapters), Windows Setup can’t initialize storage or input devices.
• Overclocking or BIOS Locks: Aggressive overclocking settings (e.g., CPU/RAM speeds, voltage tweaks) or locked BIOS options (like disabled virtualization) can prevent the installer from detecting hardware correctly.
• Incompatible TPM or Secure Boot Requirements: Newer Windows versions (like Windows 11) mandate TPM 2.0 and Secure Boot. If your hardware lacks these, the installer will block progress.

Why it matters: Windows Setup is a low-level process that relies on hardware detection. If a critical component isn’t recognized, the installer throws up its hands and stops.

🔄 System file corruption or locked partitions

Even if your hardware is fine, existing system files or partition locks can interfere with the installation process.

• Previous Windows Installation Leftovers: If an old Windows installation failed mid-setup, leftover boot files or locked partitions (like the EFI System Partition) can conflict with the new installer.
• BitLocker or Encryption Issues: If your drive is encrypted with BitLocker or another tool, Windows Setup may not have the decryption keys to access it during the initial boot phase.
• Corrupted Boot Sector: A damaged MBR (Master Boot Record) or GPT partition table can prevent the installer from writing new boot files, causing it to stall.

Why it matters: The installer needs a "clean slate" to write its own boot files. If old or corrupted data is in the way, it can’t proceed.

🔋 Power or thermal issues during boot

Even a minor power fluctuation or overheating component can disrupt the boot process, especially during the sensitive early stages of Windows Setup.

• Unstable Power Supply: A weak or failing PSU (power supply unit) may cause voltage drops when the installer tries to access storage or RAM, leading to timeouts.
• Overheating CPU/RAM: If your CPU or RAM throttles due to high temperatures, the installer may fail to load critical components, triggering the error.
• Loose or Faulty RAM: Bad RAM sticks or improper seating can cause memory errors that halt the boot process before Windows Setup even starts.

Why it matters: The installer is a resource-intensive process. If your system isn’t stable enough to handle it, the boot sequence will fail.

Quick fixes for Windows boot errors

When your Windows installation stalls with the dreaded "could not prepare the computer to boot" error, panic isn’t the answer—action is! Below are practical, step-by-step solutions tailored to the most common causes, from BIOS tweaks to disk checks.

Follow the fixes that match your situation, and get your system back on track.

🔧 Fix 1: Reset BIOS/UEFI Settings to Default

Cause: Corrupted or misconfigured BIOS/UEFI settings often trigger boot failures, especially after hardware changes or Windows updates.

How to Fix It:

1. 🔥 Restart your PC and enter BIOS/UEFI setup.
   • For most PCs: Press F2, F12, DEL, or ESC repeatedly during startup (varies by manufacturer).
   • For laptops: Check your model’s manual (e.g., Fn + Esc on Dell, F2 on HP).
2. 🍳 Navigate to the "Load Default Settings" or "Reset to Default" option.
   • Look for terms like "Optimized Defaults" or "Factory Reset."
   • Use arrow keys to select, then press Enter.
3. 👨‍🍳 Save and exit (usually F10 or Ctrl + S).
   • Your PC will reboot. Try installing Windows again.

✨ Pro Tip:

• If you’re unsure which setting caused the issue, disable Secure Boot (common culprit) and set SATA mode to AHCI before saving.

💾 Fix 2: Check and Repair Disk Errors

Cause: A failing or corrupted hard drive/SSD can prevent Windows from writing boot files, leading to this error.

How to Fix It:

1. 🔪 Boot into a Windows Recovery Environment (WinRE):
   • Use a Windows USB installer or a recovery drive.
   • Select "Troubleshoot" > "Advanced options" > "Command Prompt."
2. 🥘 Run disk checks:
   • For HDDs/SSDs: Type chkdsk C: /f /r (replace C: with your drive letter if needed) and press Enter.
     • Wait for the scan to complete (may take 10+ minutes).
   • For SSD health: Use wmic diskdrive get status to check for errors.
3. 🔄 If errors are found, reboot and retry the Windows installation.

⚠️ Warning:

• If chkdsk reports "bad sectors" or the drive is failing, back up data immediately and consider replacing the disk.

🔄 Fix 3: Update or Reinstall Drivers

Cause: Outdated or incompatible drivers (especially for storage controllers or chipsets) can block the installation process.

How to Fix It:

1. 🔥 Use a third-party tool (like Driver Booster or Snappy Driver Installer) to update drivers before installing Windows.
   • Download drivers from the manufacturer’s website (e.g., Intel, AMD, NVIDIA) if offline.
2. 👨‍🍳 If installing Windows fails:
   • Boot into Safe Mode (hold Shift + F8 during startup) and update drivers manually.
   • Alternatively, use a driver USB created with tools like Rufus or Media Creation Tool.
3. ⏰ Reboot and retry the installation.

💡 Pro Tip:

• Disable fast startup in Windows (if dual-booting) to avoid driver conflicts:
  • Go to Control Panel > Power Options > Choose what the power buttons do > Change settings > Uncheck "Turn on fast startup."

🔌 Fix 4: Disable Fast Startup and Secure Boot

Cause: Fast Startup (hybrid shutdown) and Secure Boot can interfere with clean installations, especially on newer hardware.

How to Fix It:

1. 🍳 In BIOS/UEFI:
   • Disable Secure Boot (look for "Secure Boot Control" or "OS Type" > set to Other OS).
   • Enable Legacy Support (if installing in CSM/BIOS mode instead of UEFI).
2. 👨‍🍳 In Windows (if accessible):
   • Open Power Options > Choose what the power buttons do > Change settings > Uncheck "Turn on fast startup."
3. 🔄 Reboot and attempt installation again.

✨ Pro Tip:

• If dual-booting with Linux, disable Secure Boot to avoid compatibility issues.

🛠️ Fix 5: Test Hardware Connections

Cause: Loose cables, faulty RAM, or a failing power supply can mimic boot errors.

How to Fix It:

1. 🔥 Power off the PC and unplug it.
2. 🍳 Reseat RAM and storage drives:
   • Open the case and remove/reinsert RAM sticks (try one at a time if possible).
   • Ensure SATA cables are firmly connected to both the drive and motherboard.
3. 👨‍🍳 Test with minimal hardware:
   • Remove non-essential components (extra GPUs, USB devices, etc.).
   • Use a known-working power supply if possible.
4. ⏰ Boot and check for errors (e.g., beep codes, no display).

💡 Pro Tip:

• If using an SSD, try a different SATA port or USB-to-SATA adapter to rule out port issues.

🛡️ Prevention Tips: Avoid Future Boot Errors

• 📊 Backup critical data regularly (use Macrium Reflect or Windows Backup).
• 💪 Update BIOS/UEFI before major hardware changes (check your motherboard manufacturer’s site).
• 🥗 Use trusted installation media (create a USB with Rufus in GPT/UEFI mode for modern PCs).
• 🎯 Avoid abrupt shutdowns during Windows updates or installations.
• ✨ Monitor disk health with tools like CrystalDiskInfo to catch failures early.

Need more help? If the issue persists after these steps, your hardware (RAM, storage, or motherboard) may need professional diagnosis. 🚀

Frequently asked questions