Print job goes into queue and instantly disappears with nothing being printed

Anonymous
2017-11-16T20:31:55+00:00

For some reason my system has stopped working correctly with one of my printers. The system sees the printer as being connected and available and when I print the job goes to the print queue. However it then instantly disappears and nothing is printed. Can someone advise?

The printer with the problem is an Epson Stylus Photo 1290. The printer was working a couple of days ago and the only thing I can think that has happened is that there was an automatic windows update.

I am running Windows 10 Pro 64 bit version 15063.726

I have tried: starting and stopping the print spooler, uninstalling the driver, running the trouble shooter, rebooting ...

Any help welcome.

Thanks,

Chris.

Note: 28/11/2017 - I have had an email from Epson who confirm the problem is caused by a change introduced by Microsoft. As a result they have no fix for the problem and say that if I wish to continue using the latest version of Windows 10 then I need to buy a new printer or wait for Microsoft to introduce a change (which may never happen). This is hugely disappointing and is also not very environmentally friendly.

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2020-02-28T19:18:13+00:00

Based on your post on printing, I think that the Microsoft Virtual Agent can help you troubleshoot your issue. It'll walk you through the right troubleshooting steps based on the specific problem you're facing.

Please let us know if this solved your issue.

Was this answer helpful?

3 people found this answer helpful.
0 comments No comments

78 additional answers

Sort by: Most helpful
  1. Anonymous
    2020-06-25T22:35:40+00:00

    UPDATE:  I discovered my printer was having the same problem on 6/24.  I went in and looked at the Updates and found "Update for Microsoft Windows (KB4560960)" had showed back up again on 6/22; plus the "Security Update for Adobe Flash Player" was there again on 6/19.  This time, I simply Uninstalled only the (KB4560960) Update and left the Adobe Flash one alone.  The printer started working again.  But today, even though it's working, I see that same update is back again on 6/25!  Maybe they finally fixed it.  IDK, but we'll see the next time I try to print anything.  If not, I guess I'll have to just keep Uninstalling that faulty update, Restarting the computer, then printing what I need each time until they finally do get it fixed.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-06-12T14:52:43+00:00

    Thank you KRolson. You're a star. I removed the Flash update - no joy. But following that track I then removed the Windows update (sorry, I didn't note the KB number but there were only 2 and it wasn't security one) and hey presto! we are printing again. But that's damn near 24 wasted hours. Thanks a lot Microsoft.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-06-12T12:09:34+00:00

    Go to settings - update & security - view update history - uninstall updates

    This will bring you to a screen that lists all the recent updates

    Right click on the Security Update for Adobe Flash Player update and click uninstall.

    I then uninstalled the driver for my printer and re-installed this from the Brother website.

    Restarted and printer worked again! Hope that helps.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-06-12T01:01:44+00:00

    I tried the troubleshooter posted on the thread - it did not work. I have a Brother MFC-495CW which was working fine up until today. The problem is as described at the beginning of this thread. I feel that it was a bad system update that caused the problem. Just have to figure out a way to roll them back and see which one. Microsoft if you are listening please help!

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments