About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
A Windows PC cannot download a printer driver from the print server, and its logs show events such as 4098 or 8192 with error 0x80070bcb, or event 215 in the print service log. Microsoft's page ties this set of events to one cause: "These events may be logged due to Point and Print Restrictions." Its resolution is to set the Point and Print Restrictions policy to Disabled.
That resolution loosens a restriction, so confirm the events first, record the current policy, and back up the Group Policy Object (GPO) before you edit it. The event page does not discuss the security effect of disabling the policy, but a separate Microsoft page does, and it carries a caution. KB5005652 (CVE-2021-34481) says that Windows updates released August 10, 2021 and later "will, by default, require administrative privilege to install drivers", and that the registry value RestrictDriverInstallationToAdministrators, when set to 1 or not defined, "will override all Point and Print Restrictions Group Policy settings and ensures that only administrators can install printer drivers from a print server using Point and Print". It also says: "be very careful when using a value of zero (0) because doing that makes devices vulnerable". Where that value is 1 or not defined, which is the default, the registry value decides, so changing the Point and Print Restrictions policy alone will not remove the administrator prompt. Where the value is 0, the Point and Print Restrictions settings are among the mitigations KB5005652 lists, so disabling the policy lowers protection. Whoever owns security decides whether to make the change, and it starts on a test group of PCs.
What the error means
Microsoft describes Point and Print, on its Windows protected print mode page, as "a feature that allows users to connect to a remote printer without providing drivers". The event ID page lists events that it says go with "a Windows machine's inability to download a driver from a print server". The event page does not explain the policy in detail.
The events, with the sources and wording the page shows:
| Log | Source | Event ID | Description (page wording, abbreviated) |
|---|---|---|---|
| Application | Group Policy Printers | 4098 | A computer preference item did not apply, failed with error code '0x80070bcb The specified printer driver was not found on the system and needs to be downloaded.' |
| Application | Group Policy Printers | 8192 | A user preference item did not apply, with the same error code and text |
| System | Microsoft-Windows-TerminalServices-Printers | 1111 | Driver required for the printer is unknown. "Contact the administrator to install the driver before you log in again." |
| System | 23 | Printer failed to initialize because a suitable driver could not be found | |
| System | Microsoft-Windows-PrintSpooler | 22 | Failed to upgrade printer settings for the printer driver, Error: 1801 |
| System | Microsoft-Windows-SpoolerWin32SPL | 1 | The print spooler failed to import the driver downloaded from the server, error code 800f0242; "This can occur if there is a problem with the driver or the digital signature of the driver." |
| Microsoft-Windows-PrintService/Admin | Microsoft-Windows-PrintService | 215 | Installing printer driver failed, error code 0x23f, HRESULT 0x8007023f; a second event 215 shows error code 0x0, HRESULT 0x80070705 |
| Microsoft-Windows-PrintService/Admin | Microsoft-Windows-PrintService | 808 | The print spooler failed to load a plug-in module, error code 0x7e |
Event 1111 comes from the TerminalServices-Printers source, and the event page does not say which machines log it. It does not say which of these events appears first, or how they relate to one another.
Two of the events help you tell who is affected. Event 4098 is logged when a computer preference item in a Group Policy Printers setting fails, and event 8192 when a user preference item fails. Both carry the same error code, 0x80070bcb, with the text "The specified printer driver was not found on the system and needs to be downloaded." Event 4098 adds "This error was suppressed." and event 8192 adds "For more information, see trace file." The event page does not say which policy path each event points to, so use the events only to tell whether a computer item or a user item failed, then read the policy in both places.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Point and Print Restrictions policy blocks the driver download (computer setting) | Events above on affected PCs | Policy setting under Computer Configuration / Administrative Templates / Printers |
| The same policy in the user setting | The same events for a user; event 8192 is a user preference item failing, which does not by itself show the policy path | Policy setting under User Configuration / Administrative Templates / Control Panel / Printers |
| Problem with the driver or its digital signature | Event 1 from SpoolerWin32SPL with 800f0242 | Event 1 text on the client; the driver package on the server |
| A plug-in module the spooler cannot load | Event 808 with error 0x7e | The DLL name in the event's description |
The event page says these events "may be logged due to Point and Print Restrictions". The driver-or-signature sentence is part of the wording of event 1 itself.
Prove the cause before changing anything
These steps only read. On an affected PC, find which events are present, and when.
Get-WinEvent -FilterHashtable @{ LogName='Application'; Id=4098 }
Get-WinEvent -FilterHashtable @{ LogName='System'; Id=1111 }
Get-WinEvent -FilterHashtable @{ LogName='Microsoft-Windows-PrintService/Admin'; Id=215 }
The Get-WinEvent page shows -FilterHashtable @{ LogName='Application'; StartTime=$Date; Id='1003' }, which is the form used here. Run each query on the affected PC, because event logs are local to the machine that wrote them.
Then record what policy the PC is receiving. gpresult needs an output option, and /h writes an HTML report. Create C:\Temp first if it does not exist; these commands write two files there.
gpresult /scope computer /h C:\Temp\gp-computer.html
gpresult /scope user /h C:\Temp\gp-user.html
Open both reports and look for the Point and Print Restrictions setting and the GPO that supplies it. Note the GPO name and whether the setting is Enabled, Disabled or Not configured.
Example (illustrative): at contoso.com.au, a GPO named Printers-Lockdown applies Point and Print Restrictions to all PCs. New staff laptops cannot add \\ps01\Reception-MFP from the print server ps01; event 4098 shows 0x80070bcb on each. The gpresult report shows the setting under Printers-Lockdown, so the cause is the policy and not the server.
Fix
The event page's resolution: "Configure the Point and Print Restrictions policy to Disabled." It names two paths: Computer Configuration / Administrative Templates / Printers, and User Configuration / Administrative Templates / Control Panel / Printers. It adds that the User Configuration policy "has been deprecated but is still available for backwards compatibility with legacy OS's" and that "It is generally recommended to configure both policies to 'Disabled' for uniform behavior across all clients."
Step 1: save the GPO. The Backup-GPO page says the backup directory and GPO must already exist, so create C:\GpoBackups first. On a domain controller or a management PC with the Group Policy module:
Backup-GPO -Name "Printers-Lockdown" -Path C:\GpoBackups -Comment "Before Point and Print change"
The Backup-GPO page shows Backup-Gpo -Name TestGPO -Path C:\GpoBackups -Comment "Weekly Backup". Keep the output, which holds the backup Id. Also record whether RestrictDriverInstallationToAdministrators is set on a test PC:
reg query "HKLM\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint" /v RestrictDriverInstallationToAdministrators
The key path is the one KB5005652 gives in its reg add example. If the value does not exist, reg query reports an error instead of a value; KB5005652 treats a value that is not defined as 1.
Then make a test copy of the GPO and back the copy up, because the copy is what you edit first:
Copy-GPO -SourceName "Printers-Lockdown" -TargetName "Printers-Lockdown-Test"
Backup-GPO -Name "Printers-Lockdown-Test" -Path C:\GpoBackups -Comment "Before Point and Print change"
The Copy-GPO page shows Copy-GPO -SourceName "TestGpo1" -TargetName "TestGpo2". In Group Policy Management, link the copy only to a test organisational unit.
Step 2: change the policy.
Disruptive step: this removes the Point and Print restriction on every PC and user the GPO reaches, and where the registry value is 0 it lowers a protection added for CVE-2021-34481 (KB5005652, above). Do not change the registry value to 0 as part of this; KB5005652 warns against it. Decide with the person who owns security, and make the first edit on the test copy. Back-out: restore the backup of the GPO you edited, using the Id from its Backup-GPO output in place of BackupIdGuid:
Restore-GPO -BackupId BackupIdGuid -Path C:\GpoBackups
Then run gpupdate /force on the PCs. The Restore-GPO page says -BackupId restores "a specific backup", which lets you pick the right one when several are in the folder.
On the test copy, edit the setting in the Group Policy Management Editor: set Point and Print Restrictions to Disabled under both paths above. Edit Printers-Lockdown itself only after the test result and the security owner's decision.
Step 3: apply it on a test PC.
Disruptive step: gpupdate /force reapplies all policy on that PC, not only this setting. Back-out: none needed for the command; undo the policy change with the restore step above.
gpupdate /force
The gpupdate page says the command forces "a background update of all Group Policy settings, regardless of whether they've changed". For settings that need a new sign-in, the page describes /logoff, which "Causes a logoff after the Group Policy settings are updated". Risk: /logoff signs the user out, so use it only when they have saved their work.
If event 1 or 808 is the only event. The event page's cause for those is not only the policy. For event 1, the driver or its digital signature may be wrong; for 808, the spooler cannot load a named plug-in module. The event page gives no fix for either beyond the policy change. Record the driver name and DLL from the event text and raise them with the driver's maker, rather than changing the policy again.
Confirm the fix
- On the test PC, add the shared printer again from
\\ps01. It should install without a driver error. - Run the
Get-WinEventqueries again, with a start time after the change, and confirm no new 4098, 8192, 1111, 23, 22, 1, 215 or 808 events. - Rerun
gpresultand confirm the setting now reads Disabled.
What to watch afterwards
- New devices that join the domain: the policy applies to them as soon as they receive it.
- The GPO backup. Keep it until the change has been accepted by whoever owns security.
- Any later GPO edit by another administrator that sets the policy back to Enabled; the events return if it does.
Read next
Related articles you may want next.
- Troubleshooting"Windows couldn't connect to the printer" and error 0x00000709 when users reach a print server by an aliasPrinters fail with 'Windows couldn't connect to the printer' or 0x00000709 through a DNS alias. Prove it, then apply Microsoft's DnsOnWire fix safely.Read article
- HostingClipboard, drive and printer redirection: choose the channels users needA practical policy and pilot checklist for RDP clipboard, local files and printers, including restrictive-setting precedence and client-specific support.Read article
- HostingMoving printers and scanners with a line-of-business applicationKeep printing and scanning working when business applications move to hosting. Inventory devices, drivers, queues and file destinations, then test everyday staff workflows.Read article
Risks and limits
These commands have not been run or lab-tested.
The event page is a Microsoft support article for "Supported versions of Windows Server" and lists the events without explaining the policy's options or what each one allows. It says disabling the policy is the resolution, and does not say anything about the effect on security, on other printer-related policies, or on clients that are not domain members. KB5005652 (a Microsoft support page that shows no date) says there is "no combination of mitigations that is equivalent to setting RestrictDriverInstallationToAdministrators to 1". Disabling the policy is a security decision for the owner of that risk. Do not apply it everywhere; use the test organisational unit first, and check the current Microsoft pages before you decide.
Sources
- Event ID's with point and print restrictions — Microsoft Learn, page dated 2026-02-12, accessed 20 November 2026
- More information on Windows protected print mode for enterprises and developers — Microsoft Learn, page dated 2025-07-17, accessed 20 November 2026
- KB5005652: Manage new Point and Print default driver installation behavior (CVE-2021-34481) — Microsoft Support, date not shown, accessed 20 November 2026
- Get-WinEvent — Microsoft Learn, date not shown, accessed 20 November 2026
- gpresult — Microsoft Learn, page dated 2024-11-01, accessed 20 November 2026
- gpupdate — Microsoft Learn, page dated 2023-02-03, accessed 20 November 2026
- Backup-GPO — Microsoft Learn, date not shown, accessed 20 November 2026
- Restore-GPO — Microsoft Learn, date not shown, accessed 20 November 2026
- Copy-GPO — Microsoft Learn, date not shown, accessed 20 November 2026
This article was originally published on .