G'day from Australia.
On the 16th June 2020, 2 updates were successfully installed on my computer, viz:
- Microsoft Edge Update for Windows 10 Version 1909 for x64-based systems (KB4559309).
- Update for Windows 10 version 1909 for x64-based systems (KB4497165).
Since then, my Brother MFC-490CW printer (USB connection) will not print from the computer. I have looked at every "supposed" remedial solution that I could find online. I have pulled out all the cords. Uninstalled, then re-installed the printer. And, according
to the Brother Installation Diagnostics Tool, all facets of the installation were completed successfully. Successfully, but with one exception; I could not print a test page.
Despite trying everything I could find . . . EVERYTHING thus far has be of no use. My printer STILL wont print from the computer.
So, to you techno wizards at Microsoft, please note before you tell me to check all of my connections, update the drivers, re-install the device, check to see that the printer has been set as the default printer, point me towards the control panel, check
to see if I'm on a metered connection, etc; etc; I have already done all of these things. So please, give me something new.
Here is the dilemma. My printer appears in the Device Manager. It appears in the Control Panel. It appears as the default printer in the Settings Menu. It appears in the Task Bar of the computer, and is showing itself to be "ready". Yet, when I click on
print, the document briefly appears in the print queue, then disappears. NOTHING appears on the facing screen of my printer to suggest that it is trying to receive data from the computer. If I open my printer by clicking on the printer icon, I can scan a document
which is in the printer with a simple mouse click. But I cannot print a document, email, etc. from the computer.
Yes, the printer is getting on in years. But up until yesterday (16th June 2020) when those updates came through, it was working fine.
I want my printer back, and I want it back quickly. So PLEASE, can you find me a solution to whatever it was in that last lot of updates that caused this problem.
Cheers for now,
Wayne