Windows 11 Black Screen on Startup: Diagnose It by Boot Stage

“Windows 11 black screen on startup” describes several different failure stages. It is not one diagnosis and does not have one universal repair. The screen may be blank before the computer finishes its firmware checks, after the firmware hands control to a boot device, while Windows is loading, at sign-in, or after the user signs in. It may also be displaying normally on a different connector or monitor.

This page identifies the stage with the fewest safe tests and routes the reader to the cause-specific procedure. It is intentionally a diagnostic router. Once a branch is supported, stop here and use the named specialist FIX. Do not perform every branch.

Searchable Windows error codes and exact messages

Windows 11 can display a stop error on a black background. If the screen contains a stop code, QR code, named .sys file, Recovery heading, File: line, or Info: line, it is not a featureless blank-screen case. Photograph the complete screen and search or route by the exact identifier before using this page’s display and shell branches.

Use this router when all of the following are true:

• the installed operating system is Windows 11, or the same Windows 10 startup stages must be separated before choosing a repair;
• the primary symptom is a blank or black display during startup, sign-in, or the transition to the desktop;
• the cause is not yet demonstrated;
• the user can safely observe the startup sequence, test a known-good direct display path, or enter Windows Recovery Environment without changing disk layout or firmware configuration; and
• the goal is to select one appropriate specialist repair rather than apply a generic list of fixes.

It also applies when the symptom description is ambiguous—for example, “black screen with cursor”—and the first job is to determine whether the visible cursor is a pre-Windows blinking text cursor or a movable Windows mouse pointer.

Do not use this router as the repair procedure when any of the following is already established:

• the screen shows an exact Windows stop code, Recovery status, named file, or firmware error that has its own condition page;
• the device never powers on, repeatedly loses power, emits a documented hardware diagnostic pattern, overheats, smells hot, has liquid or impact damage, or shows electrical damage;
• no image appears in firmware setup or Windows Recovery Environment on any known-good direct display path;
• the storage device disappears from firmware, reports I/O errors, makes abnormal mechanical noise, or contains irreplaceable data without a verified backup;
• BitLocker recovery is required and the correct recovery key is unavailable;
• the black display occurs only inside one application, game, browser, remote-desktop session, or virtual machine after the Windows desktop is otherwise usable;
• the user is in Windows Setup and there is no correct installed Windows system to repair; or
• a specific specialist FIX has already been confirmed. Continue with that FIX instead of returning to this general page.

No-image hardware cases may still need service, comparative testing, a model-specific manual, or a known-good GPU/display path. That is outside the Windows repair scope of FIX-058.

The following details are useful but are not required to begin stage detection:

• the exact Windows 11 edition and build;
• the GPU model or whether the system uses switchable graphics;
• the exact display-driver version;
• whether the machine uses UEFI/GPT or legacy BIOS/MBR;
• whether the display path is HDMI, DisplayPort, USB-C, Thunderbolt, an internal panel, or a dock;
• the update or driver package installed immediately before the symptom;
• whether the device uses Device Encryption or BitLocker; and
• the cause of the first failed startup.

Do not fill gaps with assumptions. Record unknown values as unknown. Firmware mode matters only if the evidence later points to a pre-Windows boot problem. GPU details matter only if the display-driver branch is supported. An exact update identifier matters only if the problem began immediately after Windows Update and the update branch remains the best explanation.

Prepare the following before changing anything:

1. A phone or camera to capture the complete screen, including any brief code, File: line, or monitor message.
2. The computer’s power adapter. Do not perform recovery work on a nearly depleted battery.
3. For an external display path, one known-good monitor or television, one known-good cable, and preferably a direct connection that bypasses docks, KVMs, capture devices, USB display adapters, and converters.
4. The BitLocker or Device Encryption recovery key if the recovery environment requests it.
5. A record of the last known-good startup and the last material change: Windows Update, graphics driver, dock, monitor, firmware, System Restore, clone, storage change, or shell customization.
6. A way to record each test and its result. A changed result is evidence; repeating unrecorded changes destroys that evidence.
7. A backup before uninstalling an update, rolling back a driver, changing a profile, or modifying system files in a specialist procedure.

If Windows is temporarily usable, save open work before testing shutdown behavior. The full-shutdown command in this router uses /f, which closes applications without waiting for unsaved work.

Return the device to a simple, observable configuration:

