Windows won't boot? Try this fix order first

The fans spin. The lights come on. Windows does not. That is a different problem from a laptop that will not turn on at all. Power is getting there. The boot path is not. Start with the cheap checks. Unplug extras. Power-cycle properly. Then let Startup Repair try. Leave BOOTREC and CHKDSK until those have failed.

• Unplug every USB stick, external drive, and extra gadget. Firmware often tries to boot from the last stick you used. The screen just sits there.
• Hold the power button for ten seconds. Wait a few seconds. Turn it back on. That clears a stuck firmware state a normal restart will not touch.
• Let Startup Repair run. If it does not appear, interrupt the boot twice by holding power as soon as the Windows logo shows. The third start should drop into Automatic Repair.
• Check the BIOS boot order. A firmware update or a stray keypress can point the PC at the wrong drive.

If you hear grinding, smell burning, or the drive does not show in BIOS at all, skip the software steps. Do not keep writing to a dying disk. Computer Repair Scientist covers homes and offices across NSW. Sydney can start with computer repair across Sydney. Central Coast homes can use computer repair on the Central Coast.

No lights, no fan, no sound? That is a power problem, not a Windows one. Use laptop will not turn on first. If Windows does start, but everything crawls, use computer running slow instead.

What failed: four stages of a Windows boot

Windows does not just "come on." It moves through four stages. The screen you are staring at tells you which one broke. Guess the wrong stage and you spend an hour on commands that were never going to help.

PreBoot. This is firmware, before Windows starts. The motherboard runs POST, checks hardware, then hands off to the boot manager. If this fails, you will not see a Windows logo. You get a blank screen, beep codes, or a firmware error.

Boot manager. Windows Boot Manager reads the Boot Configuration Data to find the install. A damaged BCD, or a manager that cannot see the drive, shows "Bootmgr is missing" or "No boot device found."

OS loader. Winload.exe loads the kernel and the drivers Windows needs to start. Trouble here is often a Blue Screen naming a missing file, or a reboot loop right after the logo.

Kernel. Drivers and services come up. A bad driver or a damaged system file usually throws a stop code rather than a silent freeze.

Here is how the symptoms line up:

• No POST, no lights, no fans: power or motherboard. Not a Windows problem.
• POST finishes, then "No boot device": the boot manager cannot find the drive. Often BCD, boot order, or a loose cable.
• Windows logo, then a Blue Screen or a reboot: loader or kernel. Drivers or system files.
• Blinking cursor on a black screen: the manager found something, then stalled. Often a damaged boot sector.

One catch: a power cut mid-start can trip a boot flag and send you into WinRE even when the drive is fine. Rule that out before you write a new boot sector.

Pro Tip: If you never see a Windows logo, stop thinking about Startup Repair. You are still in firmware.

Fast checks, in order

A surprising number of "it will not boot" calls end before anyone opens a command prompt. Do these in order. Check after each one.

1. Unplug everything that is not essential. USB drives, printers, card readers, extra monitors. A device the BIOS tries to boot first is the most common stuck-startup we see.

2. Power-cycle properly. Hold the power button until it is fully off. Wait a few seconds. Turn it on. That clears firmware states a Restart click will not.

3. Reseat the drive if you are happy opening a desktop. A SATA or NVMe cable that has worked loose looks exactly like "No boot device." Laptops are usually a job for a bench.

4. Check BIOS or UEFI boot order. Del, F2, or F10 at startup on most PCs. Confirm the Windows drive is first. Reset to defaults if a firmware update scrambled the list.

5. Try Safe Mode if you can reach Advanced Startup. It loads a thin driver set. If Safe Mode works, a recent driver or app is the likely culprit.

If there is data on that machine you cannot lose, pause here. Do not run anything that writes to the boot sector until you have read the hardware section below.

Pro Tip: Nine times out of ten, when someone says the PC is stuck on boot, there is still a USB stick in the back from last week. Check the ports first.

How to get into Startup Repair

Windows Recovery Environment is the built-in toolkit. It has Startup Repair, System Restore, and a Command Prompt. It is meant to appear after two failed boots in a row.

If it does not launch on its own:

• Interrupt twice. Turn it on. Hold power as soon as the Windows logo appears. Repeat once. On the third try, Windows should drop into Automatic Repair.
• Shift + Restart if you can still reach the sign-in screen. Hold Shift while you click Restart. That opens Advanced Startup.
• Settings, System, Recovery if Windows is partly usable. Use Advanced startup, then Restart now.
• A recovery key on some laptops. F11, or a dedicated recovery button, can open the maker's partition.
• A Windows USB install stick if none of the above work. Repair your computer, then Troubleshoot.

Once you are in WinRE, go to Troubleshoot, Advanced options, Startup Repair. It looks for a damaged BCD, a broken master boot record, missing system files, and registry errors. Then it tries a fix.

Two warnings. If the drive uses BitLocker, some repairs will ask for the recovery key. Have it ready from your Microsoft account or the printed copy. And watch for a repair loop, where Startup Repair fails, reboots, and tries again forever. Break it by choosing Advanced options the moment the repair screen comes back.

Pro Tip: Startup Repair writing a report is useful. Letting it retry ten times is not. Take Advanced options on the second fail.

