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

GET/eSCL/ScannerStatus/HTTP/1.1" printing unexpectedly – Windows

I have an HP computer and a Kyocera Ecosys M2540dw printer

The following did not work for me.

1. Open Settings.
2. Click Bluetooth & Devices.
3. Click Printers & scanners.
4. Scroll down until you get to the "Related settings" category. ...
5. Click the Advanced tab.
6. Remove the check from Show informational notifications for local printers.
7. Click Apply → OK.

In addition, if you have an HP computer, open Services and STOP  the HPPrintScanDoctorService

Then open Task Scheduler, go down to Task Schedular Library/ HP / HP Print Scan Doctor

Select Printer Health Monitor, then from the dropdown Action menu, select disable

Select Pinter Health Monitor Logon, then from the dropdown Action menu, select disable

Thank you, William R. Till for your posting!!!

I was so happy because on April 14, 2023, after an update, my HP Printer Laser Jet M553 started acting properly again. I had no more continual pages being printed with “get/ escl/scanner status http http/1.1 Host : localhost”. The honeymoon ended with your most current update on 5/12/23 because it is back to printing pages everyday. This proves to me it is a Microsoft problem not a printer issue. I am extremely disappointed with Microsoft because I would like to hear from them that they are working on a fix for this obvious “bug”. I know I would feel better if they would reach out and let us know they are working on it instead of leaving everyone in limbo like this. I wish I could go back to Windows 10 because I never had any problems with that version. Since this is a Microsoft forum I hope they are listening!

I have the same problem with my Epsom. My daughter has the same problem at the university where she teaches. They have four different printer manufacturer types. All have the exact same problem and tech support has to restart their nodes on the network daily to get anything to print. And they are using twice the amount of paper as usual because of the error message.

My one workaround is to shut off the printer IMMEDIATELY after I have printed something. If you wait even 5 or 10 minutes, the printer starts making odd noises like it thinks it should print, then stops, starts making noises and then finally prints the two line error message at the top of a page.

At that point, I have reboot my pc.

This is a Windows 11 error. I have reinstalled the drivers, run diagnostics, you name it. My printer is fine as far as Epson is concerned but printing is a problem.

I have the same issue here too - my Epson XP-900 printer keeps printing this GET /ESCL/ScannerStatus HTTP/1.1 message every time I turn my PC on pretty much every time I wake it up from sleep. It is such a waste of paper and ink and from a search on Google is clearly happening to a lot of people and a lot of different types of printers.
Mine only started doing this since my PC did an upgrade to windows 11 it is clearly a MS Win issue.

I have done all the suggested fixes, I cant run on wireless so it must be USB connected.

Come on Microsoft - fix the bug now and save the wasted paper ---> think of all the trees that have been lost because of this and get on with it!

The one thing that works for me is to press the ✓ (OK does this) on the printer screen and then turn off the printer completely. Just clearing the ✓ doesn't work. You have to turn off the printer.

If you are printing several items one after another, you do not have to turn off your printer. That sequential printing is fine.

It appears to me that, after a print job is completed and there are no more print jobs in the queue, Windows is not informing the printer that the print queue is empty and telling the printer to go back to its idle state. It seems as if the printer is saying "I'm here, where's my next job?" In other words, the printer is waiting for the next job and after a period of time, it sends that error message. Windows has not "closed" the print queue or whatever action is needed to have the printer return to idle state rather than waiting.

That is evidenced by the printer, after your last print job, making odd noises. My theory is that, getting no response from the operating system, it tries to print but there is nothing in the queue. It keeps at that for a while and then prints the error message.

It's definitely a Microsoft problem since it seems to affect a large number of different printers.