UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
A desktop PC tower on a dark workbench displaying a black screen with a blinking white cursor underscore during a failed Windows boot sequence
Fix It Yourself · Troubleshooting

flashing underscore boot

Updated 12 July 202613 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

Most people who see a flashing underscore boot screen assume the worst and reach for a Windows reinstall disc. That's almost always the wrong move. In the vast majority of cases this problem is a boot order issue, a corrupted Boot Configuration Data file, or a USB drive that got left in the machine overnight. None of those require a reinstall. What they require is about 15 to 30 minutes and the right sequence of steps.

TL;DR

A flashing underscore boot means Windows Boot Manager failed to start. Remove USB devices first, then check your BIOS boot order. If that doesn't fix it, boot from a Windows recovery USB and run Startup Repair or the bootrec command set. Most cases are sorted without reinstalling anything.

⏳️ 13 min read ✅ 85% success rate 📅 Updated June 2026

Key Takeaways

  • A flashing underscore boot happens when firmware hands off to the drive but Windows Boot Manager can't start.
  • Removing USB devices and checking BIOS boot order fixes the problem in a good chunk of cases, no tools needed.
  • Corrupted BCD or MBR files are the next most common cause and are fixable with bootrec commands from recovery media.
  • If the drive doesn't appear in BIOS at all, the problem is hardware, not software. Check cables before anything else.
  • A dedicated partition manager tool can help rebuild and verify partition structures when bootrec alone isn't enough.

At a Glance

  • Difficulty: Easy to Medium
  • Time Required: 15 to 30 mins
  • Success Rate: 85% of users

What Actually Causes a Flashing Underscore Boot?

Here's the thing: the flashing underscore itself isn't an error code. It's the cursor sitting at the start of a command line that never gets a command. What it tells you is that the firmware (your BIOS or UEFI) found a bootable device, started to hand over control, and then nothing happened. Windows Boot Manager either wasn't where the firmware expected it to be, or it was there but too damaged to run.

The single most common cause I see in day-to-day support calls is a USB drive left plugged in. The BIOS sees it as a bootable device, tries to load from it, finds no valid operating system, and just... stops. The cursor blinks. Nothing else happens. Pull the USB drive out, restart, and the machine boots fine. Takes about 20 seconds to fix. Embarrassing, but it happens to everyone at some point.

The second most common cause is a corrupted Boot Configuration Data store, usually shortened to BCD. The BCD is a small database that tells Windows Boot Manager where to find the operating system files. If Windows updated and the machine lost power mid-process, or if there was a bad sector hit on the system partition, the BCD can end up broken or empty. The firmware finds the drive, the drive is physically fine, but the boot instructions are gone. That's when you need recovery tools.

A UEFI versus Legacy (CSM) mismatch is less common but genuinely annoying when it does show up. If someone has gone into BIOS and toggled the boot mode, or if a BIOS reset has changed the default, the firmware might be looking for a GPT-partitioned drive in Legacy mode or an MBR drive in UEFI mode. Neither will boot. The flashing underscore boot is the result in both cases.

Finally, hardware. A loose SATA cable, a dying HDD, or an SSD with failing flash cells can all produce this symptom. The drive is detected just enough for the firmware to try booting from it, but not reliably enough to actually load the boot manager. If you've tried every software fix and the problem keeps coming back, the drive itself is the suspect. We'll cover how to check that too.

According to Microsoft's own Windows boot troubleshooting documentation, the boot process has several distinct phases, and a flashing underscore specifically points to a failure at the boot manager or OS loader phase, after the firmware POST has already completed successfully. That distinction matters because it narrows down where to look.

Flashing Underscore Boot: Quick Fix (5 to 10 Minutes)

Start here before touching anything else. These three steps cost almost no time and between them they fix a solid proportion of flashing underscore boot cases without any recovery media or technical knowledge.

1

