GPU Driver Disappears After Every Reboot? Windows Update Rollback, Driver Reinstall Loop & AMD Error 205 Guide

Key Takeaway
A driver that vanishes after every reboot is not one problem but three: the driver never loaded, the version was rolled back, or the card was never listed. Each shape points at a different layer — loading, Windows Update, or power and seating. Identify which shape you are seeing first, because reinstalling the driver only helps one of them.
Three Symptoms, Not One Problem
The phrase "the driver disappears after every reboot" hides at least three different symptoms, and the correct investigation is different for each one. The first step in this guide is not to reinstall the driver. It is to identify which symptom is actually being seen.
| Symptom | What it looks like | Key feature |
|---|---|---|
| A. Driver gone: Device Manager shows Microsoft Basic Display Adapter | After boot the resolution is low, games will not open, and the control panel is missing; Device Manager shows Microsoft Basic Display Adapter, with Microsoft as the driver provider | The vendor driver never loaded at all, and the system is running on the generic fallback driver |
| B. Driver version rolled back: provider, date, or version changed on its own | A new version was installed yesterday, and today the version number is smaller, the date is older, or the control software reports a version mismatch | A driver is loaded, but it is not the version that was installed; something, usually Windows Update, replaced it without being noticed |
| C. Device intermittently gone: sometimes the card is recognised, sometimes it is not | Sometimes the boot is normal, and sometimes Device Manager has no graphics entry at all, or only an unknown device with a warning; another reboot brings the card back | The device itself comes and goes, which is an enumeration, power, or seating problem rather than a driver version problem |
The three symptoms share only one thing: the problem follows the boot. Symptom A is a driver that never loaded. Symptom B is a driver that was replaced. Symptom C is a device that was never listed. Treating them as one problem leads to the wrong method most of the time — for example, reinstalling the driver repeatedly for symptom C, where the problem is not in the driver layer at all and reinstalling can never fix it.
This guide assumes a machine that was previously working normally. It does not cover a fresh Windows installation, where seeing Microsoft Basic Display Adapter is normal, or a machine that has just had hardware changed, where a card not being recognised is a separate topic.
How Windows Chooses a Driver at Boot
Booting with a graphics card follows roughly four steps. Any one of them can fail, and each failure produces a different version of "the driver is gone".
- Enumerate the device. The firmware and Windows list the PCIe devices and recognise the graphics card hardware. If this step fails, Device Manager has no graphics entry at all — symptom C.
- Match a driver. Windows uses the hardware identifiers to search the Driver Store for a compatible driver package, and picks one by driver ranking. If the Driver Store holds several versions, or Windows Update has just delivered another version, the match can differ from the version installed manually — symptom B.
- Load the driver. Windows loads the selected driver's core files, such as nvlddmkm or amdkmdap. If the files are damaged, the signature is not accepted, or another component has locked them, loading fails and Windows falls back to Microsoft Basic Display Adapter — symptom A.
- Start the control software. After the driver loads, the control software — NVIDIA App or AMD Software — reads its settings files and starts its background services. If the driver version and the control software version do not match, the control software may fail to open or report a version mismatch — a variant of symptom B.
The practical meaning of these four steps is that where the symptom appears is where the investigation should start. No entry in Device Manager means starting at step one. An entry showing Microsoft Basic Display Adapter means starting at step three. A real card name with a rolled-back version means starting at step two.
Cause One: Windows Update Installs an Older Driver
Windows Update distributes graphics drivers with certification and device compatibility as its priorities, not with the vendor's latest features as its priority. The version it delivers can therefore carry a smaller version number and an older date than the version installed manually. After a manual install of the vendor's latest version, Windows Update may later replace it with the version it considers suitable. The chain is: install the vendor's new version manually, Windows Update checks for driver updates, it considers another driver more suitable, it installs and overwrites the manual version, the next boot shows a rolled-back driver version, and the control software reports a version mismatch. The reader then concludes that the driver has disappeared.
Confirmation follows the three-evidence method: the driver provider, date, and version in Device Manager; the driver updates in the Windows update history; and the event timeline in Reliability Monitor, opened with perfmon /rel. Only when all three line up can the rollback fairly be attributed to Windows Update.
One boundary needs to be stated plainly. A smaller version number does not mean a damaged driver. If the rolled-back driver runs normally and games run normally, the situation is "not the version that was wanted", not "a broken driver". It becomes a problem when the rollback brings black screens, crashes, a control program that will not open, or a version that jumps back and forth from boot to boot. A version being older is not automatically a fault.
Cause Two: Fast Startup Restores the Old State
Fast Startup changes what a shutdown means. When it is on, shutting down is a hybrid shutdown: the user session is signed out, but the kernel session, including the drivers already loaded, is written to the hibernation file hiberfil.sys and restored at the next boot, rather than being loaded again from scratch. Microsoft's own documentation states that the kernel session is not closed during Fast Startup, only hibernated, and that Restart is not affected by Fast Startup and performs a full boot.
For a disappearing driver, Fast Startup has two consequences.
First, a bad driver state is restored. If the driver was already failing to load or had already been replaced before the shutdown, that bad state is written into the hibernation file and restored at the next boot. The result is the same symptom at every boot, which looks like a stubborn fault, when in fact the same bad state is simply being restored again and again.
Second, a driver change does not take effect. After installing a new driver, testing it with a shutdown followed by a power-on may restore the old kernel state, so the new driver was never actually loaded. The reader concludes the new driver did not work, when it was never tried. The correct test is to use Restart, not shutdown followed by power-on.
The diagnostic comparison is therefore essential: do one Restart, and then do one shutdown followed by power-on, with Fast Startup on. If Restart is normal and only shutdown followed by power-on shows the problem, Fast Startup is a suspect. If both ways of booting show the problem, Fast Startup is not the cause, and no more time should be spent on it.
To turn Fast Startup off, go to Control Panel, Power Options, Choose what the power buttons do, and clear "Turn on fast startup". Microsoft also notes that ordinary users are generally not advised to switch Fast Startup off permanently. Turning it off should therefore be presented as a diagnostic comparison step, not as a permanent recommendation. Once the cause is found, the handling should be explained, rather than telling every reader to leave it off for good.
Cause Three: Driver Signature or Damage
Windows requires graphics drivers to carry a digital signature. Loading fails when the driver files are damaged — for example, an incomplete download, a disk error, or an installation interrupted partway through — so the signature check does not pass; when an unsigned driver, or a driver whose signature is not accepted, has been installed, such as a modified driver from an unknown source; or when system files are damaged so that the signature check mechanism itself fails.
The symptom is Device Manager showing the real card name with a yellow warning icon, or falling straight back to Microsoft Basic Display Adapter. To separate the possibilities, note the device status and error code in Device Manager — error code 43, for example, means the vendor driver has loaded but the device reports an error, which is different from Microsoft Basic Display Adapter, where the driver never loaded — and check Event Viewer for driver load failures. The handling is to download again from the official channel and do a clean installation, using Custom (Advanced) and then Perform a clean installation on NVIDIA, or Factory Reset on AMD. It is not to delete driver files one by one by hand.
This guide does not give instructions for bypassing driver signature enforcement. That is a deliberate omission: the method and the risks vary by Windows version, and a bypass is not a diagnosis.
Cause Four: AMD Error 205 — Installed, Then Rolled Back
AMD's own description of Error 205 is that AMD Software appears to install successfully, but Windows Update may have restored the driver version during the installation. The result is that the AMD Software application itself is present, while Windows is actually using an older driver supplied by Microsoft or by the original equipment manufacturer, so the two versions do not match.
Error 205 deserves its own section because it has three counter-intuitive features.
First, an installer reporting success does not mean success. When Error 205 appears, the completion screen is not false — AMD Software was installed — but the driver version was replaced during the install. "Installation complete" therefore cannot be treated as verification. The driver version in Device Manager must be checked afterwards.
Second, it is not evidence of a broken card. Error 205 is essentially a driver version conflict, not a hardware fault. Reading it as a broken card leads to hardware replacement that was never needed.
Third, the official fix is a temporary setting, not a permanent shutdown of updates. AMD's guidance for Error 205 is to open sysdm.cpl, go to the Hardware tab, open Device Installation Settings, select No, save the change, restart, and then run the AMD Software installer again. That setting temporarily prevents automatic replacement of the device driver while the install runs, and it should be reviewed afterwards. It is not switching Windows Update off permanently or permanently disabling driver updates.
Related error codes must be kept separate, because they point at different handling. Error 202 means the installer detected a Windows update in progress and cannot continue. Error 206 means a Windows installation or update is pending and a restart is needed first. Error 207 means the software installed successfully but Windows detected that the display device may have a problem. The fix for 205 cannot be applied to the other codes. Older guides on this site did not mention Error 205 at all, and did not mention Device Installation Settings or sysdm.cpl, so this section is new material.
Cause Five: Power or Slot Seating Makes the Device Disappear
If Device Manager intermittently has no graphics entry at all, or only an unknown device, the problem is very likely not in the driver layer but in the enumeration layer.
Power. A loose graphics card power cable or an unstable power supply can mean the card does not complete its initialisation during a cold boot, because the power timing is wrong, so the firmware and Windows cannot list it. After a restart, the power is stable again and the card is recognised. This connects with the cold-boot power timing mechanism, including the Power-Good signal, described in earlier guides on this site.
Slot contact. Dust in the PCIe slot, oxidised contacts, a card that is not seated firmly, or vibration in the case can make contact intermittent. The characteristic sign is that the problem follows a physical change — it starts after the case was moved — or that it comes and goes, with no connection to any driver version.
Link negotiation failure. At boot, the card and the motherboard negotiate lane count and transfer speed through link training. If the signal quality is poor, the negotiation can fail and the system does not recognise the card.
The distinguishing feature is that symptom C does not follow the driver version — every driver version behaves the same way — and it does follow physical state: cold boots, a case that was moved, or one particular way of booting. This kind of problem should not be handled with DDU or driver reinstallation. The physical installation should be checked, and where opening the case or measuring power is involved, a reader who is not confident should seek professional help rather than opening a power supply or measuring supply rails.
Other Causes: Settings, Accounts, and Third-Party Software
Damaged settings profiles. When a control software settings profile is damaged — for example, the NVIDIA DRS database — the driver may fall back to default values every time it loads, so settings are restored at each reboot. The feature here is that settings are restored, not that the driver disappears. The two must be kept separate.
A stopped background service. When a service such as NVIDIA Display Container LS is not running, the control software may open but cannot write settings.
A colour calibration loader. The Calibration Loader task in Task Scheduler loads the Windows default colour settings at sign-in and overwrites the driver's colour settings. This affects only colour settings being restored, not the driver disappearing.
Third-party overclocking or monitoring software. Overclocking settings loaded automatically at boot can conflict with driver initialisation, causing the driver to fail to load or settings to be changed. When investigating, the automatic startup of such software can be disabled as a single comparison step.
The First-Step Identification Table
| Check | Symptom A: Basic Display Adapter | Symptom B: Version rolled back | Symptom C: Device intermittently gone |
|---|---|---|---|
| Device Manager graphics entry | An entry exists, named Microsoft Basic Display Adapter | An entry exists, with the real card name | Sometimes no entry, or an unknown device |
| Driver provider | Microsoft | The vendor, but with an older version or date; or Microsoft | Not applicable, because the device does not exist |
| Control software | Will not open, or is missing | Opens, but reports a version mismatch, or shows Error 205 | Depends on whether the card is recognised at that boot |
| Resolution | Locked to a low value | Usually normal, but some features are missing | Comes and goes |
| Follows what | Driver load failure | Windows Update and reboot timing | Cold boots and physical movement of the case |
| Restart versus shutdown then power-on | Both ways show the problem | Either way can show it, depending on update timing | Cold boot shows it, warm restart is normal, pointing at power or link training |
The Step-by-Step Investigation — One Variable at a Time
- Identify the symptom. Use the table above to decide whether the problem is A, B, or C. Note the driver provider, date, version, and digital signer in Device Manager, the version shown by the control software, and the date the problem first appeared.
- Compare boot methods. Do one Restart, then do one shutdown followed by power-on, with Fast Startup on. If Restart is normal and only shutdown followed by power-on shows the problem, Fast Startup is the suspect. If both show it, Fast Startup is excluded, and the investigation moves on.
- Compare timelines. Open the Windows update history and check whether a driver update was installed on the same date the problem first appeared. Open Reliability Monitor with perfmon /rel and look at the event timeline around the problem. Only when the three pieces of evidence line up should the rollback be attributed to Windows Update.
- Note the error code. If Device Manager shows a yellow warning icon, note the error code, such as 43, and the exact wording of the error message. If an AMD installer shows an error code, note the number — 205, 202, 206, or 207 — rather than writing vaguely that the install failed.
- Error 205 branch. If Error 205 appears, follow AMD's guidance: open sysdm.cpl, go to Device Installation Settings, select No, save, restart, and then run the AMD Software installer again. Afterwards, check the Device Manager version and confirm it agrees with AMD Software.
- Clean reinstall. If Windows Update and Fast Startup have been excluded and the problem remains, do the vendor's built-in clean installation first — Custom (Advanced) and then Perform a clean installation on NVIDIA, or Factory Reset on AMD. Only if that fails should DDU be considered, in Safe Mode and used once, as described in the companion brand-switch guide. Do not jump straight to DDU.
- Hardware-layer comparison. If the symptom is C, or if a clean reinstall changes nothing at all, move to the hardware layer: confirm the power cables are seated, the card is seated firmly, and the slot is free of dust; compare a cold boot with a warm restart; and compare before and after the case was moved. This step involves opening the case, so a reader who is not confident should seek professional help.
- Narrow the conclusion. Record for every step what was done, whether anything changed, and whether any message changed. If every software-layer step has been done and the symptom is completely unchanged, the problem leans towards hardware. If one step changed the symptom, the layer that step points at is where the cause lives.
Driver Problem or Hardware Problem — the Boundary
| Feature | Leans towards a driver or software problem | Leans towards a hardware problem |
|---|---|---|
| When it started | After a driver or Windows update | Out of nowhere, with nothing updated |
| Follows the version | Changing the driver version removes or changes the symptom | Every driver version behaves the same |
| Follows the boot method | Restart is normal, shutdown then power-on shows it, pointing at Fast Startup | Cold boot shows it, warm restart is normal, pointing at power or link training |
| How often | Occasionally, not every time | More and more often, until even booting shows it |
| Device Manager | An entry exists, with the problem in the driver version or loading | Intermittently no entry, or an unknown device |
| Stress test | A stress test runs smoothly | A stress test fails within minutes |
| After changing the driver | The symptom disappears or changes | The symptom is exactly the same |
The most important dividing line is this: a driver problem follows software state — version, updates, and boot method — while a hardware problem follows physical state — temperature, vibration, cold versus warm, and power. The evidence from the two sides must not be mixed together.
Other boundaries are worth stating plainly. Seeing Microsoft Basic Display Adapter after a fresh Windows installation is normal; install the vendor driver directly. Seeing it in Safe Mode is also normal, because Safe Mode deliberately does not load the vendor driver, and it cannot be used as diagnostic evidence. A version that rolled back but works normally is not a fault; it is simply not the version that was wanted, and unless the rollback brings a real problem, it does not need urgent handling. Settings being restored is a control software layer problem, and the driver disappearing is a driver loading layer problem; they can appear together, but they are investigated in a different order. Resolution or refresh rate dropping at every boot is a mode-saving problem, not necessarily a driver disappearance — the driver itself may be loading normally. A first cold boot with no picture at all, fixed by a restart, is a power timing, memory training, or link retraining problem, not a driver disappearance. No picture at all, not even the firmware screen, is a different problem from a driver disappearance, where a picture exists but the resolution is low.
Ten Common Mistakes
- Seeing Microsoft Basic Display Adapter and concluding the card is broken. That name only means the vendor driver did not load. A fresh installation, Safe Mode, or a damaged driver all produce the same name.
- Seeing an older version and concluding the driver is damaged. A rollback is most often Windows Update replacing the driver, and the driver itself may be entirely normal. Compare the timeline first, and do not reinstall at once.
- Testing a driver change with shutdown then power-on. With Fast Startup on, shutdown then power-on restores the old kernel state, so the new driver was never actually loaded. A driver change must be tested with Restart.
- Seeing Error 205 and concluding the install failed or the card is broken. Error 205 means the install completed but the driver version was restored, which is a version conflict, not a hardware fault. The fix is AMD's temporary Device Installation Settings change, not a card replacement.
- Applying the Error 205 fix to other error codes. Codes 202, 206, and 207 each have their own meaning and handling, and one fix cannot be used for all of them.
- Reinstalling the driver repeatedly as the investigation. Without noting the version, comparing the timeline, or comparing boot methods, ten reinstalls give the same result as one. Change one variable at a time and record each result.
- Jumping straight to DDU. DDU is a second-level tool. Without identifying the symptom, comparing the timeline, and trying the vendor's built-in clean installation first, DDU hides the real cause.
- Treating turning Fast Startup off as a permanent fix. Turning it off is a diagnostic comparison. Microsoft does not advise ordinary users to leave it off permanently, and once the cause is found, the handling should be explained rather than telling every reader to leave it off.
- Treating settings being restored as the driver disappearing. Settings restoration and driver disappearance are different layers with different handling. Reinstalling the driver to fix a damaged settings profile usually has no effect.
- Ignoring the physical layer. When a device disappears intermittently, continuing to reinstall drivers wastes time. A loose power cable, a card that is not seated firmly, or dust in the slot can never be fixed from the driver layer.
When to Stop and Bring the Machine In
Stop when every software-layer step has been worked through, one variable at a time, and the same result appears every time — or when the question has become which part to change, rather than which layer is at fault. Stop sooner if the card is intermittently missing from Device Manager even after the physical installation has been checked, or if a stress test fails quickly, because those signs point towards hardware.
Bring the machine in with the notes from every step: the symptom type, the driver provider, date, and version, the update history dates, the Restart versus shutdown comparison result, any error codes in their exact wording, and the clean reinstall results. 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 the driver was Microsoft Basic Display Adapter after every boot, the version and date were unchanged, Restart and shutdown behaved the same way, and a clean reinstall changed nothing 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
Does a driver disappearing after every reboot mean my graphics card is broken?
Not on its own. A driver disappearing after every boot can mean the driver never loaded, the version was rolled back by Windows Update, or the card itself was never listed at boot. Only the last shape points towards the physical layer, and even then the cause may be a loose power cable or a card that is not seated firmly rather than a broken card. Identify which of the three shapes is being seen first, using the table in this guide, before drawing any conclusion about the hardware.
How do I tell whether the driver is "not loaded", "rolled back in version", or "the device itself disappeared"?
Look at Device Manager. "Not loaded" shows an entry named Microsoft Basic Display Adapter, with Microsoft as the driver provider and a low locked resolution. "Rolled back" shows the real card name, but with a smaller version number or an older date than the version that was installed, or the control software reports a version mismatch. "Device disappeared" shows no graphics entry at all, or only an unknown device, and the card sometimes returns after another reboot. The three shapes point at loading, Windows Update, and enumeration respectively.
What does Device Manager showing "Microsoft Basic Display Adapter" mean?
It means Windows is running on the generic fallback driver because the vendor driver did not load. It does not mean the card is broken. A fresh Windows installation, Safe Mode, a damaged driver, or a failed driver load all produce the same name. To tell them apart, check the driver provider and date, check whether the situation follows a fresh installation or Safe Mode, and check Event Viewer for driver load failures before concluding anything about the hardware.
Why was the driver fine yesterday and back to an old version after booting today?
Because Windows Update can install a graphics driver it considers suitable, and the version it delivers can carry a smaller version number and an older date than the version installed manually. The chain is: install the vendor's new version manually, Windows Update later replaces it, and the next boot shows the rolled-back version. Confirm it with three pieces of evidence — the driver provider, date, and version in Device Manager, the driver updates in the Windows update history, and the event timeline in Reliability Monitor — before attributing the rollback to Windows Update.
What does AMD Error 205 mean, and how should I handle it?
Error 205 means AMD Software appears to install successfully, but Windows Update may have restored the driver version during the installation, so AMD Software and the driver in use do not match. It is a version conflict, not a hardware fault. AMD's guidance is to open sysdm.cpl, go to the Hardware tab, open Device Installation Settings, select No, save the change, restart, and then run the AMD Software installer again, and to review that setting afterwards. Afterwards, check the Device Manager version and confirm it agrees with AMD Software. Do not apply this fix to other error codes such as 202, 206, or 207.
What is the connection between Fast Startup and a driver disappearing after every boot? How do I use "Restart" as a comparison?
With Fast Startup on, shutting down is a hybrid shutdown: the kernel session, including the drivers already loaded, is written to the hibernation file and restored at the next boot, rather than being loaded again. A bad driver state can therefore be restored at every boot, and a newly installed driver may never actually be loaded when tested with shutdown then power-on. Restart is not affected by Fast Startup and performs a full boot. Compare the two: do one Restart, then do one shutdown followed by power-on. If Restart is normal and only shutdown then power-on shows the problem, Fast Startup is a suspect; if both show it, Fast Startup is excluded.
When the driver disappears, which three things should I check first?
First, identify the symptom using the table in this guide — whether the driver never loaded, the version rolled back, or the device itself disappeared — and note the driver provider, date, version, and digital signer. Second, compare boot methods: one Restart against one shutdown followed by power-on, to test Fast Startup. Third, compare timelines: check the Windows update history and Reliability Monitor for a driver update installed on the same date the problem first appeared. Those three checks decide the direction of everything that follows, and they should be done before any driver is reinstalled.
When is a disappearing driver actually a power or slot problem rather than a driver problem?
When the device itself comes and goes: Device Manager sometimes has no graphics entry at all, or only an unknown device, and the card sometimes returns after another reboot. The distinguishing features are that the symptom does not follow the driver version — every version behaves the same way — and that it does follow physical state, such as cold boots, or starting after the case was moved. A loose power cable, a card that is not seated firmly, dust in the slot, or a link negotiation failure can all produce this shape, and none of them can be fixed by reinstalling a driver.
My driver version rolled back but the machine works normally. Does it need immediate handling?
Not necessarily. A smaller version number does not mean a damaged driver, and if the rolled-back driver runs normally and games run normally, the situation is simply "not the version that was wanted". It becomes a problem when the rollback brings black screens, crashes, a control program that will not open, or a version that jumps back and forth from boot to boot. Unless the rollback causes a real problem, there is no need to act urgently, and the handling can be planned rather than rushed.
I tried a clean reinstall and the driver still disappears after every boot. What should I do next?
First, check whether the clean reinstall was actually the right step for the symptom: if the device itself disappears intermittently, the problem is in the physical layer, and no reinstall will fix it. If the symptom is a rollback, confirm it with the three pieces of evidence and follow the Windows Update or Error 205 branch. If the symptom is a load failure, note the Device Manager error code and the exact error message, and check Event Viewer. If every software-layer step has been done, one variable at a time, and the symptom is completely unchanged, the problem leans towards hardware, and the machine should be brought in with the complete record from every step.