According to the company, the bug causes Windows 10 to show duplicate copies of printers installed on a device, commonly with a similar name and the suffix “Copy1”. Also, applications that refer to the printer by a specific name cannot print a document. The update also affects the normal printer usage and normal printing operations may be interrupted, resulting in failure of printing operations. The Redmond giant says it is working on a new update to address the problem in a future update. Meanwhile, users who are experiencing issues can use the Feedback Hub to file a report and try temporary workarounds that might help resolve the issue:
Open the Settings app, navigate to “Bluetooth & devices”, and select “Printers & scanners” If there appears to be a duplicate installation of an existing printer, such as with suffix “Copy1”, confirm if printing works for this printer. This printer should operate as expected. If there is a need to use the original printer installation and not the duplicate, right-click the duplicate printer, select “Printer properties” and select the “Ports” tab. Observe the port in use. Open “Printer properties” on the original printer and select the “Ports” tab. From the list displayed, select the port option in use by the duplicate printer. If this original printer works normally, the duplicate copy printer can be removed.
If the issue still persists, Microsoft recommends attempting the following steps:
Update the print driver for your device. For guidance, see Install the latest driver for your printer. If you already have the latest driver, consult the printer Manufacturer’s web site for any device firmware updates If you are still having issues, uninstalling and reinstalling your printer might help. Turn off your printer and disconnect any cables Open the Settings app, navigate to “Bluetooth & devices”, and select “Printers & scanners” Select the affected printer and select the “Remove Device” option Restart your device Turn on your printer and reconnect it to your device
Currently, Microsoft is investigating the issue and will provide an update when more information is available. According to the Windows Health Dashboard, the affected platforms are Windows 10 21H2, 21H1, and 20H2 (including Windows Server version 20H2).
