IT technician helping fix Windows printer driver that deletes itself after reboot

Joe B.

Expert ★★★★★ 27,853 satisfied customers

Specialities: Windows print spooler & drivers, shared printers & print servers, Group Policy & Point and Print hardening, Windows 10/11 security patches

Windows print driver deletes itself after reboot — Group Policy, Point and Print and driver block fixes

Technician avatar Technician
Hi! We can definitely sort out a Windows print driver that deletes itself after reboot.

To stop the printer driver from disappearing every restart, I need a quick picture of the setup:
• Is this a locally installed USB/network printer or a shared printer from a Windows print server?
• Which Windows version is on the client — Windows 10 or Windows 11, and fully patched after the PrintNightmare updates?
• After reboot, does the entire printer queue vanish from Devices and Printers, or does the printer stay but with a generic driver / error?
• Any specific errors in Event Viewer → PrintService or in Print Management like “policy blocked driver” or “driver package deleted”?

Once I know if we’re dealing with a Point and Print restriction, a RestrictDriverInstallationToAdministrators policy, or a corrupt driver package, I’ll walk you through a safe way to keep the driver installed without breaking security.
Customer
It’s a shared printer from a Windows Server print server. Clients are mostly Windows 11 Pro, domain joined. Users can add the printer and it works until reboot. After the restart, the printer completely disappears from the list and the print driver is gone from Print Management. In Event Viewer I see messages about Point and Print restrictions and sometimes a note that a driver was removed because of policy. This started after recent Windows security updates.
Technician avatar Technician
That matches what I’ve seen since Microsoft hardened printing after PrintNightmare.

In modern Windows, policies like RestrictDriverInstallationToAdministrators and stricter Point and Print restrictions control who can install and use shared printer drivers. If a driver doesn’t meet the new rules, Windows might still let the user install it once, then remove the print driver at reboot as a security cleanup.

Common reasons a Windows print driver keeps uninstalling after restart:
• The shared printer uses an older Type 3 / kernel-mode driver that’s blocked by policy on Windows 10/11 clients.
• The client has RestrictDriverInstallationToAdministrators = 1, so non-admins can’t keep drivers installed from untrusted print servers.
• The Package Point and Print – Approved servers policy is enabled and the print server hosting that queue isn’t on the trusted list.
• A security product or hardening baseline cleans non-compliant driver packages out of the driver store at startup.

We’ll first confirm what kind of driver you’re using and which policy is actually removing it, then we can either switch to a compliant package-aware driver or adjust the print driver installation policy so the driver survives reboot.
Customer
The printer is an older HP LaserJet on a 2016 print server using a Type 3 driver. Clients are Windows 11 23H2. In the System log I see entries that the HP printer driver was deleted because of a policy. We do have some security GPOs from our MSP, so I’m guessing RestrictDriverInstallationToAdministrators or something similar is enabled. I’m okay changing the driver or policy, but I don’t want to completely turn security off.
Technician avatar Technician
Perfect, that gives us a direction.

Here’s the high-level plan:
1) Confirm how the driver is registered (package-aware / v4 vs legacy Type 3).
2) Check which Windows print driver policies are active on the client (Point and Print & RestrictDriverInstallationToAdministrators).
3) Either move to a package-aware driver on the print server or tweak the policy so trusted servers can install drivers without them being purged at reboot.

Step A — Check the driver type on the print server
• On the print server, open Print Management → Drivers and find the HP driver used for that queue.
• Note whether it’s listed as Type 3 – User Mode or Type 4, and whether the “Packaged” column shows Yes or No.
• If it’s Type 3, Packaged = No, Windows 10/11 sees it as a legacy non-package-aware driver and applies stricter rules.

Step B — Check Point and Print policies on a client
• On an affected Windows 11 PC, run gpedit.msc (if you’re allowed) or ask whoever manages GPO to review:
  – Computer Configuration → Administrative Templates → Printers → Point and Print Restrictions
  – Computer Configuration → Administrative Templates → Printers → Package Point and Print – Approved servers