1. Disconnect nonessential USB devices, storage devices, docks, KVMs, capture hardware, VR headsets, and extra displays. Keep the keyboard, mouse, power adapter, and one known-good display path.
2. On a desktop with a discrete graphics card, use the connector that previously showed Windows. Do not move the cable between motherboard and graphics-card outputs unless the machine’s documented configuration or a comparative test requires it.
3. Set the monitor to the input that physically matches the connected cable. Do not rely on automatic input switching during diagnosis.
4. Power the display on first, then start the computer once while watching the entire sequence.
5. Record the last visible milestone:
   • no manufacturer logo or firmware screen;
   • manufacturer logo or firmware setup;
   • blinking text cursor before Windows;
   • Windows logo or spinning dots;
   • sign-in screen;
   • desktop briefly visible;
   • movable mouse pointer on a black background; or
   • image visible on another display or connector.
6. Record whether the failure occurs after Restart, after Shut down and power-on, after resume from sleep/hibernate, or in all cases.

Do not enter firmware setup merely to change values. Opening it only to determine whether firmware can draw an image is a read-only test. Photograph current settings before any later model-specific change and use a separate firmware procedure.

Complete these checks in order. Stop as soon as one route is supported.

Check A — Separate “no picture” from “Windows goes black”

Start the device and try to open its documented firmware setup or one-time boot menu. If Windows Recovery Environment is already available, observe it as well.

• Firmware setup and WinRE are visible: the panel, cable, and current output path can display an image outside normal Windows. Continue to Check B.
• Firmware is visible, but a verified transition into WinRE becomes black: the image is being lost after firmware handoff. Continue to Check B and the controlled display-path checks; do not claim WinRE loaded if its interface was never visible.
• WinRE is visible, but firmware appears only on a different output or never appears on the current one: a stage-dependent output path is supported. Route to FIX-046.
• Firmware appears on a different display or connector: the output-path branch is supported. Route to FIX-046.
• No image appears in firmware or WinRE on any known-good direct display: stop Windows repair. Windows has not been demonstrated as the cause. Check power, display input, cable, direct connector, documented POST indications, and manufacturer diagnostics. Escalate to hardware service when comparative testing cannot produce a pre-Windows image.

Keyboard LEDs, fans, and startup sounds can show that the machine has power; they do not prove that Windows booted or that the GPU/display path is healthy.

Check B — Identify the last visible startup stage

Use the following distinctions exactly:

Check C — Test the current Windows display path once

Only after a Windows-stage failure is plausible:

1. Press Windows + Ctrl + Shift + B once.
2. Wait at least ten seconds.
3. Record whether the display flickers, a beep occurs, an image returns, or nothing changes.

A beep or flicker proves only that Windows received the shortcut and attempted a graphics reset. It does not prove that the graphics driver caused the original failure. If the image returns, the display/graphics route is supported; continue with FIX-009 or FIX-046 according to whether the issue is driver initialization or the selected output path.

If multiple displays, a dock, or a recently changed output is involved, use the controlled projection test from FIX-046. A blind Windows + P sequence can change output state, so do not repeat it randomly. Record each selection and wait for the display to synchronize.

Check D — Compare Restart with a true full shutdown

Use this check only if Windows can be reached temporarily, Safe Mode works, or the desktop returns after another test.

1. Save all work.
2. Test Restart from the power menu and record the result.
3. After Windows is usable again, open Terminal or Command Prompt and run:

shutdown /s /f /t 0

4. After the machine powers off, wait ten seconds, power it on, and record the result.

Interpret the comparison:

• Restart works and ordinary Shut down followed by power-on fails, while the command above works: a saved-state difference nominates FIX-036. That article must still confirm the hybrid-versus-full-start pattern before changing Fast Startup or hibernation.
• Both fail in the same way: Fast Startup is not demonstrated. Continue diagnosis.
• Only Restart fails: that is not the expected FIX-036 pattern. Route by the stage and exact error instead.

Do not repeatedly force power off to imitate a full shutdown. The command is a controlled test performed only from a usable Windows session.

Check E — Establish update or restore timing without treating timing as proof

Ask what completed immediately before the first failure.

• System Restore was running, had just completed, or the first failure occurred on its next startup: route to FIX-048.
• Windows Update installed immediately before the first failure, and no graphics, shell, profile, or output cause has been demonstrated: route to FIX-047.
• A display driver changed and normal mode fails while Windows is visible in Safe Mode or low-resolution video: route to FIX-009.
• A dock, cable, GPU connector, monitor, or projection layout changed: route to FIX-046.

The words “after an update” identify a sequence, not causation. FIX-047 contains the gates for removing an exact update and the rollback required if removal does not change the symptom.

Check F — Use WinRE and Startup Settings as discriminators