BOOTREC, CHKDSK, SFC, and DISM

When Startup Repair cannot finish the job, the WinRE Command Prompt is the same toolkit a technician reaches for. Open Troubleshoot, Advanced options, Command Prompt. Work through these in order. Do not fire them all at once.

1. Repair the boot code with BOOTREC.

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

/FixMbr writes a fresh master boot record without touching the partition table. /FixBoot writes a new boot sector. /RebuildBcd scans for Windows installs and rebuilds the BCD. That is the usual sequence when the boot manager cannot find Windows.

2. Inspect the BCD with BCDEdit if you need a closer look:

bcdedit /enum

That lists the current boot entries. You can see whether the OS line is missing, pointing at the wrong partition, or duplicated.

3. Check the file system with CHKDSK. In WinRE the Windows drive is often D: or E:, not C:. Confirm the letter first, then:

chkdsk C: /f /r

That scans for bad sectors and file system errors. It is a common cause of a blinking cursor or "No boot device" when the drive itself is still alive.

4. Verify system files with SFC from an offline prompt:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

5. DISM if SFC reports errors it cannot fix. Run this after you are back on the desktop. It needs internet or install media:

DISM /Online /Cleanup-Image /RestoreHealth

A few things to keep in mind:

• BOOTREC writes to the boot sector. Do not run it on a drive you already suspect is dying until the drive has been imaged.
• CHKDSK with /r can take hours on a large or tired disk. Do not stop it halfway.
• If a command says it cannot lock the drive, you probably have the wrong letter. Use diskpart then list volume and try again.

Pro Tip: The letter in WinRE is the trap. Repairing the recovery partition by mistake is how a five-minute fix becomes a weekend.

Match the message to the fix

The exact text on screen tells you more than a random command list.

Stop codes are worth reading. 0x0000007B, INACCESSIBLE_BOOT_DEVICE, usually means file system damage, a missing storage driver, or the controller mode in firmware (AHCI versus RAID). A missing-device message is usually hardware or firmware. A stop code after the logo, naming a file, is usually software.

When it is the drive, RAM, or firmware

Software fixes go nowhere if the drive is dying or a RAM stick is bad. Check that before you spend another hour at a prompt.

Open BIOS or UEFI (Del, F2, or F10) and see whether the drive is listed. If it is missing entirely, that is a connection or a hardware fault. Windows cannot fix a drive the firmware cannot see. While you are there, note the boot order. Reset to defaults if a firmware update left it messy.

• Reseat the drive on a desktop. Unplug and reconnect SATA or NVMe. Laptops usually need a technician.
• Run the built-in diagnostics. Many PCs offer a hardware test at startup, often F12, covering drive, memory, and battery.
• Test memory with Windows Memory Diagnostic or MemTest86. Leave it overnight if you can. Intermittent RAM faults hide in a short pass.
• Check the charger on a laptop. A failing adapter can cut power mid-boot and look exactly like a software crash.

If SMART says the drive is failing, or firmware cannot see it at all, the drive needs replacing, not repairing. Clone it, or try to, before anything else. Every extra write lowers the odds of getting the files off.

Pro Tip: A drive that only sometimes shows in BIOS is worse news than one that never shows. Intermittent detection usually means it is dying, not misconfigured.

When to stop and call

DIY covers a lot of boot failures. A few signs mean stop guessing, before you make recovery harder.

• SMART failures after a reseat or cable swap
• A drive that will not show in BIOS no matter what you try
• Clicking, grinding, a drop, or liquid
• BOOTREC, CHKDSK, and Startup Repair have all been tried and none of them held
• A RAID array, or BitLocker, and you do not have the recovery key
• You need the machine working today and you are out of time

Have this ready when you call:

• What you see: logo, beep, "No boot device", Blue Screen code
• Whether the drive still appears in BIOS
• Whether you already ran Startup Repair or BOOTREC
• Whether there is data you cannot lose

If the files matter more than a quick boot, say that first. A clone-then-repair path is slower. It is also how data survives. Newcastle and the Hunter can start from computer repair in Newcastle.

What we see on visits

Most boot visits end the same way: a USB stick, a boot order that drifted, or a BCD rebuild that Startup Repair could not finish on its own. The scary ones are quieter. A drive that "sometimes" appears. A stop code that comes back after every repair.

We start with the stage that failed. Then the cheap checks. Then an image if the disk looks tired. New hardware is rarer than people expect. When the drive is the fault, we say so before anyone spends money. Work is approved before it starts.

PC Scientist can help when it will not start

Some of these steps take five minutes. Others sit behind a BitLocker prompt or a drive that is already clicking. That is a fair reason to stop. Computer Repair Scientist can look with you, remotely first if that is enough, or onsite if the hardware itself is the problem.

Tell us what the screen shows, whether the drive appears in BIOS, and what you have already tried. We will say whether a remote look will do, or whether a visit makes more sense. Call 0493 563 381, or pick your area below.

Sources

These pages help when you want the maker's own steps:

• Windows Recovery Environment - Microsoft
• Windows RE troubleshooting features - Microsoft Learn
• No boot - Dell support

Use the PC maker's page for your exact model when you update firmware. A generic Windows repair USB is not the same as the manufacturer's recovery partition.