New Windows 10 KB5006670 update breaks network printing

Broke on one of my clients... had to remove update on 3 computers and everything started working fine. Printer was an HP OfficeJet 8600.

You can see the printer on the network, but if you try to add it it "fails to connect" with a 0x000??? something code. Removed update and restarted, could re-add printer, driver installed and everything was back on its way.
 
Broke on one of my clients... had to remove update on 3 computers and everything started working fine. Printer was an HP OfficeJet 8600.

You can see the printer on the network, but if you try to add it it "fails to connect" with a 0x000??? something code. Removed update and restarted, could re-add printer, driver installed and everything was back on its way.
Dont forget to run wushowhide to hide that update and stop it reinstalling
 
OK, I'll bite. Why do none of the countless bad printer updates over the past several weeks not been an issue for you?

I haven't had any calls, either. While these issues are not truly isolated incidents they're not global bugs, either. They depend directly on factors specific to the given ecosystem involved. If you don't have that same, or very similar ecosystem, you don't have the issue.
 
OK, I'll bite. Why do none of the countless bad printer updates over the past several weeks not been an issue for you?
That's the $1,000,000 question... because it's got me rather astonished too.

The only people I know that have had issues within my professional contact circle were guys dumb enough to let clients use an ancient HP 1020 USB crap printer, that's shared out.

Printer shares are rather not useful anymore because it means a desktop going down makes a group of people not print. When you can buy a $40 box on Amazon that's a print server to make that old laserjet a network printer... why isn't it a network printer?

That's the only divide I can think of... every single printer I have in service is a WIRED network printer. They simply work, all day every day.

Now I know the HP Laserjet 1020 is broken... that's a crap driver, for a crap printer, that HP had no business shoveling out the door. So I'm thinking that if you're having issues, it's because the printer drivers you have are garbage. I know a ton of people with label printer issues... and they're doing the magic box thing to fix them.

This thing: https://www.amazon.com/StarTech-com...009KH5Q,B00U9UDSH8,B0996NQ673,B07RHWB9FL&th=1

Connected to a Dyno label printer sorts those out... but I don't have any label printers in service anymore either. Heck the only inkjet I have out is a plotter! So mostly I'm working with HP Laserjets.
 
OK, I'll bite. Why do none of the countless bad printer updates over the past several weeks not been an issue for you?
They are only affecting SHARED USB Printers on peer to peer networks. Does not seem to matter what type of printer Zebra Barcode, Kyocera Mono Laser, Brother all in one inkjets
 
All these printer updates the last couple months, never got a call. Of course I don't have anyone really with USB shared printers for this one at least.
 
I’ve had a couple of clients affected by these updates now.
One was a peer to peer network with a brother printer connected by Ethernet but shared from the main “server” to the other two workstations.
The main pc was still printing ok.
Just switched the other two over to print directly instead.
The other two clients are domain based networks with their multi function printer/scanner/copier machines plugged into Ethernet and shared from the server. One Canon and one Ricoh.
Had to uninstall the update to get them going again.
 
I have been working on this problem in my office however I am more the IT liaison and we have to get the IT department to make any GPO & Server changes so this has been a problem for any reimaged desktops to re-add the printers we have had to deal with prompts for admin rights to reinstall drivers for all our existing setups but that is manageable comparatively do have no way to add the server printer w/ the proper drivers, which are required for functions like duplex printing, and limits our abilities and functions.
 
@DRPCNZ said:

They are only affecting SHARED USB Printers on peer to peer networks

Not exactly. We've seen it happen with Canon IR and Ricoh Copiers in two offices we support. Of course, those are not USB printers. Also had it with an HP Plotter for an Architectural Client also not a USB shared printer. All of these networks I speak of are Domain environments with Print Servers.

We did have one Win 10 computer (Workgroup) having issues printing to a USB Shared Printer but that's the only one. I think that was from the latest Windows Printer Security update.

Full disclosure: We still have a lot of Server 2012 out there an it seems they are affected the most. But you can read about all the other 2016 and 2019 Servers out there are on reddit that are affected too.
 
The printers I am seeing problems with are all connected via ethernet they are HP LaserJet Pro model printers that have been configured on a proper print server.
 
@Sky-Knight said:

That's the $1,000,000 question... because it's got me rather astonished too.

Dude, I thought in your initial response you were trying to be sarcastic. That's why I bit on your comment. Good to know you have no idea either! :) Perfect, we're all in the same boat and no one knows why we're sinking and what the hell to do. Just like working in IT should be.
 
I have two Windows 10 PCs that are point of sales with a USB attached STAR receipt printer. No sharing. It still prints, but there is a 45 second delay everytime they print a receipt since the update. KB5006670 will not uninstall because Windows says the update is cumulative and required to run Windows.

EDIT: I think there may be a DISM command to uninstall, but I have not tried that yet.
 
Dude, I thought in your initial response you were trying to be sarcastic. That's why I bit on your comment. Good to know you have no idea either! :) Perfect, we're all in the same boat and no one knows why we're sinking and what the hell to do. Just like working in IT should be.
Yep! Though I don't use USB printing anywhere... So that's my guess?

I have Ethernet connected laser printers directly connected to workstations. I have the same connected to a server and use GPO's to push them out.

I'd love to know specifically what it is, because something I'm doing must be working, and if we could confirm that all of us here would know which of my insane habits is apparently inline with with MS wants us to be doing.
 
@alluseridsrejected said:

I have two Windows 10 PCs that are point of sales with a USB

What OS are they running, Windows 10 (Home) or Windows 10 Pro? We've had no issues removing that update and hiding it off of Windows 10 Pro computers that are peer to peer. Wonder since yours are POS you can't uninstall the update regardless of version. I don't know man. But waiting 45 seconds for a POS to print something ain't good at all.

You should simply be able to open cmd as administrator and run: wusa /uninstall /kb:5006670. That should remove it.

Keep in mind, don't reboot that computer when it tells you. You wanna first run the Hide Utility (wushowhide.diagcab) from Microsoft before rebooting or that little ******* may come back on ya at reboot.
 
What OS are they running, Windows 10 (Home) or Windows 10 Pro? We've had no issues removing that update and hiding it off of Windows 10 Pro computers that are peer to peer. Wonder since yours are POS you can't uninstall the update regardless of version. I don't know man. But waiting 45 seconds for a POS to print something ain't good at all.

You should simply be able to open cmd as administrator and run: wusa /uninstall /kb:5006670. That should remove it.

Keep in mind, don't reboot that computer when it tells you. You wanna first run the Hide Utility (wushowhide.diagcab) from Microsoft before rebooting or that little ******* may come back on ya at reboot.
They are Windows 10 Pro peer to peer and neither wusa or gui work. The gui has no uninstall button when selecting kb5006670. wusa fails with the this update is cumulative and required to run Windows message.
 
Back
Top