Use an existing recovery route when available. If Windows reaches sign-in, hold Shift while selecting Power > Restart. Otherwise use Windows Recovery Environment or verified Windows installation media. When normal routes are unavailable, Windows can enter automatic recovery after a controlled interrupted-start sequence; do not make repeated hard shutdowns a routine repair.

In WinRE select:

Troubleshoot > Advanced options > Startup Settings > Restart

The device may request the BitLocker recovery key. After restart, test one relevant option:

• Enable low-resolution video when an unsupported resolution, refresh rate, or output mode is plausible.
• Safe Mode when a third-party driver, shell extension, service, startup item, or update path is plausible.
• Safe Mode with Networking only when network access is required and the added drivers do not interfere with the comparison.

Interpret results narrowly:

• WinRE is visible but normal Windows is black: the display hardware can render the recovery environment. The fault is likely later in the Windows path, but the cause remains open.
• Low-resolution video works: the normal display mode, topology, or graphics-driver path is supported. Route to FIX-009 or FIX-046 based on the evidence.
• Safe Mode works: something absent or changed in Safe Mode is implicated. This does not prove the graphics driver. Continue to Check G or use FIX-047 if the problem began after Windows Update and no component is isolated.
• Safe Mode is also black, but WinRE is visible: do not infer BCD corruption. Continue by the last visible stage, exact event, and specialist branch.

Check G — Separate Explorer/shell from graphics after sign-in

Use this check only when sign-in completes or Ctrl + Alt + Delete opens the Windows security screen.

1. Press Ctrl + Alt + Delete once.
2. If the security screen appears, open Task Manager.
3. If Windows Explorer is listed, select it and choose Restart.
4. If it is not listed, select Run new task, enter:

explorer.exe

5. Record the result before changing anything else.

Interpretation:

• The desktop, taskbar, and Start menu appear: the shell-start path is strongly supported. Route to FIX-010.
• Another user account works but the original account remains black: the profile or per-user shell path is supported. Route to FIX-010.
• Explorer does not restore the desktop, but Safe Mode/low-resolution video works and display-driver evidence exists: route to FIX-009.
• Task Manager and the security screen never appear: the shell test is inconclusive. Return to the boot-stage evidence; do not assume Explorer is corrupt.

Starting explorer.exe is a discriminator, not a permanent repair. FIX-010 contains the checks for Winlogon values, shell customization, the user profile, clean boot, component repair, and exact rollback.

Choose one branch. Do not execute branches sequentially “just in case.”

Branch A — No firmware or recovery image on a known-good direct display

Stop Windows repair. Confirm external power, display power, the physical input, a known-good cable, a direct connector, and any documented POST or hardware diagnostic indication. Compare with one known-good display path. If no pre-Windows image can be produced, use model-specific hardware diagnostics or service.

Do not remove drivers, rebuild boot files, uninstall Windows updates, reset firmware defaults, or reinstall Windows. None of those actions can be validated while the system has not demonstrated a working pre-Windows display path.

Branch B — Blinking text cursor before Windows

Open FIX-031 — Diagnose a black screen with a blinking cursor before Windows starts.

That procedure distinguishes a wrong boot target, missing firmware entry, valid UEFI files without a firmware entry, BIOS/MBR boot code, an explicitly missing SYSTEM hive, and stable-volume file-system errors. It does not treat the cursor itself as proof of BCD corruption.

Branch C — Image is on another output or returns after controlled display selection

Open FIX-046 — Recover video sent to the wrong or phantom display before or after Windows starts.

Use its firmware-output, Windows projection, phantom-display, device-code, dock/USB-C, and single-direct-display branches. Preserve a known-good output until verification is complete.

Branch D — Restart/full shutdown differs from ordinary shutdown/power-on

Open FIX-036 — Stop Fast Startup or hibernation from restoring a broken boot or display state.

Do not delete Hiberfil.sys manually. FIX-036 first proves the saved-state pattern, then separates disabling Fast Startup from rebuilding hibernation state and from a driver-specific crash branch.

Branch E — The failure begins immediately after Windows Update

Open FIX-047 — Recover a black screen that begins after a Windows update when the cause is not yet isolated.

Use that article while the responsible component is still unknown. If its tests prove the display driver, shell/profile, or output path, leave FIX-047 and use FIX-009, FIX-010, or FIX-046 respectively. Remove only an exact update with a demonstrated temporal relationship and preserve the rollback path.

Branch F — The failure begins during or immediately after System Restore

Open FIX-048 — Recover a black screen or failed startup immediately after System Restore.