Remove USB Devices and Check Boot Order Easy

  1. Unplug everything USB
    Remove every USB device from the machine except your keyboard, mouse, and monitor cable. That means USB drives, external hard drives, phone cables, USB hubs, everything. Then restart and see if Windows loads.
  2. Enter BIOS or UEFI
    If the machine still shows a flashing underscore boot after removing USB devices, restart again and immediately tap Delete, F2, F10, or F12 repeatedly as the manufacturer logo appears. The exact key varies by brand. Look for a small on-screen prompt during the first second of startup.
  3. Check the boot order
    Once inside BIOS, find the Boot menu or Boot Priority section. Your internal Windows drive or an entry labelled Windows Boot Manager should be at the top of the list. If a USB device, optical drive, or network boot option is listed first, move your internal drive to position one.
  4. Save and exit
    Save changes (usually F10) and let the machine restart. Watch whether Windows loads normally now.
  5. Power reset if still stuck
    Shut the PC down fully, unplug the power cable from the wall, hold the power button for 10 to 15 seconds to drain residual charge, reconnect power, and restart. This clears transient states in the firmware and storage controller that can cause a flashing underscore boot even when the boot order looks correct.
If Windows loads after any of these steps, you're done. Check that no USB drives are left plugged in by habit, and make sure the boot order stays correct after any future BIOS resets.
A BIOS reset (whether deliberate or caused by a dead CMOS battery) will often revert the boot order to factory defaults, which may not include your Windows drive at the top. If this keeps happening, your CMOS battery may need replacing. It's a cheap fix on most desktops.

If none of the quick steps above have sorted it, the problem is almost certainly in the boot files themselves. That means you'll need Windows recovery media for the next stage. If you don't have a recovery USB already, you can create one using the Microsoft Media Creation Tool on any other Windows PC. A standard 8GB USB drive is enough.

More Flashing Underscore Boot Solutions (15 to 30 Minutes)

These intermediate steps cover the most common software-level cause of a flashing underscore boot: damaged or missing Windows boot files. Startup Repair handles this automatically in most cases. System Restore is useful if the problem started after a recent update or software install.

2

Run Startup Repair from Recovery Media Easy

  1. Boot from your Windows USB
    Insert your Windows installation or recovery USB, restart, and enter BIOS to set the USB drive as the first boot device temporarily. Save and exit. The Windows setup screen should appear.
  2. Get to Startup Repair
    On the Windows setup screen, click Next, then click Repair your computer (bottom-left, not Install now). Go to Troubleshoot, then Advanced options, then Startup Repair.
  3. Let it run
    Startup Repair will scan your Windows installation and attempt to fix corrupted or missing boot files automatically. This can take 5 to 15 minutes. Don't interrupt it. If it finds and fixes a problem, it will prompt you to restart.
  4. Verify the fix
    Remove the USB drive and restart normally. If Windows loads, the boot files were the issue and they're now repaired.
Startup Repair works well for straightforward BCD corruption and missing bootloader files. It's the right first tool because it requires no command knowledge and covers the most common scenarios.
3

Try System Restore Easy

  1. Access System Restore from recovery media
    From the same Advanced options menu (Troubleshoot, Advanced options), choose System Restore instead of Startup Repair.
  2. Pick a restore point
    Select a restore point dated before the flashing underscore boot problem started. If the machine was working fine until a recent Windows update, pick a point from before that update.
  3. Confirm and wait
    System Restore will revert Windows system files and registry settings to the earlier state. It won't touch your personal files. This takes 10 to 20 minutes and the machine will restart automatically.
System Restore only works if restore points exist. Windows creates them automatically before major updates, but this feature can be disabled. If no restore points are listed, skip this step.

Worth checking at this stage: go back into BIOS and confirm the internal drive is actually visible in the storage device list. If it's not showing up at all, Startup Repair won't be able to find it either. A drive that disappears from BIOS is a hardware problem, not a software one. See the hard drive not detected in BIOS guide for that specific scenario.

Advanced Flashing Underscore Boot Fixes (30+ Minutes)

