Another possibly important question about your printer connections: You say that two of your printers are on ethernet. Does that mean that they are connected to your router by a cable with a printer connector (B) on one end and an RJ-45 on the other end, or are you just using "ethernet" to refer to a cable with a USB connector at one end and a B connector at the other?
Last edited by Wisewiz; 17 Sep 2021 at 11:57.
Any computer on my home network, wired or WiFi, can print on any of the three printers. None of them are wired through a computer. Computers include a 2012-vintage iMac, an old placeholder laptop running Windows 10, my main computer running Windows 10, a power workstation running Linux, and other computers that I ask the router to let onto the network. None of them care about the state of the other computers. Some or all of them require a driver to be installed for full capabilities.
The problem (as I see it at this moment):
Has to do with the "Point And Print" capability in Windows 10. It has been identified as a threat vector. KB5005565 closes that vector.
https://support.microsoft.com/en-us/...b-6d8e9a302872
My problem setup (and a few others):
Main Computer A - 2 printers connected to Computer A by USB
Computer B - Laptop that connects wirelessly through the router to Computer A to use the connected printers.
Computer C - Desktop that connects with Ethernet through the router to Computer A to use the connected printers.
With KB5005565 installed Computer B will not print to the Computer A printer ending with an error code 0x0000011b. And Computer C will not print - but there is no message - it just doesnt do anything.
Removing KB5005565 off of Computer A fixes everything. All is back to normal.
I also can't 'Add A Printer' on computers B or C from A. Error code on B, No message on C.
Both computers can "see" the printers on computer A - in Devices and Printers, and in Add a Printer).
Both computers can transfer files to and from computer A
Hope that explains it better. I didn't say this was easy!
It seems that ONLY this configuration is problematic, like I said, due to the "Point and Print" function.
I believe I am going to need to find another way to install the printers on B and C to get them to work with KB5005565.
I suspect I will end up needing to install the drivers directly on each machine and then figure out how to route the call to computer A.
Okay, @TV2 and @Motorfingers, you covered it all. To take TV2's example of computers needing to go through another (hard-wired to printer) computer, It seems that if you leave 5005565 on all computers except A and uninstall it on A, all connections should work, for now, until MS patches that patch or replaces it.
In this Tutorial by Brink, it shows how to Add A Shared Printer, the method I have been using and that I used in my recent test.
Add Shared Printer in Windows 10
Option 2, Step 5 is where things go south and the error code comes up.
I believe that is because you are trying to install drivers through Point and Print function and that is being blocked in KB5005565.
My general policy is to connect printers through Ethernet cable when possible, WiFi if not. Since I've always had a Mac and usually have a Linux machine in the house, I've never tried to "share" printers connected by USB to another computer, because it seems to be asking for trouble. Out of Ethernet cable jacks? Ethernet switches are cheap.
Old printers. Not network capable. Problematic logistics (printer not near router - YOU can do more cabling!)
That's the thing with these unannounced changes: the surprise additional work.
I was just reading a post from an IT manager who when he was told "he just had to install the driver software on each PC" complained that he had over 400 PCs to fix. Certainly not welcome news on a Friday.
I'd love to find him a better fix.
[QUOTE=TV2;2297573]This is interesting. Connected to the problem?:
_QUOTE]
I use a shared printer HP1020 connected to my Main PC via USB, I have no problem reaching it and printing from the other PCs on my network.
Did not ask for credentials either.
All my PCs are at build 19043.1237, also have a couple with Development Build Win 11 22458.1000
Quote