• Also check the registry key HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Printers\PointAndPrint for RestrictDriverInstallationToAdministrators.

We’ll keep security in place but allow your trusted print server so Windows doesn’t keep deleting the print driver at startup.
Customer
On the print server the driver shows as Type 3 – User Mode, Packaged: No. On a Windows 11 client, Point and Print Restrictions is enabled and set to only allow connections to specific servers, but our print server’s FQDN isn’t in the list. I also see RestrictDriverInstallationToAdministrators = 1 in that registry path. So it sounds like every reboot the policy is enforcing and the printer driver gets removed.
Technician avatar Technician
Exactly — you’ve hit the classic combo:
• Legacy, non-packaged Type 3 shared printer driver.
• RestrictDriverInstallationToAdministrators = 1 and Point and Print Restrictions locked down.

Windows lets the install happen initially (often when an admin is involved), but the next Group Policy refresh or reboot says “this driver doesn’t meet the rules” and the print driver is deleted automatically.

You’ve got two main, safe options:
1) Move to a package-aware / Type 4 or Class driver for that printer queue on the server so it complies with the newer policies.
2) Keep the legacy driver but scope the policy so that your specific print server is trusted for driver installs.

For stability and future upgrades, I usually recommend first seeing if HP provides a package-aware v4 or “Class” driver that works on the print server, then only loosening policy as much as needed.
Customer
I can try a different driver, but it’s an older model and the last HP package is still Type 3. If we can’t switch to a Type 4, how do we adjust the Point and Print driver policy so Windows 11 stops purging the driver while still keeping things relatively secure? Most users aren’t local admins.
Technician avatar Technician
Good question. You don’t have to turn everything off — just tell Windows that your print server is trusted for Point and Print.

On the GPO that applies to those Windows 11 machines:

Step C — Configure “Package Point and Print – Approved servers”
• Set the policy to Enabled.
• In the list, add your print server’s FQDN (for example, PRINT01.yourdomain.local).
• This tells Windows that users are allowed to install drivers from that server, even with RestrictDriverInstallationToAdministrators turned on.

Step D — Tighten Point and Print Restrictions
• In Point and Print Restrictions, keep it Enabled but set both “When installing drivers for a new connection” and “When updating drivers for an existing connection” to either “Show warning and elevation prompt” or, if you’re comfortable, “Do not show warning or elevation prompt” only for your approved servers.
• Make sure the “Users can only point and print to these servers” list matches the same trusted print server names.

With this in place, Windows is much less likely to remove shared printer drivers after reboot, because the driver source is now explicitly trusted instead of treated like a random remote host.
Customer
That makes sense. So I leave RestrictDriverInstallationToAdministrators = 1, but add our print server to the approved servers list and set Point and Print Restrictions correctly. Do I need to manually reinstall the printer driver afterward, or will it stick automatically once those GPO changes apply? Also, what about machines that already lost the driver?
Technician avatar Technician
Right — the policy change just stops Windows from auto-deleting the printer driver in future; it doesn’t recreate queues that are already gone.

Step E — Re-install the shared printer once GPO is updated
• After the new policy is applied (you can force a refresh with gpupdate /force if you have rights), re-add the shared printer on one test machine via \\printserver\queue.
• Confirm the driver installs without extra errors, then reboot the PC at least twice.
• Check that the printer queue and print driver stay installed after reboot and no new “driver package deleted due to policy” events appear.

Once the test client is stable, repeat the add-printer step for the rest of the machines that lost the driver. Since the underlying issue — the policy driver block — is now scoped correctly, the driver should no longer remove itself on startup.
Customer
That sounds doable. One more thing: our security vendor suggested just flipping RestrictDriverInstallationToAdministrators to 0 on a couple of problem machines to test. Is it a bad idea to leave that off permanently if it stops the Windows print driver from deleting itself? Or should we really stick with the “approved servers” approach?
Technician avatar Technician
Great question — this is where security vs. convenience comes in.

