Sharing Wireless Printer

Just acquired my first wireless printer, Canon Pixma MG5750. Previously OH and I had the old printer hardwired to her PC and shared, so I could use it too but only providing her PC was also running. So I was looking forward to setting up new printer as a wireless network printer, usable by any of our computers regardless of what else may or may not be running at the time. So I'm a bit frustrated to find that after printing from either machine it can't print from the other until the print spooler has been stopped and restarted. That isn't very practical of course so I have created a temporary workaround by leaving her PC connecting wirelessly and connecting mine by USB. I could leave it like that of course but there are also a couple of laptops and a couple of phones, all of which might want to use the printer now and again. So how do I fix this?

 

What driver did you install? A CD? the manufacture website? or let Windows do it? By print spooler are you talking the printer or the Windows service?

 

There is a CD but for speed - I needed to print a few things - I just let Win 10 do it. I have to stop and restart the print spooler in Services on the computer that I want to print on. Now I have at least some understanding of this new printer I'm thinking it may pay to remove it and start again using the CD, as the manual advises.

 

I always go to the website and get the latest version. Their software will usually contain any firmware updates you may need too.

 

If print spooler is disabled in Windows service's.It will not execute command.Make sure it's on manual setting.

 

Thanks plodr. Reading around this seems to be a problem affecting mainly Canon printers. I'll try updating the driver first.
@Wile - I will try setting the service to manual. Right now no time though but at least it's working ok atm.

 

wile's suggestion to start the spooler service manually has worked, no more bumping the service needed.

 

This is a potentially ignorant thought, but I was actually messing around with my own hard wired printer recently in an attempt to share it on the network as well, and while doing so, I noticed some options that suggest perhaps the print spooler service isn't exactly 100% necessary. Before this, I never even questioned it... if the print spooler isn't running, you won't be able to print... period. However, if you aren't actually "spooling" print jobs, does it still need to be running?

This doesn't seem to be very practical either, since if there is no "spooling", what are you supposed to do? Yell through the house "HEY IS ANYONE USING THE PRINTER?! I"M ABOUT TO PRINT SOMETHING!!!" That's just assuming it would even work without the print spooler service. It was just a stupid option I'd noticed to not spool print jobs, should you un-check the box, so... technically, if you opt to do that, would you even need the spooler service?

On a side note, good to see you were able to resolve the problem. Do you have to go in and start the service manually every time your system is rebooted? You could create a batch file on the desktop or something... with a simple net start print spooler command, and rather than having to double click here, right click there, double click again etc. etc.... you could just double click the batch file (or powershell script, if you prefer).

 

Yes it does need to run if you use a printer a lot.

If you are like me that does not use a printer.Than disable it.All it's doing if not used is taking up a few thousand KB in RAM.It just shits and waste your ram resources.

 

No, it still appears to start automatically, but in Services a manual start means the service won't start until you start something else that needs it.

 

Well that ain't right either! Just had a situation where I had to start the spooler in Services so I had better create a desktop batch file. Thanks

 

Have you scanned for virus or malware lately.???

 

Desktop batch file seems to have fixed it - net start spooler run as Administrator

 

Heeyyuuull yeah, that's actually one thing I did notice... even though a process, event, or program launch should trigger a service to start, print spooler has always been one of those that will not... when set to manual. There are services that... I assume... are crucial enough that even when set to manual, system events or actions will trigger the start of the service. I guess they just didn't deem printing to be one of them. Heh