Until Microsoft issues a fix, the only reliable way around the issue is to temporarily uninstall last week’s updates. The updates causing the trouble are KB4560960 for Windows 10 and Server 1903 (build 18362), 1909 (build 18363), and KB4557957 for the 2004 version (build 19041) released on 9 June. However, the local print spooling issue seems also to affect users printing to network printers. That’s not clear but the issue overlaps with an earlier problem already acknowledged to affect users printing through a local USB port.
No date for a fix has been set but the company said it was “working on a resolution” and would provide an update as soon as possible. It can also affect users printing to file formats such as PDF. The print spooler might throw an error or close unexpectedly when attempting to print, and no output will come from the affected printer. But other problems were reported too, ranging from application crashes and even the blue screen of death (BSOD), which hints at a deeper issue within Windows itself.Īfter several days of confusion, Microsoft has acknowledged the issue, describing it in the following terms:Īfter installing this update, certain printers might fail to print. Numerous printer makers seemed to be affected.
Windows cannot print due to a problem with the current printer setup. A typical error message ran something like:
It’s hard to tell how many people have encountered the latest glitch but it was enough to register on Microsoft forums as well as multiple threads on that great bell-weather, Reddit. Problems after monthly updates are not unusual, but the numbers tend to be limited to subgroups of users.
Solving this issue completely by automating all of this would help a lot I commented on Jan 3Īlso, we should perhaps move this issue and discussion to the BFC github repo.Windows 10 updates released as part of last week’s Patch Tuesday appear to be making life hard for some printer users.
This took me at least 30 minutes given the many websites and YouTube tips around this that are confusing and/or wrong (example: "Q: How to program BetaFlight? A:Press boot button" is incorrect in many cases)
Both of these modes require a different driver and both of these drivers can only be installed/configured when both of these modes have been "shown" to Windows. I don't consider myself a beginner on Windows/drivers/programming, but to me it was unclear, when I started using a quadcopter & BetaFlight, that the FC can be in two modes. I also don't think it is something useful to learn to all BetaFlight users. I think that the fully automated method of driver installation is the way to go, because that would be most user friendly. Instead the BFC Installer would need to do the inf-file modifications and possibly also registry modifications itself, replacing the Win/STM default driver with the "WinUSB" driver. Both requires the bootloader device being connected. Downloading and running Zadig or ImpulseRC DF is not a solution. The BOOTLOADER USB device interface is slightly different matter. For the USB VCP and CP210x drivers, you only need to download and make the files available in the right places, Windows PnP will then do the final installation when the device is connected. Please also remember the two different procedures needed. Hi all commented on Jan That sounds as a very reasonable solution, having options for the user to bypass the driver installations. However, I think it would be good if there was still an option for the user to re-do or repair the driver installations.
In that case, the bypass checkbox could be pre-set, or driver install part completely hidden. The BFC Installer could/should first of all check if all those driver issues has already been done.
That sounds as a very reasonable solution, having options for the user to bypass the driver installations.