question

ManuelHumbertoGaldamezBarrientos-9129 avatar image
19 Votes"
ManuelHumbertoGaldamezBarrientos-9129 asked DarrenWhitehead-4058 edited

Print server and Print Nightmare update

Hi All,

I'm having issues with some Print Servers after running Windows Updates and installed

2021-08 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5005030)

After the update installation I'm getting the error "Connect to printer Windows cannot connect to the printer. Operation failed with error 0x0000011b" and the printer fails to install.

Is there any workaround to keep Print Severs up and running?

I cannot permanently remove the August update, because the Print Nightmare update will come again in Sept Cummulative Update.

I also tried to revert the configurations using:
“Allow Print Spooler to accept client connections” policy
HKEY_LOCAL_MACHINE \Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint.

Nothing worked. I will appreciate any advice.

Thanks,

Manuel

windows-server-print
· 56
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

This just hit us this morning too. 9/15/2021. No one can print to the network printers.
I removed KB5005613 from our server and rebooted the server and that fixed it. Had to do that at all 8 of our branch offices too.
Microsoft updates seem to be more like hackers. Not professional.

9 Votes 9 ·

We had same problem, just affecting to Windows 7 computers. After uninstalling 15/09/2021 updates
(KB5005613, KB5005627 y KB5005563) and a long reboot, computers were able to print again.

6 Votes 6 ·

We did the same thing, on our PRINTER Server, and it works.

2 Votes 2 ·
Show more comments
Baronduke-9697 avatar image Baronduke-9697 JavierPoloCozar-7884 ·

thank you for help . in my case it was necessary to restart the second server which was on 2016. Windows should not launch a security update for our security.

2 Votes 2 ·
steviefaux avatar image steviefaux JavierPoloCozar-7884 ·

Just removed those 3 on our server and now all working.

0 Votes 0 ·

Some of the KBs you removed are cumulative. Printing may have been restored but so was the PrintNightmare problem and other vulnerabilities.

1 Vote 1 ·

Good point, however availability is part of the security triangle. Hopefully M$ will issue a new KB that patches the vulnerability as well as lets users print.

1 Vote 1 ·
38330931 avatar image 38330931 MikePrice-2508 ·

Same issue. Removed that update, and all devices were able to print after the server was rebooted.

0 Votes 0 ·

Currently experiencing this same issue 09/22/2021. Where a Windows Server 2012 R2 Standard can't add/connect to shared printers. "Connect to Printer Windows cannot connect to the printer. Operation failed with error 0x0000011b"

I don't have any of these KB updates mentioned installed, so basically, I can’t use the uninstallation method which seems to be working for everyone. How do I go about fixing this issue if I don’t have these KB installed already?

NB: There are pending updates which include KB5005613

0 Votes 0 ·

I don't have any of these updates installed on my Server 2019 either tried all suggestions so far nothing

0 Votes 0 ·
Show more comments

My 2k8R2 RDS servers could not connect to my 2k12 Std Print server. I removed KB5005623 from my 2k12 printer server and things came back on line.

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

Installation date: ‎2021-‎09-‎26 13:46

Installation status: Succeeded

Update type: Important

A security issue has been identified in a Microsoft software product that could affect your system. You can help protect your system by installing this update from Microsoft. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system.

More information:
https://support.microsoft.com/help/5005623

Help and Support:
https://support.microsoft.com/help/5005623

0 Votes 0 ·

I've got a good one Microsoft may not actually be devising a fix for this but...
Got the above error with a twist. We don't use PointandPrint... All our (I say "all" when things are running smoothly) printers are published using GPO's to targeted computers, not users. Every computer is named in such a way we can identify groups of computers based on location, department and OS. When a new computer is joined to the domain, the computer is added to several groups. One of the groups they are added to are used for multiple policies. The policies are designed to publish as few as one to as many as a dozen printers to that computer. So there's no user interaction when installing a printer. RestrictDriverInstallationToAdministrators - 0 is being used on a case by case basis for people who absolutely must print to keep our business running. Corporate is going to be some pissed with the AD guy because he can't get printers to deploy any more. Not a fun place to be. Never have I seen something like this before. Oh, there's been inconveniences but never a total blockage. I spun up a new 2019 server and started building V4 ONLY queues with still no joy. This is the crap suicides are made of.

5 Votes 5 ·

Today, 16 September 2021, I got the same problem, cannot print to printer on the server. Fortunately, I read this article and then I can assume what was happen to me, is caused by BAD Windows update. Then, I check Updates history, and find one update installed on 15 September 2021 (Security updates KB5005565). So, I uninstall it, and reboot. And, YES, the printer works normally, ... God Bless Us.. Alhamdulillah, Amiin

4 Votes 4 ·

I Can CONFIRM we had the same Problem and nothing would work , even our Tec couldn't figure it out so i got on this Forum and YES The Above answer Solved our Prob , Deleted the Security updates KB5005565 and restarted and bingo , Printer can connect again..

Thanks

2 Votes 2 ·

Uninstalling KB5005565 may work but this is a cumulative update. i may be wrong but you still have the PrinterNightmare issue. Just trading off risk/problem.

1 Vote 1 ·

What do you think is better, to have the inability to print within your organization, or continue to have PrintNightmare vulnerability? It's not a trade-off at all. Businesses need to print to continue their operations. Obviously Microsoft needs to fix the problem properly. You need to uninstall September 2021 cumulative update on all print servers to get them working again.

3 Votes 3 ·

It is also hepled me too! Thnaks!

0 Votes 0 ·

The correct way to fix this may lie in following this flowchart to ensure that remote exploitation of PrintNightmare is not possible while allowing Point and Print
I will update this later with any progress I find in this. If you can, please do not set RestrictDriverInstallationToAdministrators to 0 as this will make you vulnerable.

-thank you

133726-383432-printnightmare-flowchart-v9.png


3 Votes 3 ·

One more note, I would say you should add the RPC changes to this as well.

https://support.microsoft.com/en-us/topic/managing-deployment-of-printer-rpc-binding-changes-for-cve-2021-1678-kb4599464-12a69652-30b9-3d61-d9f7-7201623a8b25

And

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

This is what I primarily mention above and what seems to have triggered an influx of complaints.

1 Vote 1 ·

Awesome, I am building up a guide for my org and will use this.

From what I see most people are getting servers updated then reporting the clients can't print. So they uninstall the servers updates and volia. I'm not fully sure of the clients being unable to print if the server is updated already as well. But the aforementioned issue appears to be the main culprit. This Sept update made an enforcement change on the Jan updates for the Auth protocol of the Print Spooler to the Server/Client relationship. So the value is being set from the default of 0 as non enforcement to 1 with the Sept updates. I haven't run into this problem directly but was following this thread due to the Admin install prompt issue which is unrelated to the Sept updates issue. The unfortunate situation here is Microsoft has poorly communicated the Print Nightmare fixes. But they have slowly updated their primary Point and Point document to detail the needed changes. They have yet to deal with the V3 GPO issue, although mentioned now doing a manual compare of the users driver files. Alas. I set the Auth protocol to 0 through GPO and updated my server. Then installed the latest updates on a client and server. No issues printing. I tested on a non updated client and no issues printing as well. This is due to me changing the enforcement level for the Auth change. I suspect when I change the Auth level back to 1 as Enforced per Microsoft then those client machines won't print because they are not up to date.

Soooooo confusing. Your flow chart is very helpful!

0 Votes 0 ·

Credit goes to Will Dormann twitter @wdormann for this flow chart, I'm just sharing it here.

1 Vote 1 ·

IIf you really want really answers for this issue:
https://support.microsoft.com/en-us/topic/kb5004442-manage-changes-for-windows-dcom-server-security-feature-bypass-cve-2021-26414-f1400b52-c141-43d2-941e-37ed901c769c

Read also
https://support.microsoft.com/en-us/topic/managing-deployment-of-printer-rpc-binding-ch[…]e-2021-1678-kb4599464-12a69652-30b9-3d61-d9f7-7201623a8b25

