GET /eSCL/ScannerStatus HTTP/1.1The question is how do I stop it.

It's been over a year since you posted...and it's still a problem. I just bought a new computer with Win11 and my Epson ET2803 printed just fine for awhile but now it's started doing the same thing. Massive ink and paper loss. Annoying.

A year and they still have not fixed the problem.

My solution is to pull the paper out until I need to print.

But that doesn't solve the print head clicking back and forth.

BTW, I have subscribed to Tech Support through Office Depot. They have no clue how to fix this nor are they willing to try.

Complete waste of money...

____________________________________

Ok. I went to Epson, followed the instructions to connect by WIFI. That worked...except when I went to print, nothing happened ,,,,they didn't say I had to change the printer setup manually to not be connected to USB but to Epson network. Once I figured that out...and it was just by chance....and made the change...the maintenance program ran a troubleshoot and found the unprinted documents, printed them, and now it works. Hopefully no more scanner status error reports.

This seems to have fixed the issue the issue for me also, thank you! Keeping my fingers crossed that it stays fixed...

I agree with you that this is a very important issue and Microsoft should deal with it.

My HP Omen computer works great and one day I will either figure out why it's operating system is looking for a scanner update when my HP 6978 printer is off line.

There seems to be a connection with the printer function in the set up.

When I look at the HP printer in the setup screen, the Epson printer goes crazy with 5 or 6 2-line printing on the same page.

Thanks again for your help.

Microsoft has to fix this.

Jim

Jim,

I am sorry that didn't work for you. I am over 24 hours now and it still works so I am holding my breath. I have been dealing with it off and on for over 2 years now. I had it fairly bad in the beginning where it would kick the pages out randomly throughout the day whenever the computer woke the printer up, whether I was printing or not and it would either be one or 2 lines or several pages full of the same lines. Then I found a solution on one of these forums here in MS forums and it worked for a few months. I wish I could remember what the solution was and I can't find it since. I have been googling this issue for months now and finally last week I saw where MS owned up to this as their issue in October of 2023 and in december they stated they are currently "working on it" . Based on the fact that I have had this issue for over 2 years, I am thinking the laserprinter that has the issue will die before they solve it. The first few times I contacted MS regarding this in the beginning, they were stating it was an HP issue. So I LIED and said I had an Epson (I have 3 HP printers) and they said that they had only records of it occuring with HP printers so I would need to contact HP...that is when I KNEW they knew what was going on and were just throwing stuff at the wall to see what sticks. Why we as consumers are forced to deal with only Microsoft is beyond my level of reasoning. I would love it if someone would put out a competitive product. I would heartily pay extra to ditch MS simply because they update something and then never fix the issues and blame it on someone else. The issues I had with Windows 11 upgrading from 10 was insane. Deleted an entire UPS shipping data base of close to 10k customers shipping histories...gone...poof...even top level UPS techs who spent hours and days on my computer could not get the data base back. Deleted. What a joke.

At home, I have 2 Epson printers and an HP. The error occurs on all of them. My idiot's solution of turning off and then on works. My problem happens when I get pulled away and forget to turn off the printer. However, on Mondays, I run a bridge tournament using a Canon printer. I do not think the error occurs on that. I'll test it and see. I know that I have it turned on from the get go and print results, etc., only at the end. So the printer is sitting idle for hours without generating the error.

To be continued...