When Startup Repair comes back with 'Startup Repair couldn't repair your PC', or when it runs and the problem comes straight back on the next boot, you need to go deeper. The bootrec command set gives you direct control over the Master Boot Record, the boot sector, and the BCD store. This is what I use when the automated tools have already given up.

Before running any repair commands, check whether your important files are accessible. From the recovery Command Prompt, you can browse the drive with standard commands like dir c:\. If the drive is readable, copy critical files to a USB drive before proceeding. Repair commands don't delete data, but a failing drive might.
4

Repair Boot Records with bootrec Medium

  1. Open recovery Command Prompt
    Boot from your Windows USB, click Repair your computer, go to Troubleshoot, Advanced options, Command Prompt. You'll get a black command window with administrator access.
  2. Run chkdsk first
    Type the following and press Enter: chkdsk c: /f /r
    This scans the C: drive for file system errors and bad sectors, and attempts to repair them. The /r flag means it also recovers readable data from bad sectors. This can take 10 to 60 minutes depending on drive size. Let it finish completely.
  3. Fix the Master Boot Record
    Type: bootrec /fixmbr
    This rewrites the MBR on the system disk without touching the partition table. Press Enter and wait for the 'The operation completed successfully' message.
  4. Fix the boot sector
    Type: bootrec /fixboot
    This writes a new boot sector to the system partition. If you get an 'Access is denied' error here, it usually means the system partition is GPT-formatted. In that case, run bootsect /nt60 sys /mbr as an alternative.
  5. Scan for Windows installations
    Type: bootrec /scanos
    This scans all disks for Windows installations. If it finds one that isn't in the BCD, note the path it reports.
  6. Rebuild the BCD
    Type: bootrec /rebuildbcd
    This scans for Windows installations and prompts you to add them to the BCD. Type Y and press Enter when prompted. Once complete, type exit, remove the USB drive, and restart.
If all four bootrec commands complete without errors, the flashing underscore boot should be gone. The BCD is rebuilt and the boot sector is fresh. Windows should load normally on the next restart.

One thing worth knowing: if bootrec /rebuildbcd reports 'Total identified Windows installations: 0', the tool can't find your Windows partition. This can happen with certain GPT disk configurations or if the Windows partition has lost its 'boot' flag. This is exactly the scenario where a dedicated partition manager tool becomes genuinely useful. A good partition manager can inspect the partition table, verify that the EFI System Partition (ESP) is correctly flagged, and repair partition attributes that bootrec can't touch. The built-in Windows tools don't give you that level of visibility.

For context on what healthy drive metrics should look like before and after these repairs, Tom's Hardware's drive health monitoring guide is a solid reference. It covers both HDD and SSD health indicators and explains what warning signs to watch for.

If the bootrec commands fix the flashing underscore boot but the problem returns after the next Windows update or shutdown, the drive is likely developing bad sectors or the partition structure has an underlying issue. At that point, back up your data and start thinking about a replacement drive. See the signs your SSD is failing guide for a full checklist of symptoms to watch for.

5

Check Physical Drive Connections Easy

  1. Power down completely
    Shut down and unplug from the wall. For a laptop, remove the battery if accessible.
  2. Reseat the SATA cables
    Open the case (desktop) or access panel (laptop). Locate the SATA data cable and SATA power cable connected to the drive. Unplug both and firmly reconnect them. Try a different SATA port on the motherboard if one is available.
  3. Check for drive detection in BIOS
    Restart and enter BIOS. Go to the storage or drive information section and confirm the drive appears with its correct model name and capacity. A drive that shows up intermittently or with a wrong capacity is failing.
For M.2 NVMe SSDs, there's no SATA cable to check, but the M.2 card itself can work loose over time. Reseat it by removing the retaining screw, pulling the card out, and firmly reinserting it at the correct angle before replacing the screw.

If you're dealing with a laptop where the drive is soldered or otherwise inaccessible, or if you've tried everything above and still have a flashing underscore boot, that's when remote support becomes the most efficient option. A technician can walk through the recovery environment with you in real time and catch things that are easy to miss when you're doing it alone.

Preventing a Flashing Underscore Boot