After the later link enforcement with septermber updates all MAC-, Linux- and windows-clients printing ability was disabled.
When client tries to communicate unsufficient authentication method the server responsed access denied with unproper error message.
There might be a firewall configurations to prevent proper communications in environments where only 445/TCP is enabled, some organizations doesn't like to approve unintended high ports communications with TCP nor UDP.
MS has now triggered something that no-one was prepared to deal with and haven't shared enought documentation how to properly configure these services to communicate how they want them to communicate

.When only 445/TCP open, it is not enough ?
Should we open the high ports, is there any answer? which TCP or UDP to establish the correct communication?
IIn documentations of printing services there is ability to configure your print server to communicate only with 445/TCP, but this breaks now with the newest security update...
So you should enable high ports 49152-49158 tcp ???
Do we need to enable those documented udp ports also with 445 only enabled servers? that have the registry tweak to support non udp communications?

2 Votes 2 ·

I especially like the part about "If you find issues during testing, you must contact the vendor for the affected client or server software for an update or workaround before early 2022."

yeah just push these issues out to the manufacturers, that sounds like a good idea....

I have had issues here with Brother printers, however they are not as severe. Some application calls seem to work while others fail. Our issues appear to be related to our Azure Active Directory in some way, but I haven't gathered any evidence for this yet. I believe it is a permissions issue, as I've experienced no problems with administrator accounts.

1 Vote 1 ·
Show more comments
MikePrice-2508 avatar image
0 Votes"
MikePrice-2508 answered TrevorJHAAGSMA-3184 commented

This just hit us this morning too. 9/15/2021. No one can print to the network printers.
I removed KB5005613 from our server and rebooted the server and that fixed it. Had to do that at all 8 of our branch offices too.
Microsoft updates seem to be more like hackers. Not professional.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Seems like KB5005568 also gives error 0x00000011b or Error #283

0 Votes 0 ·
87321688 avatar image
0 Votes"
87321688 answered TrevorJHAAGSMA-3184 commented

Uninstall kb5005565 to solve the problem

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Or KB5005568

0 Votes 0 ·
Bart-Hoofd avatar image
0 Votes"
Bart-Hoofd answered Bart-Hoofd commented

Same issue here; Windows 2012 R2 printservers and Windows 7 and 10 clients.
Our Windows 10 clients responded well to the policy based remediation, our Windows 7 clients did not.

I was unable to clear the problem unless I uninstalled KB5005627, KB5005563 and KB5005613.

Does anyone have any official feedback from Microsoft about this issue?

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I have to correct my initial findings: apparently Windows 10 is not fixed as well. It appears the client OS is not the issue, just the Windows 2012 R2 server.

0 Votes 0 ·
CagriSen-1475 avatar image
0 Votes"
CagriSen-1475 answered Smueck commented

We have just joined the party!

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

We warmly welcome you!

0 Votes 0 ·
Marek4597 avatar image
1 Vote"
Marek4597 answered TheNerdCat-1286 published