Setting RestrictDriverInstallationToAdministrators = 0 absolutely can stop the printer driver from being blocked by policy, but it also relaxes protection Microsoft added for PrintNightmare-style vulnerabilities. It makes it easier for users (or malware) to install unexpected drivers from remote servers.

That’s why Microsoft and most security guides recommend:
• Leave RestrictDriverInstallationToAdministrators = 1 (the secure default).
• Use Package Point and Print – Approved servers and Point and Print Restrictions to explicitly trust only your legitimate print servers.

You can temporarily set the value to 0 on a lab machine to confirm it’s really the policy that’s deleting the driver, but for production I’d stick with the “trusted servers” pattern so you stop Windows from deleting print drivers after reboot without opening the door to unwanted drivers.
Customer
Understood. I’ll talk to our MSP about adding the print server to approved servers and leaving the restriction on. If that still doesn’t work, is there any fallback? For example, could we use a universal print driver or a local TCP/IP port instead of a shared printer so Windows 11 stops removing it?
Technician avatar Technician
Yes, you’ve got a couple of fallback options if policy + shared queue still misbehave:

• Use a universal / class driver: Many vendors and Windows itself provide package-aware “Universal Print” or IPP Class drivers that are friendlier to Windows 10/11’s security model. Installing the printer with one of those drivers often avoids policy-based removal.
• Install as a local TCP/IP printer: On small sites, you can sometimes avoid Point and Print entirely by adding the printer directly via a Standard TCP/IP port using a compliant driver. Group Policy or scripts can still deploy it, but you’re no longer pulling drivers from a remote print server.

Both options reduce your dependence on the stricter Point and Print restrictions. But before you redesign the whole print setup, it’s usually worth getting the Group Policy driver rules right and seeing if that stops the Windows print driver from deleting itself after reboot for the existing shared queue.
Customer
Great, that explains why the print driver kept uninstalling after restart and what we should change. I’ll get the GPO updated with the approved server and test a universal driver if needed. If we hit more weird policy errors, I’ll come back to chat. Thanks for the step-by-step walkthrough!
Technician avatar Technician
Anytime! Quick recap: if a Windows print driver deletes itself after reboot, it’s usually not a random glitch — it’s Group Policy or Point and Print restrictions enforcing newer security rules. Confirm the driver type on the print server, then configure Package Point and Print – Approved servers and Point and Print Restrictions so your trusted print server is allowed to deliver drivers. Only drop the RestrictDriverInstallationToAdministrators setting for testing, not as a permanent fix. If you’d like someone to double-check your GPOs, registry, and printer drivers live, just start a chat with an expert.

Quick answer: the accepted fix

Accepted fix when a Windows printer driver deletes itself after reboot: on the print server, use a package-aware driver where possible, then on Windows 10/11 clients configure Package Point and Print – Approved servers and Point and Print Restrictions so users can only install drivers from your trusted print server. Keep RestrictDriverInstallationToAdministrators enabled for security, re-add the shared printer on a test client, and confirm the print driver persists across multiple restarts without policy deleting it.

Why Windows removes printer drivers after reboot

Most cases where a Windows shared printer prints fine once and then disappears after a reboot are caused by new security defaults, not random corruption. After the PrintNightmare vulnerabilities, Microsoft tightened policies so non-administrators can’t silently install or update remote printer drivers. When those policies (especially RestrictDriverInstallationToAdministrators and strict Point and Print restrictions) detect a driver that doesn’t comply, Windows can purge the printer driver package from the client at startup.

Legacy Type 3, non-packaged drivers, unsigned or cross-signed drivers, and drivers coming from untrusted print servers are frequent triggers. The client will download and use the driver at first, but once Group Policy or security baselines reapply, Windows logs an event saying the print driver was deleted due to policy and the shared printer queue vanishes. Understanding whether the driver is package-aware and whether the print server is on the “approved servers” list is key to stopping the cycle of reinstall → reboot → driver gone.

