Turn Off Automatic Driver Installation in Windows 11 & 10
—
Windows installs and updates drivers automatically for every device you own — and the switch that controls it still exists, hiding in a dialog box that looks beamed in from the Windows 7 era: press Win + R, type sysdm.cpl, press Enter, open the Hardware tab, click Device Installation Settings, choose No (your device might not work as expected), and Save Changes. That is the whole operation — and before you perform it, hear the honest part: for almost everyone, this switch should stay on Yes. Turning it off converts you into your PC's full-time driver librarian. There is exactly one common situation that justifies it, this page covers it properly, and it also covers the road back.
Jake reached for this switch exactly once with a clear conscience. A customer's gaming rig had a recurring ritual: he would install the newest graphics driver, everything ran beautifully — and days later, Windows Update would quietly "update" him backward to an older version it preferred, breaking his frame pacing mid-tournament-season. Reinstall, wait, overwritten again: a tug-of-war with an opponent that never sleeps. Jake did the full fix — clean-installed the vendor driver, flipped the switch to No so Windows would stop redecorating, and put a note in the case file: re-enable after the version clash passes. Three months later, it did, and the switch went back to Yes. That discipline — off for a reason, back on when the reason dies — is the entire art of this setting.
Ethan: "It's the mail-hold form at the post office. Genuinely useful the month a package thief works your street — but leave the hold on forever and you are the person who must fetch every letter, every bill, every notice, personally, for life. The people with mystery problems aren't the ones who filed the hold. They're the ones who filed it in 2023 and forgot."
What the switch actually controls
Set to Yes (the default), Windows fetches drivers automatically in two moments: when you plug in new hardware (the "setting up your device" magic that makes a new mouse or printer just work) and through Windows Update's ongoing driver maintenance. It also pulls the makers' companion apps and the pretty device icons. Set to No, all of that stops: new hardware gets only whatever basic driver ships inside Windows — sometimes enough, often not — and nothing ever updates unless you do it. The dialog's own warning, "your device might not work as expected," is not boilerplate; it is a plain description of plugging a new webcam into a machine that has been told not to go get the webcam's driver.
The one legitimate reason: the overwrite war
Sometimes Windows Update's catalog holds a driver version that is wrong for you — older than the vendor's current one, or a generic build that fights your hardware — and it reinstalls its choice over yours, repeatedly, with total patience. Graphics drivers are the classic battlefield (the gamer's version-clash above), with audio and Wi-Fi drivers as occasional theaters. That tug-of-war is the honest use of this switch: it is the only way to make your deliberate driver choice stick while the bad catalog entry circulates. The discipline that keeps it honest has three parts: fix the actual driver first (clean-install the vendor version), then flip the switch; write yourself a note about why; and treat the No state as temporary — catalog clashes get fixed within months, and the switch should outlive the clash by zero days.
Flipping it, step by step
- Press Win + R, type
sysdm.cpl, press Enter — the classic System Properties dialog opens (identical on Windows 11 and 10; this veteran outlived every Settings redesign). - Open the Hardware tab → Device Installation Settings.
- Choose No (your device might not work as expected) — or Yes to restore the default — and click Save Changes (admin approval required).
- No restart needed. The policy applies to future installations; drivers already on the machine stay exactly as they are.
Windows 10 Pro and 11 Pro owners have a second, slightly narrower lever: the Group Policy editor (gpedit.msc) → Computer Configuration → Administrative Templates → Windows Components → Windows Update → "Do not include drivers with Windows updates." Enabled, it stops the update-channel deliveries while leaving plug-in-new-hardware magic alone — a more surgical cut for the overwrite war, when your edition offers it. Home edition gets the sysdm.cpl switch only, which is fine: it covers the real case.
Life with the switch off: your new job description
- Every new device is now your errand. Plug in a printer, webcam, or adapter and expect to fetch its driver from the maker's site yourself — the "just works" era is suspended on this machine.
- Security-relevant driver fixes stop arriving. Drivers get vulnerability patches like any software; you have unsubscribed from the automatic feed, so the vendor tools you still trust (GPU app, laptop maker's app) become your only pipeline — keep them.
- Leave a note for future-you. Six months from now, a non-working USB device will make no sense until someone remembers this switch. Jake's case files exist because forgetful toggles are the diagnosis behind half of "this PC has always been weird."
- Put a return date on it. When the driver clash that justified the hold is fixed upstream, flip it back to Yes the same week.
Yes vs No, honestly tabulated
Everything the two positions actually buy and cost, side by side. Notice the asymmetry the table makes obvious: Yes has one flaw (the occasional overwrite), while No has a standing tax on every future device and fix — which is why the honest advice runs so lopsided:
| Yes (default) | No | |
|---|---|---|
| New hardware | Sets itself up in a minute | Basic function at best until you fetch the driver |
| Driver fixes & patches | Arrive silently | Only what you fetch yourself |
| Your hand-picked vendor driver | Can occasionally get overwritten (the one flaw) | Stays put — the point of the switch |
| Maintenance burden | None | You, forever, for every device |
| Right for | Nearly everyone, nearly always | An active overwrite war, temporarily |
Winning the overwrite war properly (switch included)
The switch alone does not fix a bad driver — it only stops the tug-of-war. The full sequence for the gamer's scenario: uninstall the conflicting driver cleanly (for GPUs, the deep-clean route from our display-driver guide when normal uninstalls keep failing), install the vendor's current version from its own app or site, then flip this switch so the choice sticks, then set the calendar reminder to flip it back. Skipping the clean-install step and just toggling leaves you defending a driver that was half-broken to begin with — the war won, the wrong flag planted.
How to know the war is over (the flip-back test)
The switch's whole risk is being forgotten, so give it an exit condition on day one. The test is simple: when the vendor ships a driver version newer than the one Windows Update was pushing — check the version numbers in the vendor's app against what Windows offered — the clash that justified the hold is dead, because Windows will no longer "upgrade" you backward. Flip to Yes, let Windows Update run once, and confirm your device still reports the vendor's version a week later. If it does — and it nearly always does — the war is over and the default resumes. Jake's calendar reminder says exactly this: check versions; if vendor > catalog, restore Yes. Ten seconds of arithmetic, once a month, until it resolves.
Scenario → right setting
The judgment calls of this whole page, compressed into rows — including the one row that is really a myth wearing a scenario's clothes:
| Scenario | Setting |
|---|---|
| Normal PC, no driver drama | Yes — and never think about it again |
| Windows keeps replacing your GPU/audio/Wi-Fi driver | Clean-install the right driver, then No — temporarily |
| Pro edition, same war, want surgical | gpedit's "Do not include drivers with Windows updates" instead |
| Mystery: new devices never work on this PC | Check this switch — someone set No years ago; restore Yes |
| "I read that turning it off speeds up Windows" | It doesn't. Yes. |
FAQ — automatic driver installation
How do I stop Windows from installing drivers automatically?
Win + R → sysdm.cpl → Hardware tab → Device Installation Settings → No → Save Changes. Same dialog on Windows 11 and 10.
Should I turn automatic driver installation off?
Almost certainly not — the automatic system is why hardware "just works." The one honest exception is an active overwrite war where Windows keeps replacing a driver you deliberately chose.
Windows keeps overwriting my graphics driver. Is this the fix?
It is the second half of it: clean-install the vendor's driver first, then flip this switch so the choice sticks — and plan to flip it back when the catalog clash passes.
Does turning it off affect drivers already installed?
No — existing drivers stay untouched. The switch governs future installations and updates only.
Will new devices still work with it off?
Only as far as Windows' built-in basic drivers reach — a mouse will move, but printers, webcams, and adapters often need their real driver, which is now your errand to fetch from the maker's site.
Is there a way to block only Windows Update's drivers, not new-device setup?
On Pro editions, yes: gpedit.msc → Windows Update → "Do not include drivers with Windows updates." That is the surgical version of this page's switch.
Does Home edition have the Group Policy option?
No gpedit on Home — the sysdm.cpl switch is your lever, and it covers the real-world case fine. We do not recommend the registry recreations of the policy; the dialog exists for a reason.
Can I block just ONE driver instead of all of them?
Microsoft's old "wushowhide" hide-update tool has faded from support, which is precisely why this switch plus a clean vendor install became the practical answer. Blocking everything temporarily beats fighting one update forever.
Does turning this off make Windows faster or updates smaller?
No measurable speed change, and update downloads barely differ. Every "debloat" list that includes this switch is trading real convenience for imaginary performance.
Is it safer to manage drivers manually?
The opposite for most people — drivers receive security fixes through the automatic channel, and a manual regime that nobody maintains means unpatched drivers forever. Off is a tactic, not a lifestyle.
My PC never sets up new devices properly. Could this be why?
Very plausibly — a forgotten No on this switch is a classic behind "USB things never work here." Check sysdm.cpl and restore Yes; the difference is immediate on the next device you plug in.
Do the vendors' own apps still work with the switch off?
Yes — the NVIDIA/AMD/Intel apps and laptop makers' support tools install drivers independently of this switch. With automation off, they graduate from convenience to your primary supply line.
Why is this setting in such an ancient-looking dialog?
System Properties predates the Settings app by decades and has survived every redesign — Microsoft keeps the veteran dialogs alive precisely for switches too consequential to make casually discoverable. sysdm.cpl is worth remembering; several old levers live there.
Does this switch affect Windows Update itself?
No — Windows' own security and feature updates continue exactly as before. Only the driver deliveries riding alongside them are governed here.
How do I turn automatic driver installation back on?
Same dialog, choose Yes, Save Changes. Then let Windows Update run once — it will catch up on anything the hold skipped.
What's the difference between this and pausing Windows updates?
Pausing stops everything for weeks and auto-resumes; this switch stops only drivers, indefinitely, until you revisit it. Different tools — the indefinite one is the one that needs the calendar note.
Where to go next
- The honest driver-updating guide
When to update at all, and the scam industry to avoid. - Display problems after an update — the fix ladder
Including the clean-install route the overwrite war requires. - Install printer drivers in Windows 11 and 10
The device you'll meet first if you leave this switch off. - This month's Windows update, decoded
What still arrives when the driver faucet is closed.
Revision note. Originally published September 2015, as a beginner's tour of a then-new Windows 10 behavior. Rewritten August 18, 2026 with the perspective a decade of shop counters buys: the switch still lives in the same ancient dialog, the honest answer is still "leave it on Yes," and the one real exception — the overwrite war — now comes with the full winning sequence and the discipline of the return trip. If a machine in your life mysteriously refuses to set up new devices, check this switch before blaming the devices; somebody's forgotten 2023 tweak is probably in there. Spotted something wrong or something missing? Tell me through the contact page and I will fix it. Toggle wisely.