Long Black Screen During Boot Before the Picture Appears? Driver Load, Display Detection & Fast Startup Diagnosis Guide

Key Summary
Every boot leaves the screen black for a long stretch before the picture finally appears on its own, and everything then works normally. This guide separates a slow Windows loading stage from other causes, using the stage where the black screen falls, the cursor test, and Safe Mode and Fast Startup comparisons to find which layer the delay belongs to.
The Shape of the Problem: Late Picture, Not No Picture
This guide covers one specific shape, and the shape itself is the whole diagnosis. Every time the machine is switched on, it powers up — the fans spin, the drive light flickers — but the screen stays black for a long stretch, tens of seconds or longer, before the picture finally appears on its own. No key is pressed, no cable is touched, nothing is restarted. The picture simply arrives late. Once it arrives, the machine reaches the desktop and everything works normally: programs open at their usual speed, games run as they always did, and nothing else seems wrong.
Three details define the shape, and all three have to be present. First, the picture does arrive — late, but on its own, without any intervention. Second, it happens every time the machine boots, not once in a while. Third, once the machine is inside Windows, everything is normal. A machine that fits those three is a machine with a loading delay, and this guide is about finding which loading layer the delay belongs to.
That distinction — late picture, not no picture — is the line this whole guide holds. A machine whose screen stays black and never shows a picture, however long it is left, is a different problem: a black screen that stays is a fault in the display path, not a delay in loading. A machine that shows no picture on a cold start but works normally after a restart is a different problem again: there the restart itself changes the result, which points at the cold-start sequence. A machine that is slow to show a picture only the first time after a hardware change, and then boots normally ever after, is also different: a first-boot delay after new hardware is a one-off event, not a delay that repeats every boot. And a machine whose black screen appears only while a game is loading is not a boot problem at all — the loading stage there is the game's, not the machine's. If the picture in question never arrives, or only arrives after a restart or a keypress, leave this guide: the shape does not fit, and the diagnosis that follows will point at the wrong layers.
The first conclusion most owners reach is that a long black screen at boot means the graphics card is failing. It does not. A card that is failing does not usually produce a picture that is merely late and then perfect — it produces artefacts, crashes, or no picture at all. A delay that ends in a normal desktop, every time, points at something taking too long during loading, not at something broken. The delay could sit in the driver loading, in the display being detected, in the saved state being restored, in the desktop shell starting up, or in the system reading from disk — and each of those is a different layer with a different test. The rest of this guide is about telling them apart, one comparison at a time.
One honest gap should be stated up front. There is no fixed waiting time that defines a fault, and this guide does not invent one. How long is too long depends on the hardware, the storage, the number of displays, and what is installed — a machine with a slow drive and two displays will always take longer to show a picture than a machine with a fast drive and one display, and both can be healthy. The judgement this guide uses instead is whether the machine is still working while the screen is black, and which stage the black screen falls in. A machine whose drive light is flickering, whose Caps Lock light answers, and whose picture eventually arrives is still loading. A machine whose lights are dead and whose picture never arrives is not loading at all. Time the delay with a watch and write the number down — but judge the machine by what it is doing during the delay, not by the number alone.
How a Boot Is Staged, and Where a Delay Can Sit
A boot is not one event. It is a sequence of stages, and a delay can sit in any one of them. Knowing which stage the black screen falls in is the first and most important piece of the diagnosis, because a delay in one stage points at one set of causes and a delay in another stage points at a completely different set. Getting the stage wrong sends the whole investigation in the wrong direction.
The first stage is the firmware stage, before Windows starts. The machine powers on, the firmware runs its checks, and the maker's logo or the motherboard logo usually appears on the screen. If the logo itself stays on the screen for a long time, or the screen stays black before the logo ever appears, the delay is in this stage — the machine has not yet reached Windows at all. That stage is not this guide: it belongs with the firmware and initialisation diagnosis, where the checks before Windows are the subject.
The second stage is the Windows loading stage, and it is the stage this guide covers. The logo passes quickly, and then the screen goes black while Windows loads: the spinning dots may appear, or the screen may stay black until the login screen arrives. The machine is working during this stage — the drive light flickers as Windows reads its files, the driver loads, the displays are detected, the saved state is restored — but nothing is shown yet. A delay here is a Windows loading delay, and the layers in this guide are the layers that load in this stage.
The third stage is after login. The login screen appears, the password is entered, and then the screen goes black again — this time with or without a mouse cursor — while the desktop shell loads. A delay here is a different shape again: the driver and the displays are already up, and what is slow is the desktop itself or a program starting with it. This guide touches that stage only through the cursor test, because a black screen after login with a cursor points at the desktop shell layer, and that layer is one of the five below.
The practical way to tell the stages apart is to watch what the machine shows and when. Note the moment the power button is pressed, the moment the logo appears, the moment the logo disappears, and the moment the login screen or desktop appears. Write those times down with a watch. A machine whose logo passes in a few seconds and whose login screen is then late is a machine with a Windows loading delay. A machine whose logo itself lingers is a machine with a firmware-stage delay. The two look alike from the front — both are a black screen at boot — and they are different problems with different answers.
| Stage | What you see | Where the delay sits |
|---|---|---|
| Firmware stage, before Windows starts | The logo stays on screen a long time, or the screen stays black before the logo ever appears | Firmware and initialisation — not this guide |
| Windows loading stage | The logo passes quickly, then the screen stays black while the spinning dots show or until the login screen arrives | Windows loading — this guide |
| After login | The login screen appears on time, then the screen goes black again, with or without a cursor | Desktop shell or a startup program |
While the screen is black, there are three signs that say whether Windows is still alive underneath. The drive light: if it flickers, Windows is reading and writing, which means loading is still in progress. Sound: if the machine plays the login sound, or any sound, Windows has reached a stage where sound works, which means the load is nearly complete. And the Caps Lock or Num Lock light: press the key and watch the light — if the light answers, Windows is running and responding to the keyboard, which means the machine is alive behind the black screen. If the light does not answer, the machine may have stopped before Windows started, and the problem is not a loading delay at all. These three signs are the survival test for a black screen, and they should be checked before any other step: they decide whether the machine is loading slowly or has stopped.
The Deciding Forks: Four Questions That Narrow the Field
The whole guide turns on four forks. Each fork is a comparison, and each comparison removes a whole set of possibilities. They should be done in order, before any setting is changed, because a setting changed before the fork is tested destroys the evidence the fork would have given.
Fork One: Which Stage Is the Black Screen In?
The first fork is the stage. Use the times recorded in the previous section. If the logo passes quickly and the black screen falls between the logo and the login screen, the delay is in the Windows loading stage, and this guide applies. If the logo itself lingers, or the screen stays black before the logo ever appears, the delay is in the firmware stage, and this guide does not apply — the firmware and initialisation diagnosis is the right path. If the login screen appears on time and the black screen only comes after login, the delay is in the desktop shell stage, and the cursor test in fork two is the way in. Getting this fork wrong is the most expensive mistake in the guide, because every layer that follows assumes the delay is in the Windows loading stage. A firmware-stage delay investigated as a driver problem will waste every step that follows.
Fork Two: Is There a Cursor?
The second fork is the cursor. During the black screen, watch for a mouse cursor. If a cursor is visible, the picture is not fully absent — Windows is running, the display output is working, and the desktop shell or a startup program has not finished loading. That points at the desktop shell and startup program layer. If there is no cursor at all, the delay points at the driver or display-output layers instead, because the picture has not reached the point where a cursor can be drawn. This fork splits the field in one observation, and it should be made before anything else is changed: a cursor present and a cursor absent are two different problems, and they must not be mixed. If the cursor is present, press Ctrl+Alt+Del and see whether the security screen appears — if it does, Windows is responsive behind the black screen, and the shell layer is confirmed as the direction. If Task Manager can be opened from there, and the desktop shell process is not running, the evidence is stronger still.
Fork Three: One Display Direct, or More?
The third fork is the display setup. A second display, a docking station, or an adapter can lengthen the time Windows spends detecting displays during loading — each display has to be found, identified, and negotiated with before the picture appears. The comparison is simple: remove the second display, the dock, and the adapter, leave one display connected directly, and boot again. If the picture arrives noticeably sooner, the delay follows the display detection layer. If the delay is unchanged with one display direct, the detection layer is cleared, and the delay sits elsewhere. One caution: this test is about the Windows loading stage, not about the connection itself. A different cable or port can change how quickly a display shakes hands with the machine, and that is a connection matter; if the delay is the same on either connection, the cable is not the cause, and no more time should be spent on it.
Fork Four: Is It the Saved State or the Driver?
The fourth fork is actually two comparisons that answer one question: is the delay in what loads only in normal mode, or in how the machine shuts down? The first comparison is Safe Mode: boot into Safe Mode once and time it. If Safe Mode is fast and normal mode is slow, the delay follows something that only normal mode loads — the full graphics driver, a service, or a startup program. If Safe Mode is slow too, the delay is not in the driver layer, and the investigation moves to the system and disk layer. The second comparison is a full restart against a shut-down-and-power-on: restart the machine once, time the black screen, then shut it down fully, power it on again, and time the black screen again. If the full restart is fast and the shut-down-and-power-on is slow, the delay follows the saved state that Fast Startup restores — the machine is not doing a full restart when it is shut down and powered on, and the saved state it restores is where the delay sits. If both are equally slow, the saved-state layer is cleared. Both comparisons are tests, not repairs, and neither result should be written up as a fix.
The Five Suspicion Layers
A long black screen at boot can be slow at five layers, and they must be kept separate. Changing the driver, the display setup, and the startup setting all at once and finding the boot faster proves nothing about which change did the work, and the delay will return the next time only one of those conditions is present. The layers below run from the driver load to the system underneath it, and each one has its own deciding evidence.
| Layer | What it covers | Deciding evidence |
|---|---|---|
| 1. Driver loading layer | The graphics driver initialising, listing displays, and setting the display mode during Windows loading | The black screen falls between the logo and the login screen; Safe Mode is fast, normal mode is slow |
| 2. Display detection layer | Windows re-detecting displays during loading; a second display, a dock, or an adapter lengthening detection | One display connected directly is fast; two displays or a dock is slow |
| 3. Fast Startup and hybrid shutdown layer | The saved state restored when the machine is powered on after a shut-down, rather than a full restart | A full restart is fast, a shut-down-and-power-on is slow |
| 4. Desktop shell and startup program layer | The desktop shell not loading, or a startup program holding the login up; the black screen appears after login | A cursor is visible; Ctrl+Alt+Del reaches the security screen; Task Manager opens |
| 5. System and disk layer | System files, slow disk reads, or many startup services lengthening the whole load | The whole boot is slow and programs open slowly too; Safe Mode is slow as well |
Layer One: The Driver Loading Layer
The first layer is the graphics driver loading during the Windows loading stage. When Windows loads, the driver has to initialise the card, list the displays connected to it, and set the display mode — and if the driver version does not fit, if leftover files from an old driver interfere, or if the driver is waiting on a device that is slow to answer, the load drags. The signature of this layer is the stage combined with the Safe Mode comparison: the black screen falls between the logo and the login screen, and Safe Mode — which uses a basic display driver instead of the full one — boots noticeably faster. That combination points at something the full driver does that the basic driver does not. Note what this layer does not claim: it does not say the card is faulty. A driver that is slow to load is a driver problem until proven otherwise, and the proof is the comparison testing in the steps below. It also does not say the driver version is bad in general — versions can only be judged by timeline, and the current official release is the only reference that stays valid.
Layer Two: The Display Detection Layer
The second layer is display detection. During Windows loading, the system re-detects the displays: it reads each display's identity, negotiates the mode, and decides what to show where. One display connected directly is a short job. Two displays, a docking station, or an adapter make it a longer one, because each display and each link in the chain has to be found and agreed with before the picture appears. The signature of this layer is the single-display comparison: one display direct is fast, two displays or a dock is slow. If the delay is the same on either connection — the same delay whether the display is connected one way or the other — then the detection layer is cleared, and the delay sits elsewhere. One boundary matters here. A connection that is slow to establish its link is a different problem from a Windows loading delay: if changing the connection makes the picture appear at once, the delay was in the handshake, not in Windows loading, and this guide is not the right one. The test that separates them is exactly the single-display comparison — if one display direct is still slow, the connection is not the cause.
Layer Three: The Fast Startup and Hybrid Shutdown Layer
The third layer is Fast Startup, and it turns on a fact that surprises most owners: shutting down is not the same as restarting. With Fast Startup switched on, a shut-down saves the kernel state to disk, and powering on again restores that saved state instead of starting fresh. A restart, by contrast, is a full restart — nothing is restored. If the saved state carries a problem — a leftover driver state, a driver that did not shut down cleanly — then every power-on after a shut-down has to work through that saved state, and the black screen stretches out. The signature of this layer is the restart comparison: a full restart is fast, a shut-down-and-power-on is slow. That pattern points at the saved state, and it is the only pattern that does. Two cautions apply. First, switching Fast Startup off is a comparison test, not a repair: switching it off changes how the machine shuts down, and it carries its own cost — starting from a full shut-down takes longer, because nothing is restored. Second, this layer can only be tested by comparing the two kinds of boot; testing only shut-down-and-power-on, without a full restart to compare against, proves nothing.
Layer Four: The Desktop Shell and Startup Program Layer
The fourth layer is the desktop shell and the programs that start with it. This layer shows itself after login, not before it: the login screen appears, the password is entered, and then the screen goes black — with a cursor visible. The driver and the displays are already up by this point, so the delay is not in the driver load. What is slow is the desktop shell itself not loading, or a startup program holding the login up while it starts. The signature is the cursor, together with responsiveness: Ctrl+Alt+Del reaches the security screen, Task Manager opens, and the shell process is not running or not responding. That combination points at the shell layer, and it is completely different from the driver layer — the two must not be mixed, because a shell problem investigated as a driver problem will never be found. If there is no cursor at all, this layer is not the one: no cursor means the picture has not reached the point where a cursor can be drawn, and the investigation stays with the driver and display layers.
Layer Five: The System and Disk Layer
The fifth layer is the system underneath: system files, slow disk reads, or many startup services. This layer is considered last, and for a reason. Its symptoms do not appear only as a black screen at boot — a slow disk or a damaged system file would be expected to make the whole boot slow and programs slow to open as well, not only the black-screen stretch. The signature is therefore the company the delay keeps: the whole boot is slow, programs open slowly once inside Windows, and Safe Mode is slow too. A delay that appears only as a black screen, with everything else normal once the desktop arrives, pushes this layer to the back of the queue. When this layer is reached, the work belongs with professional inspection rather than further testing at home, because the checks involved reach into system files and storage that should not be disturbed without knowing what is being looked at.
The Seven Diagnostic Steps
The steps below are comparison tests. Each one changes one variable and records the result. Changing two things at once and finding the boot faster proves nothing about which change mattered, and the delay will return the next time only one of those conditions is present. Write down each result before moving on.
Step 1: Record the Baseline
Before anything is changed, record the baseline. Which stage the black screen falls in — the logo, the spinning dots, before the login screen, or after login. Whether it happens on every boot or only sometimes. How long the black screen lasts, timed with a watch, not guessed from feeling — feeling stretches time, and a delay that feels like a minute is often far shorter. Whether there is a cursor during the black screen. Whether the drive light flickers, whether there is any sound, and whether the Caps Lock or Num Lock light answers when pressed. And whether anything changed recently — a driver update, a Windows update, a new display, a new dock. Without this record, later comparisons have nothing to compare against, and a delay that changes form halfway through the investigation will look like a new problem when it is the same one wearing a different shape. Also note whether an update was still installing between restarts: a machine that is black-screened while an update is still finishing its install between restarts is not showing a fault at all, and that possibility has to be ruled out before anything else is tested.
Step 2: The Stage-Location Comparison
Use the stage table from the boot-stages section to locate the delay. Watch a boot from the moment the power button is pressed and write down the times: when the logo appears, when the logo disappears, when the login screen or desktop appears. If the logo lingers, the delay is in the firmware stage, and this guide does not apply — the firmware and initialisation diagnosis is the right path. If the logo passes quickly and the wait falls between the logo and the login screen, the delay is in the Windows loading stage, and this guide applies. If the login screen arrives on time and the black screen only comes after login, the delay is in the desktop shell stage, and the cursor test in step three is the way in. Getting the stage wrong sends everything after it in the wrong direction, so this step should not be skipped or rushed. If the stage cannot be located — the machine shows nothing at all, not even a logo — stop: a machine with no logo and no picture is not a loading-delay problem, and it needs inspection rather than further testing.
Step 3: The Cursor Comparison
During the black screen, watch for a mouse cursor. If a cursor is visible, work the desktop shell layer: press Ctrl+Alt+Del and see whether the security screen appears, open Task Manager from there, and check whether the desktop shell process is running. If the security screen appears and Task Manager opens, Windows is responsive behind the black screen, and the delay is in the shell or a startup program — not in the driver load. If no cursor is visible at all, work the driver and display-output layers instead: no cursor means the picture has not reached the point where a cursor can be drawn, and the shell test does not apply. This step splits the field in one observation, and it should be made one at a time, without jumping ahead: a cursor present and a cursor absent are two different problems, and mixing them throws away the most specific evidence available. Write down which one was seen, because the rest of the steps depend on it.
Step 4: The Single-Display Direct Comparison
Remove the second display, the docking station, and any adapter, and leave one display connected directly to the machine. Boot again and time the black screen with a watch, exactly as in step one. If the picture arrives noticeably sooner, the delay follows the display detection layer — the extra display, the dock, or the adapter was lengthening detection. If the delay is unchanged with one display direct, the detection layer is cleared: the delay does not follow the display setup, and the investigation moves on. This step uses the same logic as the connection comparison in the neighbouring guides, but the test target is different: there the question is whether the link itself is established, here the question is whether the Windows loading stage is slow. Do not change the cable and the display setup at the same time — if both are changed and the boot is faster, there is no way to tell which change mattered. One variable at a time, and the result written down before the next change.
Step 5: The Safe Mode Comparison
Boot into Safe Mode once and time it. Safe Mode loads only the most basic drivers, and it uses a basic display driver instead of the full graphics driver. If Safe Mode is fast and normal mode is slow, the delay follows something that only normal mode loads — the full driver, a service, or a startup program — and the investigation stays in the driver and startup layers. If Safe Mode is slow too, the delay is not in the driver layer, and the investigation moves to the system and disk layer. Safe Mode being fast is a comparison test, not a repair: the machine is not fixed because it boots quickly in Safe Mode, and the delay will return the moment normal mode loads the full driver again. Record both times — the Safe Mode time and the normal-mode time — because the comparison between the two is the result, and a single time on its own says nothing.
Step 6: The Fast Startup Comparison
Do one full restart, and time the black screen. Then shut the machine down fully, power it on again, and time the black screen again. Compare the two times. If the full restart is fast and the shut-down-and-power-on is slow, the delay follows the saved state that Fast Startup restores — the machine is not doing a full restart when it is shut down and powered on, and the saved state it restores is where the delay sits. If both are equally slow, the saved-state layer is cleared. Switching Fast Startup off is only a comparison test for this step: it changes how the machine shuts down, and it carries its own cost, because starting from a full shut-down takes longer when nothing is restored. Do not present switching it off as a repair, and do not leave it off permanently on the strength of one comparison — the result of the test is the evidence, and what to do with the evidence is a separate decision. Write down both times, and which kind of boot each one was, because without the labels the numbers cannot be read.
Step 7: The Driver-Reset Comparison and Preparing for Inspection
Press Win+Ctrl+Shift+B once during the black screen. This resets the display driver, and the picture may return at once. If it does, that is evidence the delay sits in the driver layer — the reset cleared the stall, and the driver was the thing holding the picture up. If nothing happens, the delay is not in that layer, and the investigation moves on. This is a comparison test, not a repair: the picture returning after the keypress proves where the delay lives, and the delay will be back on the next boot, because nothing about the driver has changed. Pressing the keys again and again adds nothing — one press, one result, written down. Then assemble the conclusion in three sentences: what the symptom is, which variable made the symptom appear or disappear, and which possibilities are still not ruled out. Write it down with the full record: the stage the black screen falls in, how long it lasts, whether there is a cursor, the single-display result, the Safe Mode result, the Fast Startup comparison result, and the driver-reset result. Bring that record to inspection. A record that says "logo passes quickly, black screen before login, no cursor, one display direct unchanged, Safe Mode fast, full restart fast and shut-down-and-power-on slow" is worth far more than a record that says "it takes ages to boot."
Six Misconceptions That Mislead This Diagnosis
Misconception 1: A Long Black Screen at Boot Means the Card Is Failing
A picture that arrives late and is then perfect, every time, does not look like a failing card. A failing card produces artefacts, crashes, or no picture at all — not a delay that ends in a normal desktop. A delay can sit in the driver load, the display detection, the saved state, the desktop shell, or the disk, and each of those is a different layer with a different test. Jumping to a dead card skips every test that could prove otherwise, and it leads to replacing a part that was never at fault.
Misconception 2: There Is a Universal Waiting Time That Defines a Fault
There is no number of seconds that separates a normal boot from a faulty one, and no such number should be written down as a standard. How long a boot takes depends on the hardware, the storage, the number of displays, and what is installed — a machine with a slow drive and two displays will always take longer than a machine with a fast drive and one display, and both can be healthy. One published guide suggests waiting a fixed period before assuming a fault; another treats a continuing black screen as a fault to work on. Both are talking about different things — the first about a machine that is still loading, the second about a machine that has stopped — and neither gives a universal standard. The judgement this guide uses is whether the machine is still working while the screen is black — the drive light, the sounds, the Caps Lock light — together with which stage the black screen falls in. Time the delay with a watch, but judge the machine by what it is doing during the delay, not by the number alone.
Misconception 3: Pressing Win+Ctrl+Shift+B and Seeing the Picture Means It Is Fixed
Pressing the keys only resets the display driver. If the picture returns at once, that proves the delay sits in the driver layer — and that is valuable evidence. It does not repair anything, because nothing about the driver has changed, and the delay will be back on the next boot. Treating a keypress that brings the picture back as a fix leaves the machine in a state where the same delay returns every morning, and the driver layer is never actually investigated.
Misconception 4: Switching Fast Startup Off Means It Is Fixed
Switching Fast Startup off is a comparison test. It proves the delay follows the saved state that a shut-down restores, and that is valuable evidence. It is not a repair, and it carries its own cost: starting from a full shut-down takes longer, because nothing is restored. A machine with Fast Startup switched off and the underlying saved-state problem still present is not a fixed machine — it is a machine whose delay has been avoided by changing how it shuts down, and the evidence should be recorded as a comparison result, not reported as a fix.
Misconception 5: Cutting the Power and Restarting at Once Is the Right Response
Cutting the power during a black screen is the wrong response, and it can make things worse. While the screen is black, the machine may be in the middle of loading — or, after a hardware change, in the middle of a first-time initialisation — and cutting the power interrupts that work. The correct response is to wait, watch the drive light and the Caps Lock light, time the delay with a watch, and write the result down. A delay that is timed and recorded is evidence. A delay that is interrupted by a power cut is evidence destroyed — and a machine that is cut off repeatedly during loading can develop a startup problem it did not have before.
Misconception 6: Changing the Cable or the Port Will Always Speed It Up
A cable or a port only affects the display handshake — the moment the display and the machine agree on a connection. It does not affect the Windows loading stage, which is where this guide's delay sits. If the delay is the same on either connection, the cable is not the cause, and no more time should be spent on it. Changing cables in circles, without the single-display comparison to show whether the display setup matters at all, wastes the investigation on a layer that has already been cleared.
Boot Speed Comparison Table
The table below puts the comparison results side by side. Each comparison changes one variable at a time; a different result points in a different direction.
| Comparison | Result A | Result B | What to record |
|---|---|---|---|
| One display direct vs one display plus dock | One display fast, with dock slow | Both equally slow | Black-screen time, number of displays, connection method |
| Safe Mode vs normal mode | Safe Mode fast, normal mode slow | Both equally slow | Both black-screen times, which mode |
| Full restart vs shut-down-and-power-on | Restart fast, shut-down-and-power-on slow | Both equally slow | Both black-screen times, kind of boot |
| Cursor present vs no cursor | Cursor present, Ctrl+Alt+Del reaches the security screen | No cursor, no response at all | Whether there is a cursor, whether the security screen appears |
| Caps Lock light test | Light answers, drive light flickering | Light does not answer, drive light completely still | Light response, drive light state |
Each comparison has to be timed separately and recorded separately. Saying from memory that the boot felt a little faster has no diagnostic value — time both runs with a watch and write both times down before comparing them.
What the Sources Disagree About
The published sources do not agree with each other, and both sides are given below.
First, wait or act now. One guide suggests waiting a fixed period before assuming a fault; other guides treat a continuing black screen as a fault to work on at once. The two sides are not talking about the same thing: the first is talking about a machine that is still loading, the second about a machine that has stopped. This guide follows the position that the decision should rest on the survival signs — the drive light, the sounds, the Caps Lock light — together with the stage, rather than on any fixed waiting time. No universal number is given here, and none should be read into the timings recorded in the steps above.
Second, the driver-reset keypress. Some guides describe pressing Win+Ctrl+Shift+B as a quick repair that clears a black screen in seconds. This site's position is that it is a comparison test: the picture returning proves the delay sits in the driver layer, and it is not a repair. This guide follows that position throughout.
Third, hardware or driver. One guide says a black screen before the Windows logo appears is a hardware or firmware problem; another says a black screen after an update is an incompatible driver. Both statements are correct, but they are about different stages — and that is exactly why this guide's first fork is the stage. Neither statement should be read as a general conclusion about all black screens.
Fourth, an update in progress. One guide notes that a black screen during an upgrade is often the install still running between restarts, not a fault; other guides treat a black screen after an update as a regression. This guide follows the position that an unfinished update should be ruled out first — a machine that is still installing between restarts is not showing a fault at all.
Fifth, there is a disagreement about how to describe the comparison steps. Third-party tutorials often describe rolling back a driver, switching Fast Startup off, and pressing the driver-reset keys as repairs. This site's position is that all of them are comparison tests. They produce evidence about which layer the delay belongs to, and they are not repairs. This guide follows that position throughout: no comparison step is presented as a fix.
When to Stop Testing
Boot-delay testing carries risk, and the testing should stop before the risk outweighs the evidence. Do not cut the power during a black screen to hurry the machine along: interrupting a load in progress can damage the startup, and repeated power cuts add stress without adding information after the first few results. Stop immediately if there is any smell of burning, any unusual noise, or any visible damage. Do not disable any protection to run a test. A test that has already given a clear result does not need to be run again, and a test that leaves the machine unresponsive is a result in itself — record it and move to the next comparison instead of running the same test again.
Do not rebuild the startup records from the recovery-environment command line. That work is for inspection, not for testing at home, and this guide gives no instructions for it. If the machine shows no logo at all, if Safe Mode cannot be entered, or if the recovery environment cannot be reached, stop testing and bring the record so far to inspection. Before entering the recovery environment at all, find the BitLocker recovery key if the machine uses BitLocker — entering recovery without it can lock the machine out. The record is already useful at that point — it says which stage the delay falls in and which layers have been cleared — and further testing on a machine that cannot reach Safe Mode risks more than it can reveal.
What to Bring for Inspection
If the comparisons point toward a hardware layer or a system and disk layer, or if they point nowhere conclusive, the next step is a professional inspection. Bring the full record: the stage the black screen falls in, how long it lasts on each kind of boot, whether there is a cursor, the drive light and Caps Lock light results, the single-display comparison result, the Safe Mode result, the Fast Startup comparison result, and the driver-reset result. The three-sentence conclusion from step seven is the summary of that record.
Inspection and repair pricing follows the site's published three-tier scale of HK$400 to HK$2,800, with the actual quote given after inspection. No price in this guide should be read as a quote for a particular fault, and no fee is stated here for any specific repair.
The workshop is at Room 1209, Dali Plaza, Shek Mun. The telephone number is 2186 8010, and the WhatsApp number is 6558 6806. There is no Mong Kok shop, and there is no on-site service — inspection is carried out at the workshop.
Frequently Asked Questions
My screen is black for a long time on every boot, but the picture always comes back. Is my graphics card failing?
Not necessarily. A picture that arrives late and is then perfect, every time, does not look like a failing card — a failing card produces artefacts, crashes, or no picture at all. The delay points at something taking too long during loading: the driver, the display detection, the saved state, the desktop shell, or the disk. Run the stage test and the Safe Mode comparison first: if the logo passes quickly and Safe Mode is fast, the delay follows something that only normal mode loads.
How long a black screen counts as a fault?
There is no universal number. How long a boot takes depends on the hardware, the storage, the number of displays, and what is installed, so a fixed waiting time cannot separate a normal boot from a faulty one. Judge the machine by whether it is still working while the screen is black — the drive light flickering, sounds playing, the Caps Lock light answering — together with which stage the black screen falls in. Time the delay with a watch and write it down, but do not treat the number alone as the verdict.
The black screen has a mouse cursor. What does that mean?
It means Windows is running and the display output is working, and the desktop shell or a startup program has not finished loading. Press Ctrl+Alt+Del and see whether the security screen appears — if it does, Windows is responsive behind the black screen. Open Task Manager from there and check whether the desktop shell process is running. A cursor present points at the desktop shell layer, which is completely different from the driver layer.
The black screen has no cursor at all. What does that mean?
It means the picture has not reached the point where a cursor can be drawn, and the delay points at the driver or display-output layers instead. Check the survival signs first: the drive light, any sound, and whether the Caps Lock or Num Lock light answers. Then run the stage test and the Safe Mode comparison — a black screen with no cursor, between the logo and the login screen, that is fast in Safe Mode, points at the driver loading layer.
It is fast on a full restart but slow after shut down and power on. Why?
Because shutting down is not the same as restarting when Fast Startup is switched on. A shut-down saves the kernel state, and powering on restores that saved state instead of starting fresh, while a restart is a full restart with nothing restored. If the saved state carries a problem, every power-on after a shut-down has to work through it, and the black screen stretches out. That pattern points at the Fast Startup and hybrid shutdown layer — and switching Fast Startup off is only a comparison test, not a repair.
Safe Mode boots quickly but normal mode is slow. What does that show?
It shows the delay follows something that only normal mode loads — the full graphics driver, a service, or a startup program. Safe Mode uses a basic display driver and loads only the most basic set of drivers, so a machine that is fast in Safe Mode and slow in normal mode has narrowed the field to the normal-mode layers. It does not mean the machine is fixed, and the delay will return the moment normal mode loads the full driver again.
I pressed Win+Ctrl+Shift+B and the picture came back at once. Is it fixed?
No. Pressing the keys only resets the display driver, and the picture returning proves the delay sits in the driver layer — that is valuable evidence, but it is not a repair. Nothing about the driver has changed, and the delay will be back on the next boot. Write the result down as a comparison result and continue the investigation from the driver layer, rather than treating the keypress as the end of the problem.
Will changing the cable or switching to a different port speed it up?
Probably not, if the delay is in the Windows loading stage. A cable or a port only affects the display handshake, not the loading stage. Run the single-display comparison first: remove the second display, the dock, and the adapter, leave one display connected directly, and boot again. If the delay is unchanged with one display direct, the cable is not the cause, and no more time should be spent on it.
Should I cut the power and restart when the screen stays black?
No. While the screen is black, the machine may still be loading, and cutting the power interrupts that work — repeated power cuts during loading can damage the startup. Wait, watch the drive light and the Caps Lock light, time the delay with a watch, and write the result down. Only if the machine shows no signs of life at all — no drive light, no sound, no Caps Lock response — is the picture different, and then the next step is inspection, not another power cut.
What should I record before bringing the machine in for inspection?
Record the stage the black screen falls in, how long it lasts on each kind of boot, whether there is a cursor, the drive light and Caps Lock light results, the single-display comparison result, the Safe Mode result, the Fast Startup comparison result, and the driver-reset result. Then put it together as three sentences: what the symptom is, which variable made the symptom appear or disappear, and which possibilities are still not ruled out.
Sources
- SolveTechToday, "Fix Windows 11 Black Screen" — https://www.solvetechtoday.com/windows-11-black-screen/
- W3Tutorials, "Fix Black Screen Without Cursor on Windows 10 and 11" — https://www.w3tutorials.net/blog/fix-black-screen-without-cursor/
- TechDows, "Black screen problems in Windows 11; stuck on black screen [Fix]" — https://techdows.com/black-screen-problems-in-windows-11-stuck-on-black-screen-fix.html
- Mundobytes, "Black Screen in Windows 11: Detailed Causes and Solutions" — https://mundobytes.com/en/black-screen-when-starting-Windows-11/
- Microsoft Learn Q&A, "How to fix automatic repair on loop and also blue screen in window 11" — https://learn.microsoft.com/en-us/answers/questions/302c3079-431a-488b-9b77-5554dfc66cdc/how-to-fix-automatic-repair-on-loop-and-also-blue