That procedure separates undoing the restore, the specific Windows 10 restore/0xC000021A sequence, post-restore shell/profile or graphics evidence, a displayed System Restore error, Windows component damage, and recovery without repeating the same restore point.

Branch G — Post-login shell or profile evidence is demonstrated

Open FIX-010 — Repair a post-login black screen caused by Explorer, shell configuration, or the user profile.

Use FIX-010 when starting Explorer restores the desktop, another account works, a known shell/theme customization is implicated, or clean-boot evidence identifies a third-party startup component. Do not overwrite Winlogon registry values without first reading and recording the values that actually exist.

Branch H — Post-login graphics evidence is demonstrated

Open FIX-009 — Repair a post-login black screen caused by the graphics driver.

Use FIX-009 when sign-in is reached and evidence points to display-driver initialization—for example, low-resolution video or Safe Mode changes the result and the graphics path remains implicated, a specific display driver changed immediately before the failure, or a graphics code/module is consistently recorded. Safe Mode alone is insufficient proof.

Branch I — An exact stop or Recovery code appears

Leave this router. Search the complete code, message, File: line, and boot stage. Examples:

• 0x0000007B routes to storage/controller access diagnosis.
• 0x0000009F routes to the driver or device blocking the power transition; it is not automatically the GPU.
• 0x00000116 routes to TDR/display-driver and hardware stability diagnosis.
• 0x00000117 is interpreted from a live dump, not treated as a displayed stop screen.
• 0xC000000F or 0xC0000225 requires the complete Recovery text; a named critical file, missing device, and BCD entry are different branches.

Do not continue with black-screen display steps after an exact non-display boot condition is established.

• No image outside Windows: Windows repair stops. The next action is physical display, POST, GPU, power, or platform diagnosis.
• Firmware or WinRE is visible: the current display path can render a pre-Windows image. Continue with the Windows-stage discriminator; this result does not prove Windows is corrupt.
• Blinking text cursor appears before Windows: FIX-031 becomes the active procedure.
• Another display or connector works: FIX-046 becomes the active procedure.
• Windows + Ctrl + Shift + B returns the image: the Windows graphics/display path is supported. Route to FIX-009 or FIX-046 using the other observations. The shortcut result alone does not identify a defective driver.
• Restart works but ordinary shutdown/power-on fails, and a full shutdown succeeds: FIX-036 becomes the active procedure.
• The problem begins immediately after Windows Update with no isolated component: FIX-047 becomes the active procedure.
• The problem begins during or immediately after System Restore: FIX-048 becomes the active procedure.
• Ctrl + Alt + Delete and Task Manager work, and starting Explorer restores the desktop: FIX-010 becomes the active procedure.
• Safe Mode or low-resolution video works and separate graphics evidence exists: FIX-009 becomes the active procedure.
• Safe Mode works but no component is isolated: the result narrows the field but does not establish a graphics cause. Use update timing, shell tests, clean-boot evidence, and exact device events in the relevant specialist procedure.
• A stop code or Recovery text appears: the exact-code condition page becomes the active procedure.
• Nothing changes after the safe discriminators: stop rather than escalating into speculative repairs. Collect the boot-stage observations, display comparison, recovery visibility, exact recent change, and any code or dump for expert diagnosis.

• Do not rebuild BCD, run broad bootrec commands, alter an EFI System Partition, change an Active flag, or rewrite boot code for a post-login display or shell symptom.
• Do not format, clean, convert, resize, move, delete, or recreate any partition as black-screen troubleshooting.
• Do not uninstall the graphics driver merely because the screen is black or because Safe Mode works.
• Do not uninstall several updates at once. A specialist update procedure must identify the exact package and preserve a rollback path.
• Do not run every FIX in this router. Once one branch is supported, stop routing and use that specialist article only.
• Do not repeatedly hard-power-off the device as a repair. A controlled interruption sequence is reserved for entering WinRE when safer routes are unavailable.
• Do not reset firmware defaults, toggle UEFI/legacy mode, change SATA/AHCI/RAID/VMD mode, disable Secure Boot, clear TPM, or update firmware without exact model-specific evidence and a separate rollback plan.
• Do not assume WinRE assigns the installed Windows volume the letter C:.
• Do not assume 0xC000000F or 0xC0000225 means “corrupt BCD.” Record the full screen.
• Do not describe 0x00000117 as a displayed blue- or black-screen bug check. It identifies a live dump.
• Do not treat a monitor’s No signal message as a Windows error.
• Do not confuse a movable mouse pointer with a blinking text cursor.
• Do not use Registry Editor, third-party driver cleaners, partition utilities, “PC optimizer” software, or unverified command lists during the routing stage.
• Do not continue software repair when the disk disappears, produces I/O errors, or contains unprotected irreplaceable data.
• Do not force-close applications with the full-shutdown command until work is saved.

