From: Jose on
On Apr 9, 12:37 pm, "yuppicide" <yuppicide...(a)optonline.net> wrote:
> I think that was the answer.
>
> Something earlier in the day was stuck in print queue by mistake. I got rid
> of it and rebooting must have solved the problem because it's not happening
> today.
>
> I didn't remember something stuck in queue until I just read this.. Thanks!
>
> "Jose" <jose_e...(a)yahoo.com> wrote in message
>

Good.

Did you clean up those old references to Past Items in the
Notification Area using that KB?

Here is a way to clean up any of those stuck print queue items when
rebooting does not work:

To empty the print queue, stop the Print Spooler service and remove
all files from here:

C:\windows\system32\spool\PRINTERS
From: yuppicide on
Yes, thanks. Cleared up the past items too. The only thing I wouldn't
recommend is running that fix while you're doing any work. I had some
software running in the background, which was doing something, the fix
cleaned up everything nicely, but it also closed the program I needed. Only
took me a few minutes to recreate what I was working on, so it wasn't that
bad.


"Jose" <jose_ease(a)yahoo.com> wrote in message
news:17c2c447-6382-470a-a076-e761e797c01c(a)r27g2000yqn.googlegroups.com...
On Apr 9, 12:37 pm, "yuppicide" <yuppicide...(a)optonline.net> wrote:
> I think that was the answer.
>
> Something earlier in the day was stuck in print queue by mistake. I got
> rid
> of it and rebooting must have solved the problem because it's not
> happening
> today.
>
> I didn't remember something stuck in queue until I just read this..
> Thanks!
>
> "Jose" <jose_e...(a)yahoo.com> wrote in message
>

Good.

Did you clean up those old references to Past Items in the
Notification Area using that KB?

Here is a way to clean up any of those stuck print queue items when
rebooting does not work:

To empty the print queue, stop the Print Spooler service and remove
all files from here:

C:\windows\system32\spool\PRINTERS