GPU Driver Installer Stuck With No Error Message? Installer Stall, Lock & Safe-Interrupt Diagnosis Guide

Key Takeaway
A driver installer whose progress bar has stopped is not necessarily dead: the bar can sit still while the installer is writing files in the background. Task Manager shows whether the installer process is still using processor and disk activity. Judge by that activity, not by the clock, and end a stuck installer through Task Manager, never by cutting power.
What This Problem Is — and What It Is Not
A graphics driver installer has been opened — the official installer from NVIDIA, AMD, or Intel, or an update started inside NVIDIA App or AMD Software — and its progress bar has stopped at one percentage. It might be 47%, or 99%, or a screen that says "Preparing to install" with no percentage at all. It has been like that for a long time, with no progress, but there is no error message, no rollback to the old driver, and no black screen. The installer window is still there. Pressing Cancel may do nothing at all.
That scene is the whole problem this guide covers, and its shape is the most important piece of evidence in the diagnosis. The installer opened, it started, and progress stopped — with no message explaining why. It is not an installer that shows an error message and rolls back to the old driver. That is a driver installation failure, and it belongs to the guide on installation failure. It is not an installer that goes black during installation. That is an installation black screen problem, and it belongs to its own guide. It is not a machine that stays black after the driver was installed and the machine restarted. That is a post-installation black screen rescue problem. And it is not a driver version that Windows Update replaced afterwards. That belongs to the guide on Windows Update changing the driver. None of those is this guide.
Four conditions must all be true before the steps below apply:
- A graphics driver installer was started — from the official standalone package, or from inside NVIDIA App or AMD Software — and its progress bar has stopped at one percentage, or at a named stage such as "Preparing to install", and has not advanced.
- There is no error message, no rollback, and no black screen. The installer window is still visible, and the desktop is still visible behind it.
- The machine boots into Windows and shows a desktop normally. If there is no display at all, the problem is a display problem, not an installer problem, and a different guide applies.
- The progress bar is stopped, not merely slow. If the percentage is still changing, or the installer is still showing signs of work, the installer is still working through its stages, and the correct action is to let it finish, dealt with in Step 3.
The counter-intuitive core of this guide is that a stopped progress bar does not mean the installation is dead. An installer can be doing real work in the background — writing files, registering components, waiting for another step to complete — while its progress bar does not update. Or it can genuinely be stuck — waiting for a response that will never come, held by another program, or unable to write a file. The progress bar itself cannot tell those two apart, because it looks the same in both cases. The evidence that separates them lives elsewhere — in Task Manager, in the installer process's processor and disk activity. The five suspicion layers below are the five things that can hold an installer still, and the seven steps are the order in which to test them.
The Progress Bar Is Not the Evidence
Before changing anything, it is worth understanding what a progress bar actually is. A progress bar is a report from the installer about which stage it believes it is in, and how far through that stage it believes it has gone. It is not a live measurement of work being done. Some stages report their progress in fine detail, and their bars move smoothly. Other stages do a large amount of work and report nothing until the stage is finished, and their bars sit still for the whole stage. A bar that sits still at 99% can mean the installer is writing the last files, or registering the last components, or waiting for a restart — all of which are real work, reported as stillness.
That is why the first habit in this diagnosis is to look away from the bar. Write down the percentage it shows, the stage name it shows, how the installation was started, and whether this is a first installation or an update of an older version. Then open Task Manager and look at the installer process. The bar is a starting point for the record, not the verdict. The verdict comes from whether the process is moving — processor activity, disk activity, and whether the process responds — and that verdict is Step 2.
One more point about waiting deserves stating plainly. There is no universal number of minutes that defines when an installer has become stuck, and NVIDIA publishes no universal timeout for this screen. Different installer packages and different machines take very different amounts of time, and any single figure would be wrong for most readers. A widely quoted fifteen-minute figure that circulates online comes from a different situation entirely — the first boot after a fresh Windows 10 installation — and it does not apply to a driver installer that has stopped mid-installation. The judgement in this guide is movement, not minutes: a process whose processor and disk are still active is a process that is still working, however long it has taken, and a process whose resources have all been still is a process that has stopped, and waiting longer will not change that.
The Five Suspicion Layers
An installer stall can come from five layers, and they must be kept separate. Mixing them together is how a Windows Update lock gets treated by downloading a new installer package again and again, or a damaged package gets treated by turning the antivirus off and leaving it off, and how the real cause survives because the wrong layer was treated. The five layers below are ordered the way the diagnosis should work through them, and each one has its own deciding test.
Layer One: The Stall Layer — "Stopped" Does Not Mean "Dead"
The first layer is the stall itself, and it is the layer most often misunderstood. A progress bar that does not move can describe two completely different states. In the first, the installer is still working in the background — writing files, registering components, waiting for another step to complete — and only the progress bar has not updated. In the second, the installer has genuinely stopped: it is waiting for a response that will never come, it is held by another program, or it cannot write a file. The outward picture is identical. The progress bar is not evidence, and the length of the wait is not evidence either. The installer process's processor and disk activity is the evidence.
The deciding evidence for this layer is the installer process in Task Manager. Sustained processor or disk activity by the installer process means the installer is still working, and the correct action is to let it finish. Processor and disk activity both close to zero, sustained over time, together with a process that shows "Not responding", means the installer has genuinely stopped. That distinction is the fork the rest of the diagnosis follows, and it is the reason Step 2 comes before any other test. Without it, every later step is a guess: a lock cannot be distinguished from a damaged package, and an antivirus interception cannot be distinguished from an installer that was simply still working, because all of them present as the same still bar.
Layer Two: The Lock Layer — Another Installation or Update Is Holding the Installer
The second layer is the lock. Windows allows only one installer to use the Windows Installer service at a time. If Windows Update is installing updates in the background, or another program is installing or updating, or a previous installation finished without the restart it was waiting for, the new driver installer can stop at one step while it waits for the lock to be released. The installer is not broken; it is queuing. But it is queuing for something that may take a long time, or that may never finish on its own, and the installer itself gives no message to say so.
The signature of this layer is where the installer stops. It tends to stop at "Preparing to install", or very early in the process, before much has been written — and the same stillness appears in other installation actions on the system, because the lock is system-wide, not specific to the driver. The deciding evidence is what else is running: Windows Update installing in the background, another installer process such as msiexec running at the same time, or a pending restart from an earlier update. Published guidance on this problem agrees on the point: an overlapping Windows Update installation is a recognised cause of driver installation failure, and the first thing to check when an NVIDIA App update stalls at "Preparing to install" is what else is installing. This layer is checked in Step 4, and it deliberately comes after the process-activity test, because a lock can only be the cause once the installer has been shown to be genuinely stopped rather than merely still working.
Layer Three: The Interception Layer — Antivirus or System Protection Is Holding a File
The third layer is interception. Antivirus real-time protection, Windows SmartScreen, or a system optimisation tool can hold a file for checking at the moment the installer tries to write a driver file, or can treat one step of the installation as suspicious behaviour and block it. The installer, which expected the write to complete, waits. Nothing is written, nothing is reported, and the progress bar sits still. The installer is not broken, and the file is not necessarily damaged; a protection layer has simply stepped between the installer and the disk.
The signature of this layer is also a stage: the installer tends to stop while writing files or registering components, rather than at the very start. The deciding test is a diagnostic comparison — whether the installation proceeds when the antivirus real-time protection is briefly turned off. That comparison is a test, not a solution: once the result is known, the protection must be switched straight back on. Turning antivirus off for a longer period is not a fix, and it must never be presented as one. A machine left unprotected while a driver is installed, and then left unprotected afterwards, has traded one problem for a worse one. The comparison belongs in Step 6, alongside the other single-variable changes, and it is never the first step, because an interception can only be blamed once the installer has been shown to be genuinely stopped and the lock layer has been ruled out.
Layer Four: The File Layer — A Damaged or Incomplete Installer Package
The fourth layer is the package itself. An installer package that was interrupted during download, or downloaded incompletely, or damaged in transit, can stop the installer at one percentage while it tries to unpack, or can leave it waiting silently at a verification stage. The installer expected a complete file and received a partial one, and it has no error message prepared for that situation, so it simply stops. The package is the variable here, not the machine: the same machine, with a complete package, installs normally.
The signature of this layer is repetition. The installer stops at the same percentage every time, with the same package, and a freshly downloaded package from a different source gets past that point. The installation path is a variable too: updating through NVIDIA App or AMD Software is a different route from downloading the standalone package from the manufacturer's website, and the two routes download, verify, and unpack differently. A stall that follows one route and not the other points at the route or the package, not at the machine. This layer is tested in Step 6, by downloading a fresh standalone package and running it with administrator rights, changing one thing at a time, and writing down the result of each attempt. Retrying the same damaged file again and again is not a test; it is the same test repeated, and it will give the same answer every time.
Layer Five: The Stage Layer — Where It Stops Points at Which Layer
The fifth layer is the stage itself, and it is the layer that turns the percentage into a useful starting point. A driver installation passes through several stages: downloading files, unpacking, removing the old driver, installing the new driver files and services, registering system components, and then asking for a restart. Where the installer stops points, roughly, at which layer to suspect — but only roughly, and only together with the process activity from Step 2. A stop near 0% usually points at a download or launch problem. A stop in the middle usually points at a file-writing or registration problem. A stop near 99% is often the actual installation phase, where a file is being written or a restart is pending. Published guidance on frozen NVIDIA driver updates describes the same pattern: a freeze at 0% usually points to a download or launch problem, while 99% is often the installation phase where a file is being written or a reboot is pending.
The percentage is a starting point, not a diagnosis. Two installers can stop at the same percentage for different reasons, and the same cause can stop two installers at different percentages, because the stages do not line up exactly between installer versions and between manufacturers. The percentage must always be read together with the process activity, the stage name, and the installation route, and it must never be used on its own to declare what is wrong. A note that says "stopped at 47%, installer process idle, standalone package, Windows Update not running" is a diagnosis in progress. A note that says "stopped at 47%" is a starting point with no direction.
| Layer | What can be wrong | Deciding evidence | What resolves it |
|---|---|---|---|
| 1. Stall | The installer is still working, or it has genuinely stopped | Installer process processor and disk activity in Task Manager | Letting a working installer finish; ending a stopped one safely |
| 2. Lock | Windows Update, another installer, or a pending restart holds the installer | Windows Update running; another installer process such as msiexec active | Letting the other installation finish or pausing it |
| 3. Interception | Antivirus or system protection holds a file during writing | The installation proceeds only when real-time protection is briefly off for comparison | Identifying the interception; protection switched straight back on |
| 4. File | The installer package is damaged or incomplete | The same percentage every time; a fresh package gets past it | A freshly downloaded standalone package from the official site |
| 5. Stage | The percentage points at a stage, but only roughly | The percentage plus the stage name, read with process activity | Using the stage as a starting point, never as a verdict on its own |
The Seven Diagnostic Steps
The seven steps below are ordered so that each one tests one layer, and so that no step destroys the evidence a later step needs. Work through them in order, one variable at a time, and write down the result of each step before moving on. Changing two things at once and seeing the installation succeed leaves the reader not knowing which change mattered — and not knowing what to do when the problem returns.
Step 1: Write Down Where It Stopped — Percentage, Stage, Waiting Time, and Route
Write down the percentage the progress bar shows, the stage name it shows — downloading, preparing to install, installing, or waiting for a restart — how long it has been stopped, and how the installation was started: through NVIDIA App or AMD Software, or from a standalone package downloaded from the manufacturer's website. Note also whether this is a first installation or an update of an older version, and whether it has stopped at the same percentage before.
This step proves that the problem has been narrowed to an installer stall at a named stage and percentage, and it records the only direct evidence of which stage that is. It proves nothing about whether the installer is still working — that is what Step 2 is for. But without the percentage, the stage, and the route, nothing else can be checked against them. A note that says "stopped at 47%, 'Installing', standalone package, second time at the same percentage" is a diagnosis in progress. A note that says "it got stuck" is a starting point with no direction. Do not judge by impression; write the numbers down.
Step 2: Look at Task Manager — Is the Installer Working or Has It Stopped?
Open Task Manager and find the installer process — the NVIDIA installer process, or the AMD installer process — and look at its processor usage and its disk usage. This is the most important step in the whole guide, and it must not be skipped, because it is the step that separates an installer that is working from an installer that has stopped, and everything after it depends on the answer.
If the processor or the disk shows sustained activity, the installer is still working — writing files or registering components — and it is not dead, however still the progress bar looks. If the processor and the disk are both close to zero, and the process shows "Not responding", the installer has genuinely stopped. That distinction is the fork the rest of the diagnosis follows. Do not judge by the clock. Judge by movement: the percentage changing, or the processor and the disk showing activity. An installer that is still working should be left alone. An installer that has stopped is the one that needs the steps below. No fixed waiting time can be given here, because the time an installation takes varies so widely between packages and machines that any single figure would be wrong for most readers, and NVIDIA publishes no universal timeout for this screen.
Step 3: Give a Working Installer a Fair Window — Only When the Process Is Still Moving
If the percentage is moving, or the processor and the disk show activity, let the installer finish. Do not cancel the installation partway through, do not force the machine off, and do not start a second installer while the first is running. Only when the process has completely stopped moving — processor and disk both still, over a sustained period — should the diagnosis move on to the next step.
This step follows the same principle as the loading screen guide's rule for a game whose progress bar has stopped: a bar that is not moving, while the processor and the disk are moving, is a process that is working, and the definition of a stopped process is no response plus all resources still. The judgement is movement, not minutes. An installer whose percentage is still changing is an installer that is still working, however long it has taken. An installer whose percentage, processor, and disk have all been still is an installer that has stopped, and waiting longer will not change that.
Step 4: Check for a Lock — Windows Update and Another Installer
Look at whether Windows Update is installing updates in the background, in Settings under Windows Update. Look at whether another installer process is running — an msiexec process, or another program's installer. Look at whether the system is waiting for a restart from an earlier update that was never completed. If Windows Update is in progress, let it finish, or pause it, and do not run the driver installation at the same time.
This step comes after Step 2 has confirmed that the installer process is genuinely stopped, and it must not be used as the opening move. Checking for a lock before knowing whether the installer is working wastes the test: a working installer does not need a lock to be found, and a lock found while the installer was still working proves nothing. A lock and a damaged package can also exist at the same time, and they must be confirmed separately. Each possibility gets its own check, so that when the installation finally proceeds, the change that released it is known.
Step 5: Interrupt Safely — End the Installer Through Task Manager, Never with the Power Button
Once the installer process has been confirmed as genuinely stopped, end the installer process through Task Manager. Do not press the power button to force the machine off. Forcing the machine off while an installation is in progress can leave the driver half-written, and a half-written driver is a real black screen fault — the kind of fault that the installation black screen guide warns about in its own terms. Ending the process through Task Manager stops the installer; forcing the machine off stops the whole machine mid-write, and the two are not the same action.
After ending the process, confirm that the old driver is still working normally: the picture is normal, and the graphics card appears normally in Device Manager. Write down the percentage and the stage at which the installation was interrupted. That record is part of the diagnosis, and it is what the next attempt will be compared against. If the picture is not normal, or the graphics card does not appear normally, do not start another installation immediately — that is a different problem, and it needs to be dealt with before any retry.
Step 6: Retry by a Different Route — Standalone Package, Administrator Rights, and Background Interference Removed
Download a fresh standalone installer package from the manufacturer's official website. Do not reuse the previous file, which is suspected of being damaged or incomplete. Run the installer with administrator rights. Before installing, close unnecessary background programs — and, as a diagnostic comparison only, the antivirus real-time protection may be briefly turned off to test whether it was intercepting the installation. Once the result is known, switch the protection straight back on, whether the test succeeded or not. Change one thing at a time, and write down the result of each attempt.
If the fresh standalone package gets past the point where the old one stopped, the cause was the package or the route, and the diagnosis ends here: note which change made the difference, so the same pitfall can be avoided at the next update. If the fresh package stops at exactly the same percentage and stage, the cause is not the package, and the search moves on to Step 7. A restart of Windows before retrying is a reasonable step at this point in the sequence — after the process activity has been checked and the installer safely ended — but it is not the first step, and it was never a substitute for Step 2. Published guidance differs on the order of these methods, with some sources recommending a restart first and others recommending cancelling and changing package first; the order in this guide is deliberate, because the process-activity test must come before any retry, or the retry is a guess.
Step 7: Decide — and Record What Happened
The decision follows from the steps, and there are three directions.
If the installation completed after changing route, the record should note which change made the difference — the fresh package, the administrator rights, or the background program that was closed — so the same pitfall can be avoided at the next update.
If repeated retries still stop at the same percentage and stage, bring the machine in with the complete record: the percentage and stage where it stopped, the process activity readings from Task Manager, the installation route, the Windows Update status, and the changes already tried. Inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. There is no home-visit service and no Mong Kok shop; inspection is carried out in the shop.
If the installer stops the same way for several different programs, not only for the driver, the suspicion moves to damaged system files, and the next step is a system file check — not repeated driver reinstalls. Repeating the same driver installation against a system-level fault will give the same answer every time, and it wastes the evidence that the pattern itself provides. A clean-removal tool is a last resort, considered only after the different-route retry has failed; it is never a first step, because it destroys the old settings and installation state that the comparison depends on.
| Step | What to do | What it proves | What it does not prove |
|---|---|---|---|
| 1. Write down where it stopped | Percentage, stage, waiting time, route, first install or update | Which stage and percentage the installer stopped at | Whether the installer is still working |
| 2. Check Task Manager | Installer process processor and disk usage | Whether the installer is working or has stopped | Which layer is at fault, on its own |
| 3. Give a working installer a fair window | Let a moving installer finish; do not cancel, force off, or start a second installer | Whether the stall clears on its own | Anything, if nothing is moving |
| 4. Check for a lock | Windows Update status, another installer or msiexec process, pending restart | Whether another installation holds the lock | Anything about the package |
| 5. Interrupt safely | End the installer process through Task Manager; confirm the old driver still works | That the installer was stopped without a half-written driver | Anything about the cause |
| 6. Retry by a different route | Fresh standalone package, administrator rights, background programs closed; one change at a time | Whether the package, the route, or an interception was the cause | Anything, if it stops at the same point again |
| 7. Decide | Record the change that worked, or bring the record in, or check system files | Which direction follows from the evidence | Anything beyond the test that was actually run |
Six Common Misconceptions
Misconception 1: A stopped progress bar means the installation is dead
No. A progress bar that is not moving is not the same as an installer that has stopped. While the installer writes files or registers components, the bar may sit still and the screen may not change. A stopped installer is defined by the process not responding and all resources sitting still — processor and disk close to zero — not by the picture being still. The screen cannot tell you which one it is. Task Manager can.
Misconception 2: There is a universal number of minutes to wait
No. NVIDIA publishes no universal timeout for an installer screen, and different installer packages and different machines take very different amounts of time. The judgement must be made from resource activity, not from the clock. An installer whose processor and disk are still active is an installer that is still working, however long it has taken. An installer whose resources have all been still is an installer that has stopped, and the length of the wait is not the evidence — the stillness is.
Misconception 3: Forcing the machine off with the power button is the fastest fix
No. Forcing the machine off while an installation is in progress can leave the driver half-written, and a half-written driver is a real black screen fault. The correct action is to end the installer process through Task Manager, confirm that the old driver is still working normally, and only then try again. The power button is not a shortcut around a stuck installer; it is a way of turning a stuck installer into a damaged driver.
Misconception 4: Retrying the same installer package will eventually work
No. When a package is damaged or downloaded incompletely, retrying the same file will stop at the same percentage every time, because the file itself has not changed. The test is a freshly downloaded standalone package from the official website, or a different installation route — not the same file run again. A repeated failure at the same percentage is itself evidence, and it points at the package.
Misconception 5: Turning the antivirus off will fix every installation problem
No. Turning antivirus off is a diagnostic comparison: it shows whether the antivirus was intercepting the installation, and once the result is known, the protection must be switched straight back on. Leaving antivirus off for a longer period is not a fix, and it must never be presented as one. Most installer stalls have nothing to do with antivirus at all, and a machine left unprotected has traded one problem for a worse one.
Misconception 6: A clean-removal tool should be used as soon as anything goes wrong
No. A clean-removal tool is an advanced step, kept for after the different-route retry has failed. Using it first destroys the old settings and installation state that the comparison depends on, and it removes the evidence that would have shown which layer was at fault. It is a last resort, not an opening move, and it should only be considered when the record shows that the simpler routes have all been tried and have all stopped at the same point.
Boundaries: Problems That Look Similar but Are Not This One
Not every driver installation problem is a stall, and the similar problems each belong to their own guide. If the symptom is one of the following, follow that guide, not this one.
An installer that shows an error message and rolls back to the old driver is an installation failure. A screen that goes black during installation is an installation black screen problem, and the installer window in this guide is still visible, with the picture not black. A machine that stays black after the driver was installed and the machine restarted is a post-installation black screen rescue problem, and its route runs through safe mode, the basic display driver, and a clean removal and reinstall. A driver version that Windows Update replaced afterwards is a Windows Update problem, and Windows Update appears in this guide only as one lock source in Step 4. A game that stops on its loading screen is a loading stall, and it belongs to the loading screen guide — though the principle is the same one used here, that a still progress bar with a moving process is a process that is working, and a stopped process is defined by no response plus all resources still.
Finally, there are things this guide will never teach, and a source that teaches them should be closed. Never force the machine off with the power button to interrupt an installation. Never leave antivirus off for a longer period. Never edit the registry. Never download a single DLL file from the internet, and never install an unknown "driver repair tool". None of these is a diagnosis, and each one trades a working machine for a less safe one.
When to Stop and Bring the Machine In
Stop when all seven steps have been worked through, one variable at a time, and the installer still stops at the same percentage and stage every time — or when the question becomes which part to change, rather than which layer is at fault. Stop sooner if ending the installer through Task Manager leaves the picture abnormal or the graphics card not appearing normally in Device Manager, or if the same stall appears for several different programs, which points at damaged system files rather than at the driver.
Bring the machine in with the notes from every step: the percentage and stage where it stopped, the processor and disk readings from Task Manager, the installation route, the Windows Update status, and the changes already tried. In-store inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. There is no home-visit service and no Mong Kok shop; inspection is carried out in the shop.
A diagnosis that ends at the stop line is not a failed diagnosis. A note that says "stopped at 47%, installer process idle, standalone package, Windows Update not running, fresh package stopped at the same percentage" is a precise description of where the fault lives, and it is exactly what an in-store inspection needs to start from the right place instead of from the beginning.
Frequently Asked Questions
Q1: The progress bar has stopped — does that mean the installation is dead?
Not necessarily. A progress bar that is not moving is not the same as an installer that has stopped. While the installer writes files or registers components, the bar may sit still and the screen may not change. Open Task Manager and look at the installer process: if the processor or the disk shows sustained activity, the installer is still working and should be left to finish. Only when the processor and the disk are both close to zero, and the process shows "Not responding", has the installer genuinely stopped.
Q2: How long should I wait before calling it stuck? Is there a universal number of minutes?
There is no universal number. NVIDIA publishes no universal timeout for an installer screen, and different installer packages and different machines take very different amounts of time, so any single figure would be wrong for most readers. Judge by movement, not by minutes: if the percentage is still changing, or the processor and the disk show activity, the installer is still working. Only when everything has been still is the installer genuinely stopped. A fifteen-minute figure that circulates online comes from a different situation — the first boot after a fresh Windows 10 installation — and it does not apply here.
Q3: How do I use Task Manager to tell whether the installer is still working or genuinely stuck?
Open Task Manager and find the installer process — the NVIDIA installer process, or the AMD installer process — and look at its processor usage and its disk usage. Sustained processor or disk activity means the installer is still working, however still the progress bar looks. Processor and disk both close to zero, sustained over time, together with a process that shows "Not responding", means the installer has genuinely stopped. That is the decisive test in this guide, and it must be done before any fix is attempted.
Q4: What is the danger of pressing the power button to force the machine off? How do I interrupt safely?
Forcing the machine off while an installation is in progress can leave the driver half-written, and a half-written driver is a real black screen fault. The safe interruption is to end the installer process through Task Manager, once the process has been confirmed as genuinely stopped. After ending it, confirm that the old driver is still working normally — the picture is normal, and the graphics card appears normally in Device Manager — and write down the percentage and stage at which the installation was interrupted before trying again.
Q5: Can Windows Update running in the background lock up a driver installation?
Yes. Windows allows only one installer to use the Windows Installer service at a time, so a Windows Update installation running in the background, another program installing or updating, or a previous installation waiting for a restart can hold the driver installer still. Check Settings under Windows Update, look for another installer process such as msiexec, and check for a pending restart. If Windows Update is in progress, let it finish, or pause it, and do not run the driver installation at the same time.
Q6: Can antivirus software block the installation? Is turning antivirus off the fix?
Antivirus real-time protection can hold a file for checking while the installer tries to write a driver file, or treat one step of the installation as suspicious and block it. Turning the protection off briefly is a diagnostic comparison: it shows whether the antivirus was the cause. It is not a fix. Once the result is known, switch the protection straight back on, whether the test succeeded or not. Leaving antivirus off for a longer period is not a solution, and it must never be presented as one.
Q7: What does it mean if it stops at the same percentage every time?
It usually points at the installer package itself. A package that was interrupted during download, or downloaded incompletely, or damaged in transit, will stop the installer at the same point every time, because the file itself has not changed. Retrying the same file will give the same answer. Download a fresh standalone package from the manufacturer's official website and try that instead, changing one thing at a time and writing down the result. If the fresh package gets past the point, the package was the cause.
Q8: What is the difference between a standalone installer package and updating through NVIDIA App / AMD Software?
They are different routes to the same installation, and they download, verify, and unpack differently. Updating through NVIDIA App or AMD Software runs inside the manufacturer's app, with its own download and staging steps. A standalone package is downloaded from the official website and run directly, with administrator rights. A stall that follows one route and not the other points at the route or the package, not at the machine — which is why Step 6 retries by the standalone route, with a freshly downloaded file.
Q9: When should I consider a clean-removal tool (DDU)?
Only as a last resort, after the different-route retry has failed. A clean-removal tool is an advanced step, not a first step: using it first destroys the old settings and installation state that the comparison depends on, and it removes the evidence that would have shown which layer was at fault. Consider it when repeated retries still stop at the same percentage and stage, and the record shows that the simpler routes have all been tried. Even then, it is a step to be taken with the full record in hand, not a cure on its own.
Q10: If retrying through a different path still fails, what should I do next?
Bring the machine in with the complete record: the percentage and stage where it stopped, the process activity readings from Task Manager, the installation route, the Windows Update status, and the changes already tried. If the installer stops the same way for several different programs, not only for the driver, the suspicion moves to damaged system files, and the next step is a system file check — not repeated driver reinstalls. In-store inspection is at Room 1209, Dali Plaza, Shek Mun, charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. You can call 2186 8010 or WhatsApp 6558 6806.