FIX-058 is designed to avoid persistent changes. Restore only what was changed during diagnosis:

1. Display topology: reconnect additional monitors, docks, KVMs, and adapters one at a time only after one direct display completes verification. Restore the previous main display in Settings > System > Display if a controlled projection test changed it.
2. Projection mode: use Settings > System > Display or the controlled Windows + P menu to restore the recorded starting mode. Do not cycle blindly.
3. Safe Mode or low-resolution video: restart normally. These Startup Settings choices are normally one-boot states.
4. Explorer discriminator: no rollback is required for manually starting or restarting explorer.exe. If it restored the desktop, continue with FIX-010 to make only the demonstrated correction.
5. Disconnected peripherals: reconnect one device at a time. If reconnecting one device recreates the black screen, disconnect it again and move to its device/dock/output procedure.
6. Full-shutdown comparison: no setting was changed by shutdown /s /f /t 0. It only produced one full shutdown. If the test exposes a Fast Startup difference, use FIX-036 for the actual setting change and rollback.
7. Any change made outside this router: use the rollback section of the specialist FIX that authorized it. Do not improvise a combined rollback.

If the device becomes less bootable after any test, stop. Return to the last known-good direct display configuration and recovery path. Do not add another change until the result is understood.

Routing is complete only when the observation can be reproduced and points to one branch. A permanent repair is verified under the chosen specialist FIX.

Before leaving FIX-058, record:

• whether firmware setup or WinRE is visible;
• whether the last visible stage is firmware, blinking text cursor, Windows logo/spinning dots, sign-in, or post-login;
• whether the pointer is a movable mouse pointer or a blinking text cursor;
• whether another direct display or connector works;
• whether Windows + Ctrl + Shift + B changes the image;
• whether Ctrl + Alt + Delete and Task Manager are available;
• whether explorer.exe restores the desktop;
• whether Safe Mode or low-resolution video changes the result;
• whether Restart differs from shutdown/power-on;
• whether the failure begins immediately after Windows Update or System Restore; and
• the complete text of any stop or Recovery screen.

After the specialist repair reports success, verify all applicable paths:

1. Start Windows normally to sign-in and the desktop.
2. Restart once and confirm the same display path works.
3. Shut down normally, wait ten seconds, and power on once.
4. If Fast Startup was part of the diagnosis, perform the specialist article’s hybrid-versus-full-start verification.
5. If multiple displays or a dock are required, reconnect one component at a time and repeat sign-in.
6. Confirm the desktop, taskbar, Start menu, keyboard, mouse, and required displays remain usable for at least ten minutes.
7. Review Windows Update history, Device Manager, Reliability Monitor, or event/dump evidence only when the chosen branch calls for it.
8. Confirm the rollback material created by the specialist procedure still exists until several successful starts have completed.

A single successful boot is encouraging but not sufficient for an intermittent output, driver, storage, or saved-state problem.

Confidence in this router is high for stage selection when the observations are repeatable: pre-Windows images, Windows logo, sign-in, a movable pointer, another working output, Task Manager, Explorer launch, Safe Mode, and Restart-versus-shutdown behavior are materially different states. Confidence in any root cause remains limited until the specialist procedure demonstrates it.

The page deliberately makes no universal causal claim from the phrase “Windows 11 black screen on startup.” It also does not claim laboratory reproduction for every routed condition. Reporter-confirmed outcomes and condition-linked evidence remain separate from controlled reproduction.

Stop and seek qualified help when any of the following occurs:

• no image appears in either firmware or WinRE on a known-good direct display;
• the machine shows hardware diagnostic lights or tones, loses power, overheats, or has physical damage;
• the storage device disappears, reports I/O errors, or contains important data without a verified backup;
• BitLocker requests a key that cannot be positively matched to the device;
• the display shows an exact code or named file not covered by the selected branch;
• Windows becomes less bootable after a test;
• recovery media cannot be positively distinguished from the installed system;
• the available observations support more than one destructive or firmware-level action;
• the symptom remains intermittent and cannot be reproduced under a controlled display configuration; or
• the specialist FIX reaches its own stop condition.

The correct end state for FIX-058 is not “every possible fix was tried.” It is: one startup stage was established, one cause-gated specialist procedure was selected, and unrelated repair paths were left untouched.