june cumulative improvements knock away their networked printers Many admins statement that installing the most recent. The problem appears to span all typical versions of Home windows and Server and several printers which have been set up and employed in place for a long time. The bug seems to result in a conflict with old (but quite typical) PCL 5 and PCL 6 version 2 motorists on printers which are attached to systems, although the information aren’t clear yet.

Microsoft provides acknowledged a bug within the June patches (it isn’t very clear precisely those) where the USB printer port disappears:

If a USB is connected by you printer to Windows 10 edition 1903 or later, turn off Windows and disconnect or shut down the printer then, when you begin Windows once again the USB printer slot shall not be accessible in the set of printer ports. Windows shall not have the ability to complete any task that will require that port.

This isn’t exactly the same bug.

With that one, installing the cumulative update causes printers mounted on a network to vanish, behave oddly, or even crash the device just.

All the info I see up to now targets the cumulative up-dates and the PCL 5 and PCL 6 version 2 printer drivers. In at the very least some full cases, changing your printing driver to the PCL 6 version 3 driver removes the nagging problem. In all cases, rolling the cumulative upgrade brings back again the printers back.

Rance_Mulliniks, posting on Reddit, describes the outward symptoms:

Publishing sends to spooler also it disappears from the queue rapidly and will not print then. A uninstall and reinstall of the printer and brand-new drivers does NOT fix the problem. Uninstalling KB4560960 fixes it.

Reported medical indications include system freezes also, Excel “messed up totally,” problems with printing to PDF, “when I printing from an Okay station, the stations that may’t print present the work going thru the printing queue (Spiceworks).”

User Groka-NT, posting on Reddit, says this:

Network technician for a Ricoh dealership primarily, here. HPs appears to be hit or miss with this particular presssing issue. Ricoh/Canon/Brother/KM/Kyocera all appear to be experiencing problems.

Specifically, the PCL5e driver fubar is very, and the PCL6 driver for Universal print appears to work on some rather than others, may be in line with the age of the drivers. After a good amount of service calls these last 2 days, I could say PCL5 can not work at all confidently, of driver age regardless. Installing the most recent version of the PCL6 universal driver appear to work *does*. Not a realistic method of servicing a huge selection of clients, but at the very least new clients setup prior to the new patch ought to be okay.

PostScript drivers appear to be working (up to now) and we’ve seen some weird problems with respect to print servers having their print spooler being switched off without warning.

Canons utilizing the UFRII driver don’t yet appear to be showing signs of errors.

This isn’t a fresh bug. Patch Woman Susan Bradley, publishing on the patchmanagement.org mailing list says:

We opened up this case LAST 30 days. In the printer logs we discovered: “Setting up printer driver – failed, mistake program code 0x490, HRESULT 0x80070490. Start to see the event user information for context details” The workaround we discovered (with zero assist from Microsoft I would add) has been to “Install the HP General PCl6  Driver and check out if that ongoing functions.”

The Microsoft assistance personnel had been of zero assist in this full case.  They verified that the printer driver had been having a concern just, clearly they didn’t take this suggestions to the Windows 10 team.

It isn’t at all crystal clear what caused the nagging issue in May, nor what’this month s managed to get much more common.

Like expected, there’s no mention from all inside the associated Knowledge Bottom articles, or even on the Release Information Status page.

We’d notch everything around two common Home windows update problems:

1. Microsoft doesn’t check its mainstream patches in a wide enough selection of configurations, and
2. Problems made through official stations — opened support cases, Suggestions Hub, Microsoft Answers discussion board — drop on deaf ears.

It’s including Déjà vu yet again.

{Join the discussion Join the {conversation|dialogue|debate} on AskWoody.com.