• jobs stuck in print queue

    From micky@NONONOmisc07@fmguy.com to alt.comp.os.windows-11 on Fri Feb 6 15:50:41 2026
    From Newsgroup: alt.comp.os.windows-11

    jobs stuck in print queue

    I have two print jobs that continue to show on the print queue, though
    they are both labeled "printed'. Neither has come out of the printer.

    One from yesterday, one from 3 days ago. One printed by Eudora, one 2
    pages out of 4 of a pdf file, printed by Firefox**.

    I'm pretty sure the wifi printer was on when I printed them, but I found
    it off this morning. I turned it back on. I refreshed the print
    spooler, I restarted the print spooler, I resumed all he print jobs. I
    paused all the pring jobs, and I again resumed all the print jobs.

    I've run out of ideas.

    **This one I printed twice before and each time they disappeared.
    Nothing came out of the printer and the one time I checked, the print
    queue was empty, a few days ago. I had printed all 4 pages the day
    before, but then I was trying to print only the first 2 pages.
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Print Spooler Solution@invalid@invalid.invalid to alt.comp.os.windows-11 on Fri Feb 6 22:26:17 2026
    From Newsgroup: alt.comp.os.windows-11

    On 06/02/2026 20:50, micky wrote:

    I've run out of ideas.


    Have you tried deleting the print job from the spooler? Try that and let
    us know what happens. It's best to start with the simplest solution first.





    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From micky@NONONOmisc07@fmguy.com to alt.comp.os.windows-11 on Fri Feb 6 21:48:15 2026
    From Newsgroup: alt.comp.os.windows-11

    In alt.comp.os.windows-11, on Fri, 6 Feb 2026 22:26:17 +0000, Print
    Spooler Solution <invalid@invalid.invalid> wrote:

    On 06/02/2026 20:50, micky wrote:

    I've run out of ideas.


    Have you tried deleting the print job from the spooler? Try that and let
    us know what happens. It's best to start with the simplest solution first.

    Then will I have to print it again? For one of the two things, I don't remember what I printed.
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Graham J@nobody@nowhere.co.uk to alt.comp.os.windows-11 on Sat Feb 7 08:40:48 2026
    From Newsgroup: alt.comp.os.windows-11

    micky wrote:

    [snip]

    Then will I have to print it again? For one of the two things, I don't remember what I printed.


    It can't be important then ...
    --
    Graham J
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsQ==?=@winstonmvp@gmail.com to alt.comp.os.windows-11 on Sat Feb 7 02:27:32 2026
    From Newsgroup: alt.comp.os.windows-11

    On 2/6/2026 1:50 PM, micky wrote:
    jobs stuck in print queue

    I have two print jobs that continue to show on the print queue, though
    they are both labeled "printed'. Neither has come out of the printer.

    One from yesterday, one from 3 days ago. One printed by Eudora, one 2
    pages out of 4 of a pdf file, printed by Firefox**.

    I'm pretty sure the wifi printer was on when I printed them, but I found
    it off this morning. I turned it back on. I refreshed the print
    spooler, I restarted the print spooler, I resumed all he print jobs. I paused all the pring jobs, and I again resumed all the print jobs.

    I've run out of ideas.

    **This one I printed twice before and each time they disappeared.
    Nothing came out of the printer and the one time I checked, the print
    queue was empty, a few days ago. I had printed all 4 pages the day
    before, but then I was trying to print only the first 2 pages.

    The usual printer manufacturer recommended method for clearing an orphan
    or problem print job from the print queue.

    Services.msc
    Stop Print Spooler service
    Navigate to spool folder(C:\Windows\System32\spool\PRINTERS)
    Delete the contents
    Start Print Spooler service

    Retry Print(if necessary)
    - if it still doesn't print when other documents of the same file
    type do print, it's likely the specific document or the program used to
    tell the printer to print the document.
    --
    ...w-i|#-o-#-n|#
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From micky@NONONOmisc07@fmguy.com to alt.comp.os.windows-11 on Sat Feb 7 11:55:27 2026
    From Newsgroup: alt.comp.os.windows-11

    In alt.comp.os.windows-11, on Sat, 7 Feb 2026 02:27:32 -0700, ...wi+o#n+ <winstonmvp@gmail.com> wrote:

    On 2/6/2026 1:50 PM, micky wrote:
    jobs stuck in print queue

    I have two print jobs that continue to show on the print queue, though
    they are both labeled "printed'. Neither has come out of the printer.

    One from yesterday, one from 3 days ago. One printed by Eudora, one 2
    pages out of 4 of a pdf file, printed by Firefox**.

    I'm pretty sure the wifi printer was on when I printed them, but I found
    it off this morning. I turned it back on. I refreshed the print
    spooler, I restarted the print spooler, I resumed all he print jobs. I
    paused all the pring jobs, and I again resumed all the print jobs.

    I've run out of ideas.

    **This one I printed twice before and each time they disappeared.
    Nothing came out of the printer and the one time I checked, the print
    queue was empty, a few days ago. I had printed all 4 pages the day
    before, but then I was trying to print only the first 2 pages.

    The usual printer manufacturer recommended method for clearing an orphan
    or problem print job from the print queue.

    Services.msc
    Stop Print Spooler service
    Navigate to spool folder(C:\Windows\System32\spool\PRINTERS)
    Delete the contents
    Start Print Spooler service

    Okay, you and Solution have convinced me.

    When there are two printjobs in the queue and the first in line is no
    good, will it normally still print the second one?

    Retry Print(if necessary)
    - if it still doesn't print when other documents of the same file
    type do print, it's likely the specific document or the program used to
    tell the printer to print the document.
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From micky@NONONOmisc07@fmguy.com to alt.comp.os.windows-11 on Sat Feb 7 11:55:59 2026
    From Newsgroup: alt.comp.os.windows-11

    In alt.comp.os.windows-11, on Sat, 7 Feb 2026 08:40:48 +0000, Graham J <nobody@nowhere.co.uk> wrote:

    micky wrote:

    [snip]

    Then will I have to print it again? For one of the two things, I don't
    remember what I printed.


    It can't be important then ...

    That's what my mother said when I forgot something. LOL
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsQ==?=@winstonmvp@gmail.com to alt.comp.os.windows-11 on Sat Feb 7 12:35:09 2026
    From Newsgroup: alt.comp.os.windows-11

    On 2/7/2026 9:55 AM, micky wrote:
    In alt.comp.os.windows-11, on Sat, 7 Feb 2026 02:27:32 -0700, ...w-i|#-o-#-n|#
    wrote:
    The usual printer manufacturer recommended method for clearing an orphan
    or problem print job from the print queue.

    Services.msc
    Stop Print Spooler service
    Navigate to spool folder(C:\Windows\System32\spool\PRINTERS)
    Delete the contents
    Start Print Spooler service

    Okay, you and Solution have convinced me.

    When there are two printjobs in the queue and the first in line is no
    good, will it normally still print the second one?

    Emptying the spool\Printers folder removes all items from the queue.

    If the 2nd document was available for re-printing, one would look at(it)
    in the print queue.
    i.e. You could/should-be-able to answer your own question.
    Hint: The print queue item's context or tool bar menu.
    --
    ...w-i|#-o-#-n|#
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From micky@NONONOmisc07@fmguy.com to alt.comp.os.windows-11 on Sun Feb 8 19:42:57 2026
    From Newsgroup: alt.comp.os.windows-11

    In alt.comp.os.windows-11, on Sat, 7 Feb 2026 12:35:09 -0700, ...wi+o#n+ <winstonmvp@gmail.com> wrote:

    On 2/7/2026 9:55 AM, micky wrote:
    In alt.comp.os.windows-11, on Sat, 7 Feb 2026 02:27:32 -0700, ...wi+o#n+
    wrote:
    The usual printer manufacturer recommended method for clearing an orphan >>> or problem print job from the print queue.

    Services.msc
    Stop Print Spooler service
    Navigate to spool folder(C:\Windows\System32\spool\PRINTERS)
    Delete the contents
    Start Print Spooler service

    Okay, you and Solution have convinced me.

    When there are two printjobs in the queue and the first in line is no
    good, will it normally still print the second one?

    Emptying the spool\Printers folder removes all items from the queue.

    If the 2nd document was available for re-printing, one would look at(it)
    in the print queue.
    i.e. You could/should-be-able to answer your own question.
    Hint: The print queue item's context or tool bar menu.

    I can't answer my own question. At one time there were 3 dots for the
    whole queue and each of the two items, but when I looked later, both
    jobs were still there but the dots were only for the whole thing. And
    now I've purged them all and reprinted both, successfully I guess
    (except fof a seemingly coincidental unrelated. problem that the print
    has turned grey eventhough there is plenty of ink.)

    Brother all-in-one inkjet; windows 11.
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to alt.comp.os.windows-11 on Mon Feb 9 01:54:29 2026
    From Newsgroup: alt.comp.os.windows-11

    On 2026-02-09 01:42, micky wrote:
    (except fof a seemingly coincidental unrelated. problem that the print
    has turned grey eventhough there is plenty of ink.)

    Ink saving mode? Or draft mode.
    --
    Cheers,
    Carlos E.R.
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From micky@NONONOmisc07@fmguy.com to alt.comp.os.windows-11 on Mon Feb 9 21:03:29 2026
    From Newsgroup: alt.comp.os.windows-11

    In alt.comp.os.windows-11, on Mon, 9 Feb 2026 01:54:29 +0100, "Carlos E.
    R." <robin_listas@es.invalid> wrote:

    On 2026-02-09 01:42, micky wrote:
    (except fof a seemingly coincidental unrelated. problem that the print
    has turned grey eventhough there is plenty of ink.)

    Ink saving mode? Or draft mode.

    I forgot about that. I'll check.
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From micky@NONONOmisc07@fmguy.com to alt.comp.os.windows-11 on Thu Feb 12 11:44:25 2026
    From Newsgroup: alt.comp.os.windows-11

    In alt.comp.os.windows-11, on Mon, 09 Feb 2026 21:03:29 -0500, micky <NONONOmisc07@fmguy.com> wrote:

    In alt.comp.os.windows-11, on Mon, 9 Feb 2026 01:54:29 +0100, "Carlos E.
    R." <robin_listas@es.invalid> wrote:

    On 2026-02-09 01:42, micky wrote:
    (except fof a seemingly coincidental unrelated. problem that the print
    has turned grey eventhough there is plenty of ink.)

    Ink saving mode? Or draft mode.

    I forgot about that. I'll check.

    That might be it. A brother, inkject printer, and my red is clogged, so
    since I almost never want to print in color, i looked up how to change
    to black and white, and it said to use Greyscale, and I know I changed
    it on the old and new computers, because it printed in nice black just a
    few days ago. But now it said Color. I changed it again. I'll see if
    that fixes it.
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From micky@NONONOmisc07@fmguy.com to alt.comp.os.windows-11 on Mon Feb 16 10:42:59 2026
    From Newsgroup: alt.comp.os.windows-11

    In alt.comp.os.windows-11, on Fri, 06 Feb 2026 15:50:41 -0500, micky <NONONOmisc07@fmguy.com> wrote:

    jobs stuck in print queue

    I did as you all said and purged my print queue and started over and
    everything worked. Thank you.

    That was 10 days ago. Today I printed one copy of what I thought was
    only one page and the window for the spooler says Printed 2 of 1 pages.

    HOw can one print 2 of 1 pages?

    Since I'm posting anyhow: It also said it was Job 5. No other jobs are pending. Is this Job 5 since the start of the Windows session? That
    would make sense.




    I have two print jobs that continue to show on the print queue, though
    they are both labeled "printed'. Neither has come out of the printer. .......
    --- Synchronet 3.21b-Linux NewsLink 1.2