Possible printer issue with KB5005565

seems like there are some printer issues with the newly released KB5006670 update

so KB5006670 doesn't fully solve the printer issues with the older KB5005565 update

All my network printers are borked again. I have RpcAuthnLevelPrivacyEnabled set to zero and they wont print

This is beyond the pale!!! What are those idiots at Microsoft doing?!

steve108 said:

Only the print server PC needs that registry setting, not the client PCs. Did you do that PC too? It should do any harm if you did the clients too.

The RpcAuthnLevelPrivacyEnabled setting is zero on all computers that have shared printers (that is three of the four in the lab), but I have done it to the 4th printer as well.

The problem I had is that even with RpcAuthnLevelPrivacyEnabled set to 0, I still could not print to network shared printers. I uninstalled KB5006670 (see Erpster4's post above) and its all working again.

I have now paused all updates on all computers until Nov18. I know this exposes our system to a potential hacker, but that's just "potential". Allowing KB5006670 to install again will bork my business for certain. I simply do not trust Microsoft updates any longer.

What I would like to know is more information about the vulnerability itself. What is meant by "installing network printers with admin privileges". I was logged in as admin when I installed all the shared printers, so I don't get why I am even having this problem. Also, because I have only a small a small number of staff, I don't have separate accounts for each person. All the computers are permanently logged into the Admin account all the time, so everyone is printing with admin privileges.

smartcooky said:

The RpcAuthnLevelPrivacyEnabled setting is zero on all computers that have shared printers (that is three of the four in the lab), but I have done it to the 4th printer as well.

The problem I had is that even with RpcAuthnLevelPrivacyEnabled set to 0, I still could not print to network shared printers. I uninstalled KB5006670 (see Erpster4's post above) and its all working again.

I have now paused all updates on all computers until Nov18. I know this exposes our system to a potential hacker, but that's just "potential". Allowing KB5006670 to install again will bork my business for certain. I simply do not trust Microsoft updates any longer.

What I would like to know is more information about the vulnerability itself. What is meant by "installing network printers with admin privileges". I was logged in as admin when I installed all the shared printers, so I don't get why I am even having this problem. Also, because I have only a small a small number of staff, I don't have separate accounts for each person. All the computers are permanently logged into the Admin account all the time, so everyone is printing with admin privileges.

Sorry, I didn't catch they MS introduced a totally new problem this month as @erpster4 posted. Apparently the old fix no longer applies.

I presume you've seen post #12 in link below about replacing a new printer spooler dll with the one from last month. A band-aid workaround until they break it again next month:
KB5006670 - Network Printer Problems Again This Month - Windows 10 Support

steve108 said:

Sorry, I didn't catch they MS introduced a totally new problem this month as @erpster4 posted. Apparently the old fix no longer applies.
I presume you've seen post #12 in link below about replacing a new printer spooler dll with the one from last month. A band-aid workaround until they break it again next month:
KB5006670 - Network Printer Problems Again This Month - Windows 10 Support

Yeah, I saw that. However, as I already have things running, I'll stick with what I have done.

On the weekend, I might go in and do the dll thing just to see if it works.

I'd also be interested to hear opinions on suggestion in post #37 in that link

"...the clients need RestrictDriverInstallationToAdministrators registry value set to 0 Registry location HKEY_LOCAL_MACHINE \Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint"

After reading this topic, I used show or hide updates - wushowhide.diagcab to hide KB5006670 until a resolution is found.

I think I have same/similar issue but networking is below my altitude for flight.
I have a Dell laptop with 20H2 and KB5005565 (also now showing this machine is w11 ready).

Ethernet from ADSL modem direct to Brother 2370 b/w laser.
This laptop wireless to router.
All "used" to work but have been away from here for nearly 6 weeks.
KB5005565 installed during that period.

Now cannot get to print but just get "error" without further feedback.
Have logged on to browser page for printer and was able to change admin password.
Browser printer page (ip address) shows network active with MAC address matching the one in the Win10p device properties page.
Printed test page from printer control panel just for good measure.
Will print from direct usb cable ... but that is still a struggle and seem to have to install another version of the printer.

Is current forum advice (for 'non' network admins/wizards) to wait for something better than KB5006670 ?
Or roll back KB5005565 ?

EDIT:
Just tried the regedit advice without success.

END OF EDIT:

Pavl said:

I think I have same/similar issue but networking is below my altitude for flight.
I have a Dell laptop with 20H2 and KB5005565 (also now showing this machine is w11 ready).

Ethernet from ADSL modem direct to Brother 2370 b/w laser.
This laptop wireless to router.
All "used" to work but have been away from here for nearly 6 weeks.
KB5005565 installed during that period.

Now cannot get to print but just get "error" without further feedback.
Have logged on to browser page for printer and was able to change admin password.
Browser printer page (ip address) shows network active with MAC address matching the one in the Win10p device properties page.
Printed test page from printer control panel just for good measure.
Will print from direct usb cable ... but that is still a struggle and seem to have to install another version of the printer.

Is current forum advice (for 'non' network admins/wizards) to wait for something better than KB5006670 ?
Or roll back KB5005565 ?

EDIT:
Just tried the regedit advice without success.

END OF EDIT:

Do you have a print server PC that all printing has to go through or what?

I have KB5006670 installed and print directly from PCs to network printers (no print server PC involved) and just confirmed printing still works fine for that case - which is of course different from the case of having a print server PC in the equation and the main purpose of this thread).

Just wanted to clarify this difference as the terms "networked printer" and "networked printing" aren't specific enough to identify printing via a print server vs no print server/direct PC-to-printer printing.

Thank you steve108

Single printer, single ethernet cable from adsl router to printer.
Only method of printing is from wireless laptop through home network and router.
No other equipment in the path.

Device manager shows ... Microsoft IPP Class Driver and an ip address/WebServices/Device
Devices Printers shows .. make/model and a web page link (which is functional and correct to printer)
Connection = Standard, Currently Connected, MAC address, unique ident and IP address.
IP address matches within WebPage link and "IP address" but with suffixes :80 and %20.

(Same setup in use for years with XP/w7p with a colour laser that got fried this year with an electrical "event")

Hope that is enough info for anyone else in same boat.