Overview
A Windows computer that will not start normally may have a power, hardware, boot, update, driver, disk, or Windows startup problem. Start by observing exactly how far the device gets before taking recovery actions.
Why this happens
The failure can occur before Windows loads, during sign-in, after an update, or when Windows attempts to load drivers and services. The point where startup stops is important diagnostic evidence.
Before you begin
- Disconnect unnecessary USB devices but leave required keyboard, mouse, and power connected.
- Record any error, recovery screen, beep, or blinking-light pattern.
- Do not enter BitLocker recovery keys from untrusted sources.
- If the device may contain unsynchronized business data, avoid reset or reinstall options.
Click-by-click troubleshooting
Step 1: Confirm power and startup behavior
Action: Connect the approved power adapter. Press the power button once and observe the screen, lights, fans, and sounds.
Why this matters: A device with no power symptoms is different from a device that powers on but cannot load Windows.
What to look for: Look for manufacturer logo, Windows logo, black screen, recovery screen, repeated restart, or no power response.
Expected result: You should be able to classify the failure as power/hardware, display, or Windows startup related.
Step 2: Remove unnecessary external devices
Action: Shut down if possible. Disconnect docks, USB storage, printers, external displays, and other nonessential peripherals. Start the computer again.
Why this matters: Faulty peripherals or bootable USB devices can interfere with normal startup.
What to look for: Note whether Windows starts normally with peripherals removed.
Expected result: If startup succeeds, reconnect peripherals one at a time to identify the trigger.
Step 3: Record Windows Recovery information
Action: If Windows Recovery Environment appears, photograph or record the displayed options and error information before selecting anything.
Why this matters: Recovery messages can identify update, boot, disk, or BitLocker conditions.
What to look for: Look for Automatic Repair, Startup Repair, BitLocker recovery, error codes, or rollback messages.
Expected result: You should have clear evidence before attempting recovery actions.
Step 4: Try Startup Repair only if recovery is already available
Action: If Windows Recovery Environment is already displayed and organizational policy allows it, select Troubleshoot > Advanced options > Startup Repair.
Why this matters: Startup Repair can correct some boot problems without reinstalling Windows.
What to look for: Record whether Startup Repair completes, reports it could not repair the PC, or requests additional credentials.
Expected result: Windows should either start normally or provide a repair result for escalation.
Step 5: Check whether the problem began after an update
Action: If the recovery screen indicates an update problem or the user confirms the issue began immediately after an update, record that timing. Do not remove updates unless IT directs you.
Why this matters: A clear change timeline can significantly narrow the cause.
What to look for: Look for recent update installation, restart loops, or rollback messages.
Expected result: You should know whether an update is a likely trigger without making an irreversible change.
Step 6: Stop if BitLocker recovery or disk errors appear
Action: If prompted for a BitLocker recovery key, or if the system reports disk, SMART, or storage errors, stop and document the message.
Why this matters: These conditions can involve encryption or failing storage and should be handled carefully to protect data.
What to look for: Look for a BitLocker recovery key ID, drive errors, SMART warnings, or repeated disk-check failures.
Expected result: The device should be escalated with the exact evidence rather than reset or reinstalled.
What to look for
- No power response suggests hardware or power delivery.
- Manufacturer logo but no Windows load suggests boot or storage problems.
- Recovery loop after an update suggests a Windows startup or update issue.
- BitLocker prompts require approved recovery procedures.
When to stop
When to contact IT
Contact J3 Systems Group if the computer will not power on, cannot pass the manufacturer logo, enters repeated recovery loops, displays BitLocker recovery, reports disk errors, or Startup Repair cannot correct the issue. Include article code KB-10.004 and photos of the exact startup screen.
Need help with this issue?
J3 Systems Group supports small businesses and nonprofits with Microsoft 365, Google Workspace, cybersecurity, devices, documentation, and day-to-day IT operations.
Contact J3 Systems GroupAuthoritative references
Vendor interfaces, licensing, and security guidance can change. Verify current platform behavior against the primary documentation below before making high-impact production changes.