Most of the cases I see are preventable. The biggest single cause is power loss during a Windows update, which corrupts the BCD. A UPS (uninterruptible power supply) on a desktop, or simply keeping a laptop plugged in during updates, eliminates that risk entirely.

Keep your boot order correct. After any BIOS reset, CMOS battery swap, or new hardware install, go back into BIOS and confirm Windows Boot Manager or your system drive is still first in the boot sequence. It takes 30 seconds and saves a lot of grief later.

Here are the most important prevention steps, in priority order:

  1. Create a Windows recovery USB now, before you need it. The Microsoft Media Creation Tool is free and takes about 10 minutes. Having recovery media ready means a flashing underscore boot is a minor inconvenience rather than a crisis.
  2. Monitor drive health regularly. Tools like CrystalDiskInfo (free) read S.M.A.R.T. data from your drive and flag early warning signs like reallocated sectors or pending uncorrectable errors. Catching a failing drive early means you can back up and replace it before it causes a boot failure.
  3. Don't leave USB drives plugged in during shutdown. This is the simplest one and the most commonly ignored.
  4. Avoid toggling UEFI versus Legacy boot mode unless you're doing a full reinstall. Switching modes on an existing Windows installation will almost always produce a flashing underscore boot or worse.
  5. Keep regular backups. Whether it's Windows Backup, a cloud service, or a manual copy to an external drive, having a backup means boot repair can be attempted without any data-loss anxiety. See the Windows backup setup guide for a quick walkthrough.

Flashing Underscore Boot: Summary

A flashing underscore boot looks alarming but it's one of the more fixable Windows problems out there. The cursor is just telling you that the firmware ran out of instructions. Give it the right boot device, or repair the boot files so Windows Boot Manager can do its job, and the machine comes back.

Work through the steps in order: remove USB devices, check BIOS boot order, run Startup Repair, then bootrec commands if needed. The vast majority of flashing underscore boot cases are sorted by the time you get to Startup Repair. The bootrec commands handle almost everything else. If the drive isn't showing up in BIOS at all, shift focus to the physical connection before spending time on software repairs.

And if the problem keeps coming back after repairs, take that seriously. A recurring flashing underscore boot on a healthy drive configuration is a drive health warning, not a software quirk. Back up, test the drive, and replace it if the S.M.A.R.T. data looks bad. Drives are cheap. Data isn't.

Frequently Asked Questions

It means the firmware (BIOS or UEFI) has handed off to the storage device, but the Windows Boot Manager or OS loader has not started. The cursor is just sitting there waiting. The most common causes are a wrong boot device, corrupted boot files, or a drive that is not being read properly.

Yes, always. Unplug every USB device except keyboard, mouse, and monitor, then restart. A USB drive left in the machine is one of the most common reasons for a flashing underscore boot, because the firmware tries to boot from it and finds nothing useful.

Restart and immediately tap Delete, F2, F10, F12, or Esc repeatedly as soon as the manufacturer logo appears. The exact key depends on your motherboard or laptop brand. Look for a message like 'Press F2 to enter Setup' during the first second of startup. If you miss it, restart and try again.

Absolutely. A loose SATA data cable or a loose power connector on the drive can prevent the disk from being read during boot, which drops you straight to the blinking cursor. Reseat both cables at the drive end and at the motherboard end. Also try a different SATA port on the motherboard.

If the drive is invisible in BIOS, the problem is hardware rather than software. Check all physical connections first. If it still does not appear, the drive may be failing or the SATA port may be faulty. Try a different SATA port and a different cable before concluding the drive has died.

The bootrec commands themselves are fast, usually under a minute each. The chkdsk /f /r command is the slow one. On a large HDD it can run for 30 to 60 minutes or longer. Do not interrupt it. Let it finish completely before you restart.

Yes, in most cases. If Windows cannot boot at all, you need external recovery media to access Startup Repair or the Command Prompt. You can create a Windows 11 or Windows 10 bootable USB on another PC using the Microsoft Media Creation Tool from the Microsoft support site.