How to test if your policy fix for disappearing printer drivers worked

Once you change the GPO or driver, you want to be sure Windows won’t delete the printer driver again after restart. A simple test flow:

First, apply the updated Point and Print and Package Point and Print – Approved servers policies and verify the registry on a test machine reflects the new settings. Then, remove any broken shared printer connections, re-add the printer from the trusted print server, and confirm that the correct driver version shows under Print Management → Drivers on the client.

Next, perform two or three full reboots with some time in between, watching the Microsoft-Windows-PrintService logs for any warnings that a driver package was deleted due to policy. If the printer queue and driver remain after several restarts and a normal Group Policy refresh cycle, your fix has likely worked. If the print driver still disappears after reboot, you may need to revisit which servers are approved, whether the driver is packaged, or consider a universal or IPP Class driver approach instead.

Windows print driver deletes itself after reboot — quick troubleshooting tips

Treat it as a policy issue, not just a corrupt driver — adjust trust and driver type first.

Fast path: on the print server, check if the driver is Type 3, Packaged = No. If so, see whether a package-aware or universal driver is available, or plan to trust your server via policy. On Windows 10/11 clients, keep RestrictDriverInstallationToAdministrators enabled but configure Package Point and Print – Approved servers and Point and Print Restrictions so users can only install drivers from your own print servers. Re-add the shared printer on a test device and make sure the printer driver no longer uninstalls itself after restart.

Disclaimer: This information is AI-generated and intended for general guidance only. For changes to production Group Policy, print server configuration, and security baselines in your environment, please consult a verified expert or follow your organisation’s change-control process.

Getting Started Is Easy

Ask for help, 24/7

Members get round-the-clock access to certified IT and print server Experts for Windows printer drivers deleting after reboot, Point and Print policy errors, Print Spooler issues, and more.

Expert will respond in minutes

We match you with a specialist who knows Windows print driver policies, Group Policy and Intune baselines, and typical reasons a shared printer driver keeps disappearing, so you can stabilise printing quickly.

Save time & money

Stop rebuilding printers after every reboot or rolling back updates. Get a clear, policy-aware fix for Windows print drivers that uninstall themselves so your users can print reliably again.

FAQ

Why does my Windows printer driver delete itself after reboot?

On modern Windows 10/11 builds, security policies and Point and Print restrictions can remove printer drivers that don’t meet hardening rules. If the driver is non-packaged, kernel-mode, or comes from a print server that isn’t listed as trusted, Windows may allow a one-time install and then delete the driver package at restart or Group Policy refresh to reduce attack surface.

How do I stop a shared printer driver from disappearing each restart?

First, check the driver type on the print server and use a package-aware or universal driver if possible. Then, on client machines, keep RestrictDriverInstallationToAdministrators enabled, but configure Package Point and Print – Approved servers and Point and Print Restrictions so users can only install drivers from your trusted print server. After that, re-add the printer and confirm the driver stays installed across multiple reboots.

Can Group Policy or Point and Print restrictions remove printer drivers?

Yes. Policies like Point and Print Restrictions and the registry value RestrictDriverInstallationToAdministrators control whether non-admins can install or update printer drivers from remote servers. If a driver install doesn’t comply with those policies, Windows can block the install, break the connection, or delete the driver package during the next reboot or policy refresh.

Is it safe to disable RestrictDriverInstallationToAdministrators to fix driver removal?

Turning RestrictDriverInstallationToAdministrators off may stop Windows from blocking printer drivers, but it also relaxes protections Microsoft added to mitigate vulnerabilities like PrintNightmare. For most environments, it’s safer to leave the restriction enabled and instead configure trusted print servers and package-aware drivers. If you do turn it off for troubleshooting, limit that change to test devices and restore the secure default afterward.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant
5 Tech Support Specialists are online right now.