Hello, Guys,
can you pls somebody help me. I have this problem in small company (after update KB5005565) where is printer shared between users on workstations. I cant this update remove, it can´t. I try this.
I make list of packages with: dism /online /get-packages /format:table then select afected update for remove command dism /online /remove-package /packagename: etc
But this fail with error 0x800f0905
Actually i cant print a not found any solutions for this :-(
Manny thanks. Marek

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I install the KB5005565 yesterday night and this morning when i came to office users started to call in to say cannot print with errors.

so the only thing i did was to uninstall the KB on my print server, reboot and behold, everything back to normal. Microsoft really wants us as IT Pro to work to our death... lol. so my suggestion to you is uninstall the KB. its the only way now so far as i can see till Microsoft come up with workarounds or a better patch.

other servers are also installed with the patch but since they are not print servers there is no issues.

0 Votes 0 ·
Marek4597 avatar image Marek4597 LukeWalker-7933 ·

Hi,
i can simply uninstall KB5005565 over Control Panel/Add/Remove Programs on Client, but can´t. OS say error :-(

0 Votes 0 ·

Try on Computer (in administator)

reg add "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint" /v RestrictDriverInstallationToAdministrators /t REG_DWORD /d 0 /f

restart computer

Try to add printer or print

if work, apply on you all computer Company

0 Votes 0 ·
GlennKaas-4216 avatar image
0 Votes"
GlennKaas-4216 answered KeithBoddy-5543 published

Having similar issues.
Client pc's can't connect to network printers. When trying to add via UNC path the message "cannot connect to printer" error code: 0x0000011b

I've tried adding a GPO: Computer Configuration > Administrative Templates > Printers
Set the the Point and Print Restrictions Group Policy setting to "Enabled".
"When installing drivers for a new connection": "Do not show warning and elevation prompt".
"When updating drivers for an existing connection": "Do not show warning and elevation prompt".

KB5005565 and KB5005613 are not installed on the client pc or domain controller (when print server is located).

Not sure what to do for the clients, if anyone has any ideas let met know :)

· 7
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,
this is exact my problem but in small Company, without AD, Print Share between Users :-(
This Sucks

0 Votes 0 ·

Try this on computer

reg add "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint" /v RestrictDriverInstallationToAdministrators /t REG_DWORD /d 0 /f

restart computer

try to add printer / or print

if this work

Apply for all computer in your Company

1 Vote 1 ·

I mean i'm looking for a GPO solution. I dont really feel like adding regkeys to 2500 pc's

0 Votes 0 ·
Show more comments

Try on Computer (in administator)

reg add "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint" /v RestrictDriverInstallationToAdministrators /t REG_DWORD /d 0 /f

restart computer

Try to add printer or print

if work, apply on you all computer Company

0 Votes 0 ·

Try on Computer (in administator)

reg add "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint" /v RestrictDriverInstallationToAdministrators /t REG_DWORD /d 0 /f

restart computer

Try to add printer or print

if work, apply on you all computer Company

0 Votes 0 ·

this didn't work for my situation.

1 Vote 1 ·
gaggelis avatar image
0 Votes"
gaggelis answered

What a bad day.

I just removed the update from our Print Servers, and all clients are able to print now.

I have a much of GPOs to deploy various printers. I noticed the event on a testing machine, that printer was not deployed.

Nice to mention that, my GPOs that was Per User, was working fine.
All other GPOs, that was Per Machine couldn't print.

Thanks all for this emergency post.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Joakimc-5502 avatar image
0 Votes"
Joakimc-5502 answered

I think this is confusing. An updated server 2016/2019 server and windows 7 client. All updated windows 10 clients can print. But the windows 7 one can't.

I have not done any point and print restrictions yet. But not sure if it will help the few windows 7 ones

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

TheAlanMorris avatar image
1 Vote"
TheAlanMorris answered TheAlanMorris edited

@Joakimc-5502
I am not expecting Microsoft to be patching Windows 7 with the updated protocol methods but I could be wrong.

Add the Windows LPD service to the print server

On the Windows 7 client systems create a local printer using a Standard TCP/IP targeting the IP or hostname of the print server.
132727-image.png


The print system issues an SNMP call which will fail to the LPD service on the print server. You will land on this page. Be patient, 60 to 60 seconds. Select Custom
132857-image.png


Configure the port as LPR. The Queue Name is the printers Share name. Make it easy on yourself and do NOT have spaces in the share name. You must select LPR Byte Counting Enabled.

132883-image.png




Finish adding the printer with the proper driver. When you send the test page, you will see the job owner as "USER (IP of client system)

This solution should completely bypass the update from yesterday.



image.png (17.3 KiB)
image.png (24.9 KiB)
image.png (20.4 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ChunshengZhao-9499 avatar image
0 Votes"
ChunshengZhao-9499 answered

I spent two days on this patch, and many employees complained that the printer was unavailable. There is no patch to solve this problem now? Or what is the standard solution? Only some computers can be solved by RestrictDriverInstallationToAdministrators=0.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.