Source attribution: This post is a curated breakdown of What to Do When a Computer Will Not Start, with additional PCRuns context and practical computer guidance.
If your computer won’t start, the big risk isn’t just “downtime”—it’s accidentally making a data problem worse while you’re trying quick fixes. The safest approach is to start with the simple, non-destructive checks (power, display, basic reset), then decide whether you’re dealing with a hardware power issue, a Windows boot issue, or a failing drive. I’m John at PCRuns—this is local computer repair guidance for Milwaukee and Wisconsin residents, with a repair-before-replace mindset and no-pressure recommendations.
What the source says
The PCRuns material is focused on the real-world “computer won’t start” situation and points readers toward practical next steps: identify what kind of “won’t start” you’re seeing, try the simplest checks first, and use diagnostics/system recovery and data recovery/backup services when the issue isn’t something you can safely solve at home. The site also emphasizes a broad set of related services (diagnostics, operating system recovery, security recovery, upgrades, and data recovery/backup) that often apply when a device won’t boot.
Because the excerpt provided is site navigation and summaries rather than a full step-by-step article, I’m treating it as the spine (the intent and scope), and I’m adding the concrete, careful workflow I use in the shop so you can avoid the two common mistakes: (1) replacing parts blindly and (2) repeatedly forcing a struggling drive to boot until it fails completely.
First: what does “won’t start” actually mean?
People use the same phrase for several different failures. The quickest way to narrow this down is to match your symptom to one of these buckets:
- No signs of life: no lights, no fan, no sound.
- Power but no picture: fans/lights on, but screen stays black.
- Starts but won’t load Windows: spinning dots forever, Automatic Repair loop, blue screen, or “No boot device.”
- Starts sometimes: intermittent booting, random shutdowns, or it only starts after many tries.
Those buckets matter because the safest next step is different for each one.
Data safety rule (before you try a bunch of fixes)
If the computer contains anything you can’t easily replace—family photos, school work, business QuickBooks files, irreplaceable emails—treat repeated boot attempts as a risk. A failing drive can degrade fast when it’s repeatedly powered on, heats up, and tries (and fails) to read damaged areas.
Step-by-step: the least risky checks (laptops and desktops)
1) Check power (don’t assume it’s the computer)
- Laptop: verify the charger is firmly seated; if you have a USB-C laptop, try a known-good compatible USB-C charger; look for a charging light.
- Desktop: confirm the power cable is fully seated at both ends; try a different wall outlet or power strip; confirm the monitor is powered on.
If there are no lights or signs of life, it’s often power-related (charger, battery, DC jack, power supply, or motherboard). That’s a “stop and evaluate” moment—especially if the machine is important and you don’t want to risk further damage.
2) Do a “hard reset” (safe, quick, and often effective)
This clears a stuck power state. It does not erase your files.
- Laptop (most models): unplug the charger. If the battery is removable, remove it. Hold the power button down for about 15–20 seconds. Reconnect power (and battery if removable) and try to start.
- Desktop: shut down, switch the power supply off (if it has a switch), unplug, hold the power button 10–15 seconds, plug back in, and try again.
If it boots after this, you may still want to follow up—unexpected power-state issues can be harmless, but they can also be an early warning of power or sleep/hibernate trouble.
3) If it powers on but you see a black screen
Separate “computer problem” from “display problem”:
- Desktop: check the monitor input source (HDMI/DP), reseat the video cable, and if you have a graphics card, try the other port(s). If the CPU has integrated graphics, you can test the motherboard video output (only if your system supports it).
- Laptop: raise brightness, connect an external monitor/TV if available, and listen for Windows sounds (startup chime, login sound) that suggest it’s actually running.
If an external monitor works but the laptop screen stays dark, you may be looking at a screen/backlight/cable issue—not a “won’t start” problem. PCRuns handles screen and hinge repairs, and those are typically very fixable when the underlying system is OK.
4) If you get a Windows error, looping repair, or “no boot device”
This is where people can accidentally make things worse by guessing. The main possibilities are:
- Windows boot corruption (often repairable without touching your personal files, but it depends what’s damaged)
- Drive not detected (loose connection on a desktop, failing SSD/HDD, or a failed controller)
- BitLocker recovery prompt (not a “virus” by itself—often triggered by hardware/firmware changes or boot issues)
If your system asks for a BitLocker recovery key and you don’t have it, don’t keep flipping settings at random. Data recovery options become much narrower when encryption is involved. Microsoft’s security guidance is clear that encryption is meant to prevent access without the key—so the goal is to recover the key (if it exists), not to “bypass” it. For background on Microsoft security concepts and device protection, see Microsoft’s security documentation at Microsoft Learn Security.
Practical decision tree: repair, recovery, upgrade, or replace?
In Milwaukee, I see three common endings to a “won’t start” story. Here’s how I think about them in plain language.
Outcome A: It’s a power/display issue
Typical signs: no lights, no fan, or it clearly powers but nothing displays; behavior doesn’t change even when you attempt Windows recovery tools.
What usually makes sense: diagnose first. A failed charger or power supply is often a straightforward fix. A motherboard issue can be economical or not depending on the model and age—this is where an honest evaluation matters.
Outcome B: Windows is damaged but the drive is OK
Typical signs: BIOS/UEFI sees the drive, but Windows won’t load or repair loops; system previously shut down during an update or lost power.
What usually makes sense: system recovery or Windows repair. This can be a reasonable repair-before-replace scenario, especially if the machine is otherwise in good shape. If the PC is older and has a mechanical hard drive, this is also a good time to consider an SSD upgrade rather than just reinstalling Windows onto a slow drive.
If you’re considering upgrades as part of the fix, our computer upgrade guides can help you understand when SSD/RAM changes are noticeable and when they’re not.
Outcome C: The drive is failing (data first, then repair)
Typical signs: it got slower over time, then started freezing, then stopped booting; you hear clicking (HDD) or see frequent “repairing disk” messages; SMART warnings (when visible) or “no boot device” after a rough week of glitches.
What usually makes sense: prioritize your files before heavy troubleshooting. A common path is: attempt a non-destructive data recovery approach, then replace the drive and restore the system. PCRuns focuses on data recovery and backup as a service area for exactly this situation—see data recovery and backup diagnostics for the kinds of scenarios we evaluate.
Safe troubleshooting steps that genuinely apply (without turning this into a giant generic guide)
Below are steps I consider “generally safe” for most home users. I’m leaving out the risky ones (firmware flashing, registry hacks, random command-line repairs) because they can increase downtime and data loss when used blindly.
Reseat what’s easy and low-risk (mostly desktops)
- Unplug, then reseat RAM (if you’re comfortable opening the case).
- Reseat the SATA data and power cables to the drive.
- Remove non-essential USB devices (printers, external drives, dongles) and try booting with just keyboard/mouse.
If you’re not comfortable opening a computer, it’s fine to stop here. There’s no shame in that—forcing it can create a bigger bill.
Try one clean boot attempt after disconnecting peripherals
Sometimes a stuck USB device or docking station can block boot. Disconnect everything except power and one display (and on a desktop, keep keyboard/mouse).
When cloning is the right move (and when it’s not)
If the drive is readable but unstable, cloning to a new SSD can be a smart “save what we can” move—but it’s not always appropriate if the drive is failing badly. The wrong cloning approach can pound a failing drive for hours and reduce the odds of recovery.
If you want to understand the concept and risks before doing anything, start with PCRuns’ hard drive cloning guides. If your data is high-value, it’s often wiser to get an evaluation first rather than letting a DIY clone run overnight.
Common pitfalls I see (and how to avoid them)
“It’s probably the battery / it’s probably the SSD” guessing
Parts swapping can be reasonable, but guessing tends to snowball: a charger turns into a battery, then a motherboard, then a reinstall. A short diagnostic step can prevent spending money twice.
Repeated forced shutdowns during boot
Sometimes people force power-off five or ten times in a row. If Windows is updating, that can corrupt the install. If the drive is failing, it increases wear and heat. Try a single clean attempt after a hard reset and peripheral disconnect—then reassess.
Signing into accounts on a “maybe infected” PC
If the “won’t start” episode follows popups, unknown antivirus warnings, or suspicious remote access events, treat it as a security incident. Don’t log into banking or business email on the affected PC until it’s checked. For general, authoritative security readiness guidance, the U.S. Cybersecurity & Infrastructure Security Agency publishes practical recommendations at CISA.
When to stop DIY and get it evaluated
- You hear clicking/grinding (HDD) or the system suddenly can’t see the drive.
- The computer powers on and off repeatedly (boot loop) with no progress.
- You’re seeing a BitLocker recovery screen and you don’t have the key handy.
- This is a business computer and downtime matters.
- You’ve tried the safe steps above and symptoms don’t change at all.
Need local computer help?
PCRuns serves readers in Milwaukee, Wisconsin and nearby communities. Services or primary themes include computer diagnostics, Windows repair, malware removal, data backup, system recovery, hardware upgrades, remote support, small business IT support, broken screen replacement, broken hinge repair.
Schedule a free evaluation, get an honest opinion, or see whether repair makes sense with no pressure and no obligation.
Bottom line
“Won’t start” is a symptom, not a diagnosis. Start with the non-destructive checks (power, hard reset, display test, remove peripherals). If signs point to a failing drive or encryption/recovery-key situation, shift immediately to data-first thinking. When it’s a straightforward Windows repair or a sensible upgrade (like moving from a hard drive to an SSD), repair-before-replace can be the best value—but when the core hardware is failing and the device is older, replacement can honestly be the more practical call. Either way, the right next step is the one that protects your files and avoids paying twice.
Q&A
Is it safe to keep trying to start a computer that won’t boot?
A few basic, low-risk attempts are fine (power check, one hard reset, disconnect peripherals). But if you suspect drive failure—new clicking noises, “no boot device,” or it was slowing down for weeks—repeated boot attempts can make data recovery harder. In that case, prioritize your files and get it evaluated.
My PC turns on but the screen is black. Does that mean it’s dead?
Not necessarily. It can be a monitor/cable/input issue (common on desktops) or a laptop screen/backlight issue. Testing with a known-good monitor/TV is a quick way to separate a display problem from a true boot problem.
What does “No boot device” usually mean?
It means the system firmware (BIOS/UEFI) can’t find something bootable. That can be as simple as a loose cable (desktop) or as serious as a failing SSD/HDD. If your files matter, avoid lots of repeated restarts and focus on diagnosis/data recovery.
If Windows won’t start, should I reinstall Windows right away?
Not right away if you haven’t protected your data. A reinstall can be the right repair in some cases, but the safer order is: confirm your important files are backed up or recoverable first, then choose repair vs reinstall based on what failed.
When does replacement make more sense than repair?
Replacement can be the better value when the motherboard or multiple major components are failing on an older system, or when the repair cost approaches the value of a more reliable newer/refurbished machine. A quick diagnostic is usually the only honest way to make that call without guessing.






Leave a Reply