Brother Printer Has an Error When Connecting by USB to a

This practical guide walks through brother printer has an error when connecting by USB to a, explains the main requirements, and highlights common issues that may appear along the way.

• Detects your Brother printer when it is connected to the computer with a USB cable.
• Change your Brother printer settings.
• Connect more than one Brother printer via USB.

In addition, Brother also provides a list of applications and tools that may have problems connecting via USB:

• Device Settings Tool
• Paper Size Setup Tool
• Distributed Print Tool
• Special ID Setting Tool
• Wireless Setup Wizard
• P-Touch Editor 5.4
• Update Software
• Transfer Manager
• Transfer Express
• Template Settings
• Printer Setting Tool

This issue is currently under investigation and it affects both Ink Jet and Laser printers. Here are the affected printers:

DCP-B7500D, DCP-B7535DW, DCP-J1050DW, DCP-J1100DW, DCP-J1140DW, DCP-J1200W(XL), DCP-J572DW, DCP-L2531DW, DCP-L2535D , DCP-L2535DW, DCP-L2550DW, DCP-L2550DW, , DCP-L3551CDW, DCP-L5500D, DCP-L5600DN, DCP-T220, DCP-T310, DCP-T420W, DCP-T510W, DCP-T520W, DCP-T710W, DCP-T720DW, DCP-T820DW, DCP-T825DW, HL -B2000D, HL-B2080DW, HL-L2310D, HL-L2335D, HL-L2350DW, HL-L2351DW, HL-L2370DN, HL-L2375DW, HL-L2376DW, HL-L2385DW, HL-L2386DW, HL-L-L23 , HL-L3230CDN, HL-L3230CDW, HL-L3270CDW, HL-T4000DW, MFC-B7715DW, MFC-J1010DW, MFC-J1300DW, MFC-J2330DW, MFC-J2730DW, MFC-J3530DW, MFC-JFC-J39( ), MFC-J4440DW, MFC-J4540DW(XL), MFC-J491DW, MFC-J5330DW, MFC-J5730DW, MFC-J5845DW, MFC-J5930DW, MFC-J5945DW, MFC-J6530DW, MFC-J6545DW, MFC-J6730DWFC -J690DW, MFC-J6930DW, MFC-J6935DW, MFC-J6945DW, MFC-J890DW, MFC-L2710DW, MFC-L2713DW, MFC-L2715DW,MFC-L2716DW, MFC-L2730DW, MFC-L2750DW, MFC-L2751DW, MFC-L2770DW, MFC-L2771DW, MFC-L3710CW, MFC-L3735CDN, MFC-L3745CDW, MFC-L3750CDW, MFC-L3770 L5755DW, MFC-L5900DW, MFC-L6700DW, MFC-L6900DW, MFC-L8690CDW, MFC-L8900CDW, MFC-L9570CDW, MFC-T4500DW, MFC-T810W, MFC-T910DW, MFC-T920DW, MFC-T920DW, MFC

According to Brother, temporarily to solve the problem, users should switch to using other connection types if available.

Users have started reporting this problem on forums but not many. Hopefully this isn't a common problem. Microsoft fixed a similar issue on Windows 10 earlier this year.