Few things are more frustrating than pressing the power button on your PC, watching the lights come on, hearing the fans spin up — and then sitting in front of a black screen, a blinking cursor, or an error message where Windows should be. The machine is clearly alive. Something is just stopping it from getting to the desktop.
The good news is that “turns on but won’t load Windows” covers a range of problems that are, in most cases, diagnosable and fixable. The bad news is that some of them point toward hardware failure that requires professional attention before more damage is done.
This guide walks through every common cause of a PC that powers on but won’t load Windows — from the most easily resolved to the most serious — what symptoms distinguish each cause, what you can try yourself, and when it’s time to hand it to a professional.
What “Won’t Load Windows” Actually Means?
Before diving into causes and fixes, it’s worth being precise about what you’re seeing — because different symptoms point to very different causes.
Black screen with blinking cursor — The system is attempting to boot but can’t find a bootable device or the boot sector is corrupted.
“No bootable device” or “Boot device not found” error — The BIOS/UEFI can’t locate a drive containing Windows. This can mean a disconnected drive, a failed drive, or corrupted boot files.
Windows logo appears, then restarts — The system gets far enough to start loading Windows but encounters a fatal error and restarts. Often indicates driver corruption, Windows file corruption, or hardware instability.
Blue Screen of Death (BSOD) before or during loading — A specific Windows or hardware error is preventing boot. The error code on the BSOD is a meaningful diagnostic clue.
Stuck on the Windows loading screen — Windows begins loading but freezes. Often indicates a failing hard drive, corrupted system files, or a driver conflict.
“Preparing Automatic Repair” loop — Windows detects a problem and tries to repair itself, but can’t complete the repair. Often indicates storage problems or corrupted Windows files.
Black screen after the Windows logo — Windows partially loads but fails to reach the desktop. Often graphics driver issues, a corrupted user profile, or a startup programme conflict.
The specific symptom you’re experiencing gives significant diagnostic information. Keep it in mind as you work through the causes below.
Cause 1: Corrupted Windows System Files
This is one of the most common causes of a PC that turns on but won’t reach the Windows desktop, and it’s worth checking early because it’s often resolvable without replacing any hardware.
Windows system files can become corrupted through an interrupted Windows update (power loss mid-update is a classic cause), a sudden shutdown during disk activity, malware infection, or gradual storage errors affecting critical system locations. The result is that Windows starts loading, encounters a corrupted or missing file it needs, and either crashes, loops to Automatic Repair, or freezes on the loading screen.
What you can try: If you can access Windows Recovery Environment (WinRE) — which appears automatically if Windows fails to load twice in a row — the Startup Repair option attempts to fix common boot issues automatically. From the command prompt in WinRE, the sfc /scannow and DISM /RestoreHealth commands can repair corrupted system files if the underlying storage is functional.
If Windows Update was the culprit, the recovery environment also includes an option to uninstall recent updates — this can resolve boot failures caused by problematic updates. Our blog on how to fix Windows update issues covers this in more detail, and our PC crashing after latest Windows update blog is directly relevant if your boot failure appeared after a recent update.
When to get help: If Startup Repair fails and command line repairs don’t resolve the issue, a professional diagnosis is needed to determine whether the corruption is software-only or whether failing storage hardware is the underlying cause.
Cause 2: Failing or Failed Storage Drive
A failing hard drive or SSD is one of the most serious causes of Windows not loading — and one of the most important to diagnose early, because continued use of a failing drive risks permanent data loss.
The connection between storage failure and boot failure is straightforward: Windows lives on your storage drive. If that drive is failing, struggling to read data, or has developed bad sectors in the areas where Windows is stored, the system can’t load what it can’t read.
Hard drives give more warning signs before failure — clicking or grinding sounds, very slow read performance, gradual appearance of errors — while SSDs can fail more suddenly and silently. Either way, a storage failure that’s preventing Windows from loading is an urgent situation from a data preservation perspective.
What to look for: If you hear clicking, grinding, or unusual repetitive sounds from inside the PC while it’s attempting to boot, suspect the hard drive immediately and stop attempting to boot. Repeated clicking is often the sound of a drive’s read/write heads failing — continued attempts to boot under these conditions can cause further physical damage. Our blog on 5 signs of a failing hard drive covers the warning signs in detail, and what to do when your hard drive fails explains the immediate steps to take.
For SSDs, failure is typically silent — the drive simply stops responding or is no longer detected. If your system is showing “no bootable device” errors and the drive was previously working, SSD failure is a strong possibility, particularly on drives more than four to five years old.
What you can try: If you can access BIOS/UEFI setup (usually by pressing F2, F10, F12, or Delete during startup), check whether the system is detecting your drive. A drive that doesn’t appear in BIOS has either failed, disconnected, or failed to initialise.
When to get help: Any situation involving a potentially failing drive where data matters requires professional attention before further boot attempts. Our data recovery Melbourne and emergency data recovery Melbourne services handle storage failure situations where data preservation is the priority. Our SSD data recovery and HDD data recovery services address the specific failure modes of each storage type. Our computer not starting repair service includes a storage assessment as part of the diagnostic process.
Cause 3: Corrupted Boot Sector or Bootloader
Even if Windows system files are completely intact and your drive is healthy, a corrupted boot sector or damaged bootloader will prevent Windows from loading, because the bootloader is what tells the system where to find and how to start Windows in the first place.
Boot sector corruption can be caused by a malware infection (some malware specifically targets the boot sector), an abrupt power loss during a Windows update or disk operation, or incorrect modification of disk partitions. The symptom is typically a black screen with “no bootable device,” “invalid partition table,” or “bootmgr is missing” error messages.
What you can try: Windows Recovery Environment includes a bootrec command that can attempt to rebuild the BCD (Boot Configuration Data) and repair the Master Boot Record. This is a command-line operation that, done correctly, resolves a surprising number of bootloader-related failures.
If the bootloader corruption was caused by malware, repairing the bootloader without also removing the malware means the problem will return. Our virus, spyware and malware removal service handles boot-sector malware alongside the bootloader repair, ensuring the underlying cause is addressed rather than just the symptom.
When to get help: If bootrec commands don’t resolve the issue, or if you’re not comfortable working at the command line in the recovery environment, professional bootloader repair is a quick and inexpensive fix when handled by an experienced technician. Our BIOS update and recovery service covers firmware and boot-related repairs at the system level.
Cause 4: Faulty or Incompatible RAM
RAM issues are a frequently underestimated cause of boot failures. If your RAM is faulty, incorrectly seated, or if two sticks are incompatible with each other, Windows may fail to load in ways that appear identical to software or storage problems.
A RAM-related boot failure typically manifests as the system crashing or restarting during Windows loading, blue screens with memory-related error codes (MEMORY_MANAGEMENT, PAGE_FAULT_IN_NONPAGED_AREA), or the system failing to POST entirely. Intermittent RAM failure is particularly frustrating — the system boots fine sometimes and fails other times, making diagnosis harder.
What you can try: If you have multiple RAM sticks, try booting with only one installed, then try the other — this identifies whether one stick is faulty. Reseat the RAM (remove and reinsert firmly) to rule out a seating issue. Windows Memory Diagnostic (accessible from the recovery environment) can detect RAM errors, though MemTest86 run from a USB is more thorough for intermittent failures.
If you recently upgraded your RAM and the boot problems appeared immediately after, the new RAM may be incompatible with your motherboard or not installed correctly. Our laptop RAM upgrade service ensures RAM upgrades are installed and tested correctly.
Cause 5: Failed Windows Update
Windows Update is a common trigger for boot failures in otherwise healthy systems. A poorly tested update, an update that conflicts with an existing driver, or an update that didn’t install completely can leave Windows in a state where it partially loads but can’t complete the boot process.
The symptom is typically a system that was working fine until you installed or Windows automatically installed an update — after which it fails to boot, loops to Automatic Repair, or produces a BSOD. Our blog on PC crashing after the latest Windows update covers this specific scenario in detail.
What you can try: From the Windows Recovery Environment, navigate to Troubleshoot → Advanced Options → Uninstall Updates. Rolling back the most recent cumulative update or feature update often resolves the boot failure immediately.
If the system can be made to boot in Safe Mode (accessible from the recovery environment’s startup settings), you can uninstall the problematic update from within Windows, reinstall drivers, or run system file checks with access to the full Windows toolset.
Cause 6: Driver Conflict or Corrupted Driver
A recently installed or automatically updated driver that is incompatible with your system can prevent Windows from loading, because drivers are loaded during the boot process, and a driver that crashes during loading takes Windows down with it.
Graphics drivers, storage controller drivers, and network adapter drivers are the most common culprits. If Windows updated a driver automatically and the system stopped booting immediately after, a driver conflict is the likely explanation.
What you can try: Booting in Safe Mode (which loads only essential drivers) is the diagnostic test for driver-related boot failures. If the system boots successfully in Safe Mode but fails on normal boot, a specific driver is almost certainly the problem. From Safe Mode, you can uninstall recently updated drivers, roll back to a previous driver version, or use System Restore to return to a state before the problematic driver was installed.
For systems with display issues where Windows partially loads but the screen is blank or corrupted, our fix Windows blue screen of death service addresses driver-related BSOD scenarios comprehensively.
Cause 7: BIOS/UEFI Configuration Issues
Sometimes the problem preventing Windows from loading isn’t Windows itself — it’s a BIOS/UEFI configuration that has changed, either because someone manually changed settings, a BIOS update modified defaults, or a flat CMOS battery (which stores BIOS settings) reset the system configuration.
Common BIOS-related boot failures include the boot order being changed so the system is looking for a boot device on a USB drive or optical drive rather than the hard drive, Secure Boot settings being changed in a way that’s incompatible with your Windows installation, or SATA mode being changed between AHCI and IDE, which can make Windows fail to recognise the storage controller.
What you can try: Access your BIOS/UEFI setup and check that the correct drive is first in the boot order. If the system recently had a BIOS update or the CMOS battery is old, loading BIOS defaults and then setting the correct boot drive is worth trying.
If the BIOS is showing a firmware-level problem or isn’t accessible, our BIOS update and recovery service handles UEFI/BIOS issues that can’t be resolved from within Windows.
Cause 8: Overheating Causing Thermal Shutdown
A computer that turns on, starts booting, and then shuts down or freezes before reaching the desktop may be shutting down due to overheating rather than a software or storage problem. Thermal shutdown is a protection mechanism — when the CPU or GPU reaches a dangerous temperature, the system shuts down to prevent damage.
If your system is overheating during boot, it’s typically because the cooling system is compromised — a fan has failed, the heatsink has become clogged with dust, or the thermal paste between the CPU and heatsink has dried out and is no longer conducting heat effectively.
Signs that overheating is the cause include: the system getting further into the boot process on the first attempt after the machine has been cold for a while, the system shutting down faster on subsequent attempts as it retains heat, and fans that are either not spinning or spinning at maximum speed immediately.
Our cooling system repair service addresses thermal management failures, including fan replacement, heatsink cleaning, and thermal paste reapplication. Our laptop fan replacement service specifically addresses fan failures in laptops, where cooling is more compact and more sensitive to component failure. Our blog on signs your computer needs professional cleaning covers how dust accumulation contributes to thermal problems.
Cause 9: Failing Power Supply
An inadequate or failing power supply unit can cause intermittent boot failures that are difficult to diagnose because the symptoms — random shutdowns, failure to POST, crashes during loading — overlap with almost every other cause on this list.
A PSU that’s degrading may provide enough power to turn the system on and run basic hardware checks but fail to sustain the load required to power the drive and run Windows simultaneously. The symptom is often a system that attempts to boot, gets a variable distance through the process, and then shuts down or restarts without any error message.
If your system makes it further into the boot process sometimes than others with no other changes, and particularly if you’ve recently added hardware (additional drives, a new GPU, more RAM) that increased the power demand, PSU failure is worth investigating. Our power supply repair service diagnoses and replaces failing PSUs.
Cause 10: Motherboard Failure
Motherboard problems are the most difficult to diagnose and the most consequential — because the motherboard is what everything else connects to. Capacitor failure, a damaged PCIe slot, failed voltage regulators, or a corrupted UEFI firmware can all produce boot failures that look identical to software or storage problems from the outside.
Motherboard-related boot failures often present with POST failures (no display, no beep codes, no response), random and unpredictable boot behaviour, or persistent failures that don’t respond to any software-based repair attempts.
If you’ve worked through all the above causes and the system still won’t load Windows, and particularly if the system has experienced a lightning strike, power surge, or liquid damage, motherboard hardware failure is likely. Our motherboard repairs service handles component-level board diagnosis and repair across all major brands. Our computer not starting repair service covers the full diagnostic process when the root cause is unclear.
Your Data: Protecting It Through All of This
Regardless of which of the above causes is responsible for your boot failure, your data priority should be established before aggressive repair attempts. If the system contains important files — documents, photos, client data, financial records — and you don’t have a current backup, data preservation takes precedence over Windows repair.
The majority of boot failures described above don’t destroy data — the files on the drive are typically intact even when Windows can’t load. A professional technician can usually access the drive, verify the data is readable, and back it up before any repair work begins. This sequencing — data first, repair second — is what prevents a recoverable situation from becoming an irrecoverable one.
If the drive is failing (Cause 2 above), the urgency of data recovery increases significantly. Our data recovery Melbourne and emergency data recovery services handle data extraction before repair or replacement work begins. Our blog on DIY data recovery vs professional recovery explains when self-help data recovery is appropriate and when professional recovery is necessary.
For anyone without a current backup, the experience of a boot failure is an excellent motivation to set one up before it happens again. Our data backup and recovery service and cloud backup service establish automated backup systems that ensure your data is protected regardless of what happens to your hardware.
When to Try Self-Repair vs When to Call a Professional?
The repair approaches above range from things any Windows user can attempt to things that require specialist equipment and expertise. Here’s a practical guide to knowing which category your situation falls into.
Reasonable to try yourself: Startup Repair from recovery environment, uninstalling a recent Windows update, booting in Safe Mode to identify driver issues, reseating RAM, checking BIOS boot order.
Better handled professionally: Failing drive with data to recover, BSOD errors you can’t interpret, boot failures that don’t respond to recovery environment tools, any situation involving unusual sounds from the drive, suspected hardware failure (motherboard, PSU, RAM), or a system that’s had physical trauma (drop, liquid spill, lightning).
Our computer not starting repair service starts with a comprehensive diagnostic to identify the exact cause before any repair work is quoted — so you have a clear picture of what’s wrong and what it will cost before committing.
For laptops specifically, our laptop repair service handles boot failure diagnosis and repair including the specific challenges of laptop hardware access. For desktop PCs, our PC repair service covers the full range of desktop hardware and software repair. Our frozen computer crash repair service specifically addresses systems that freeze, crash, or fail to load in ways that indicate either software or hardware problems.
If you’re not sure whether your situation requires professional help or can be self-resolved, our drop-off vs mobile vs remote IT support guide explains the different service options and which suits different types of computer problems.
Conclusion
A computer that turns on but won’t load Windows has a diagnosable cause — the right approach is working through the possibilities systematically rather than guessing.
The most common causes are corrupted system files, failing storage, boot sector corruption, RAM problems, failed Windows updates, and driver conflicts — all of which are fixable.
The symptoms you’re seeing provide meaningful diagnostic information. A blinking cursor, a specific error message, a BSOD error code, or a freeze at a particular point in the loading process all point toward specific causes.
Data preservation takes priority over repair when there’s any possibility of storage failure. Back up first, repair second.
Overheating and hardware failure (PSU, motherboard, RAM) produce boot failures that are indistinguishable from software problems without proper diagnostic tools — which is why persistent failures that don’t respond to software repair attempts warrant professional hardware assessment.
