Windows 11 can't add shared printers after KB5127648. Where should I start?

November 18, 2026 4 answers
Asked by 9w+plendrix_482

Windows 11 clients can see printers shared from a Windows Server 2019 print server, but adding them through Settings fails with Error 87. The Point and Print policies appear in gpresult, including the approved server and the administrator driver-install restriction.

Could KB5127648 be involved, or should I focus on the driver and policy setup first?

Answers

b.614!quazelo

Check whether the exact driver package is already in the affected client's driver store. An approved print server doesn't by itself let a standard user install a new driver when RestrictDriverInstallationToAdministrators is enabled. Seeing both policies in gpresult doesn't mean the user can stage a missing package.

As a test, have an administrator stage the matching driver package on one affected client, then try the shared printer again as the user. You can also test with administrator credentials. That may narrow it down without weakening the restriction for everyone.

Reply to this answer
5p+zaldrix_814

I'd test the update theory, but wouldn't call it confirmed yet. Compare affected Windows 11 builds and check when the failures started. On a test machine, removing the update and retrying the same printer could be useful if your organization's patch policy allows it.

A successful rollback would be a clue, not proof of which part of printing broke. Weigh the security impact before leaving an update uninstalled.

2v!kavlixo_594:

Keep the driver package and user account the same between tests if possible. Otherwise it gets harder to tell what changed the result.

Reply to this answer
_t48+vexlano.6

Try connecting to the shared printer through File Explorer instead of Settings on one client. There are reports of the Settings path failing while another connection method works, though that doesn't establish that it's the same issue here.

Reply to this answer
_vexlin.5

Error 87 can indicate an invalid parameter during installation. It doesn't, on its own, establish that the driver was rejected or that Point and Print policy failed. I'd check the relevant print and driver installation logs around the failure before changing policy.

The NTLMv1 theory is also worth treating as unconfirmed. Look for authentication errors before assuming that's the cause.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions