Printing Issues "Driver Update Needed"

[Michael]

I'm on WUfb and 30 days behind too, so all my workstations/servers are currently on the August 2021 patch.

 

From my observations, Microsoft have patched another printer related issue in the September 2021 update, but guidance notes before still apply.

 

I'll put my hands up and admit I haven't tested the September 2021 patch yet, but @FN-GM has above.

[willtech]

I am getting print issues after KB5005568 update on Server 2019.

 

Trying to install a shared printer errors with code 11b. After uninstalling the update and restarting the print server normal function returns.

 

Anyone else getting this?

Edited September 16, 2021 by willtech

[gshaw]

Applied the KB5005568 update on some Win 10 LTSC machines in my office, doesn't appear to have made any difference to the UAC prompts with Konica drivers

 

@FN-GM what printer models and drivers are you running? Type 3 or Type 4?

[Jaan]

Hello,

 

For other reasons we are a couple of months behind on patching. (I know!)

 

Anyway, on a freshly imaged test machine we have updated to 2021-09 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB5005565).

 

Our printers are deployed to users from the print server. So I was expecting to have issues with the drivers installing once this update had been deployed.

 

However, everything on the test machines seems fine. The drivers hadn't previously been installed - it was a clean image.

 

Have I missed something?

 

Thanks

 

You made any registry gpo tweaks surrounding this issue or not?

 

We have done anything apart from fully patch and disable print-spooler all servers except print server and clients. just to reduce the foot print.

 

Only our IT admin team can print if logged in as Admins. I installed the sept update last night on a group of machines..... "no printers"

[FN-GM]

@FN-GM what printer models and drivers are you running? Type 3 or Type 4?

 

I am not 100% sure, I would have to check tomorrow. We have a lot of printers so I would guess both. Does this only impact type 3 or something?

 

You made any registry gpo tweaks surrounding this issue or not?

 

I haven't yet no. I installed all the patches and nothing else. I then tested to see what happens and everything was fine!

[Duranis]

I am getting print issues after KB5005568 update on Server 2019.

Trying to install a shared printer errors with code 11b. After uninstalling the update and restarting the print server normal function returns

Anyone else getting this?

 

Yep server 2012R2 update KB5005613. Stopped users being able to print, stopped being able to install printers with the same 11b error. Removed the update and restarted the server and everything is back to normal. Seen a few work arounds but looks like most are just adding more security issues so far.

[gshaw]

Another weird thing, I can't see the 2021-09 Cumulative Update on WSUS for LTSC (1809) but can for Server, 2004 and 20H2. Any else the same?

[Koldov]

This one...?

 

 

What I don't see occasionally is the SSU, but I guess that's not always needed?

Edited September 16, 2021 by Koldov

[Koldov]

I am not 100% sure, I would have to check tomorrow. We have a lot of printers so I would guess both. Does this only impact type 3 or something?

 

Yes, only Type 3 I think...

 

I've had mixed results, some install fine others don't, some have kept their printers, some have disappeared!

 

Not helped by when this kicked off I changed print server in the summer holidays (from a DC to a VM), and if the computer had installed the updates before getting the new printers... well they didn't get the printers!

[Koldov]

Quite a good explanation...

 

http://n1vacations.com/mcsa15/Type%203%20and%20Type%204%20Printer%20Drivers.pdf

 

So the server gets the 'driver' installed and nothing is done on the client, hence why it's 'safer' I guess, but this means that the client only gets a generic print dialogue box and why some of the extra printer features aren't there?

 

How are people using V4 drivers getting around this?

 

Also, why are there V4 drivers available to install from the manufacturers if they are supposed to be downloaded from Windows Update/WSUS... (I checked on the Kyocera site because I can't find 'KYOCERA TASKALFA 5052ci' on the Windows Update Catalogue)?

 

Also, can I presume all drivers on WU are Type 4 (can't seem to see that stated anywhere)?

[RLR]

A heads up that the September Roll-up might break printing even more. Not much info in the post but might be worth keeping an eye out:

[Norphy]

It definitely does something to break things further. The September 2021 patch was automatically installed on the print server at one of my customers and after that, noone could print. We removed the September patch and things started working again.

 

The error was "Cannot connect to printer, operation failed with error 0x0000011b"

 

All the Point and Print stuff and registry entries were present on the workstation.

[FN-GM]

Yes, only Type 3 I think...

 

@FN-GM what printer models and drivers are you running? Type 3 or Type 4?

 

We are using Type 3 drivers and the printers map ok.

[FN-GM]

A heads up that the September Roll-up might break printing even more. Not much info in the post but might be worth keeping an eye out:

 

It definitely does something to break things further. The September 2021 patch was automatically installed on the print server at one of my customers and after that, noone could print. We removed the September patch and things started working again.

 

The error was "Cannot connect to printer, operation failed with error 0x0000011b"

 

All the Point and Print stuff and registry entries were present on the workstation.

 

It seems like these issues only impact the print server. At least there is something to be thankful for!

[stkidlasaint]

I have applied GPO to trust the printer server like this example, Looks like this is working.

 

 

As per security not keen on following Regedit via GPO. Anyway I can't even find this regedit

 

create the following GPP regedit:

 

Code:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint

 

Value: RestrictDriverInstallationToAdministrators

 

Dword: 0

Registry should look like this on a workstation:

 

[stkidlasaint]

The short version:

 

Leave your Point and Print GPO 'as is' like this example, including your servername.fqdn:

 

[ATTACH=CONFIG]62942[/ATTACH]

 

Create the following GPP regedit:

 

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint

Value: RestrictDriverInstallationToAdministrators

Dword: 0

 

Registry should look like this on a workstation:

 

[ATTACH=CONFIG]62943[/ATTACH]

 

 

I can find that regedit on GPO?

[mrstrong]

trying to catch up on this. Can't you just disable point and print restrictions ? :

 

If you disable this policy setting:

-Windows Vista client computers can create a printer connection to any server using Point and Print.

-Windows Vista computers will not show a warning or an elevated command prompt when users create a printer connection to any server using Point and Print.

-Windows Vista computers will not show a warning or an elevated command prompt when an existing printer connection driver needs to be updated.

[gds64]

From what I've seen, you need to apply the patches to both server and client, or it will introduce the printer connection issues described above.

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-36958

[Koldov]

I can find that regedit on GPO?

 

YOU create the registry entry with that GPP.

 

trying to catch up on this. Can't you just disable point and print restrictions ? :

 

I think that to enable the regedit to allow non-admin printer installs, you HAD to enable point and print.

[mullet_man]

Our 2016 printer has installed the September Cumulative update KB5005573 last night and I've come into chaos this morning most people can't print but some can.

 

Am uninstalling the KB now, google seems to suggest that's the fix.

 

I've got all the settings set as suggested so not sure what the issue is.

 

Hold off installing the Sept KBs if you haven't already applied them to your print servers.

[mullet_man]

Although am currently stuck on 100% "Working on updates"

[Koldov]

I know everybody is all 2016 or 2019...

 

But does anyone know if the 2012R2 Sept update is having the same effect?

 

2021-09 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5005613)

[mrstrong]

I'm deploying printers via a user gpo i.e.

Preferences==>Control Panel Settings==>Printers

new Shared Printer

Action Update

 

so for users who've logged on and got their printers added ok (i.e. drivers installed)

should be ok (as the gpp action is update)? Only issue might be with new logons after the update(s) ? (which I've not approved yet )

Am I right ?

 

edit: No for all Common options e.g.

Run in logged-on user's security context (user policy option) No

Edited September 17, 2021 by mrstrong

[mrstrong]

I can find that regedit on GPO?

 

have a read here:

How to Add, Edit, Deploy and Import Registry Keys through GPO? | Windows OS Hub

[Norphy]

It definitely does something to break things further. The September 2021 patch was automatically installed on the print server at one of my customers and after that, noone could print. We removed the September patch and things started working again.

 

The error was "Cannot connect to printer, operation failed with error 0x0000011b"

 

All the Point and Print stuff and registry entries were present on the workstation.

 

OK, with a couple of completely clean VMs:

 

Server 2016 with one queue, patched to September 2021

Windows 10 1909, patched to August 2021

 

When attempting to connect from the client to a mapped queue on the server, error 0x0000011b. Bringing the client up to 2021-09 makes no odds. Even connecting to a queue with type 4 drivers doesn't make any difference. Pre-installing the printer drivers on the clients makes no odds either. I don't think this issue is with Point and Print

Edited September 17, 2021 by Norphy