Printer installation problems

I have a home built system with an os upgraded from XP to Vista. I had one printer attached to this system one which worked fine with XP then became buggy once Vista was installed. I just wrote it off since Vista was new it would be eventually fixed as updates became available. I received a new printer "Vista ready" a Lexmark installed the software and it worked once and then would not print again. I recently purchased a wireless Canon Pixma MP495 tried to set it up and get the error as follows:

"Process cannot continue because Print Spooler service has been stopped. Restart the computer to start the Print Spooler service and then try again. <sent image>

I read many forum pages and have tried to correct the problem myself.

Went to command prompt as admin and typed net stop spooler/net start spooler.
ans received: the dependency service does not exist or is marked for deletion

Went to registry and deleted files recommended by forum under HKEY_LOCAL_MACHINE. files under Printer were deleted not the folder itself.
Problem persists.

Long story short I found a thread which matched what is happening to me "exactly". I believe it was listed under "system error 5" spoolsv.exe.

The solution was to replace a corrupt spoolsv.exe file. I sent a pic of my properties file size information box to illustrate my file is larger than it should be.

Is there any way someone could help me download a spoolsv.exe file which may help me correct this problem. Any help would be appreciated.

Try disconnecting the Canon USB Printer and reboot.
Then plug the USB connection in and let it look for the Canon Printer.
Have your disk ready just in case it ask for it.

Print spooler is in your services and can be restarted there.
Start search type services, scroll to print spooler highlight it, right click,properties
Set the start up type to automatic in the drop down box and click OK.

Thank you for the response however I had tried restarting from services see new screen cap. I really feel I need a clean spoolsv.exe file.

Born2golf, thank you for the suggestion however the printer is wireless and is currently not hooked up to the tower. I was attempting to access the printer through the set-up disc/router (which does allow a wireless set up).

If you go to the "dependencies" tab, what does it show?

this is the screen cap of dependencies

Would a system file check help?

http://www.vistax64.com/tutorials/66978-system-files-sfc-command.html

Tutorial:Thanks to Brink

I have already done a sfc I have the log if it helps?

You need to check the dependencies have started as well.

kjzig said:

I have already done a sfc I have the log if it helps?

Click to expand...

Were errors found that could not be repaired?

how do you check?

yes there were spool errors that could not be repaired and it said they would be repaired after reboot. Rebooted and it did an update however problem persists.

At the end of the SFC it show for a shorrt time on the screen. There is also a cbs log
http://www.vistax64.com/general-dis...-not-completing-successfully.html#post1239523

OK
You posted your second while I was posting

When you run the sfc /scannow command it will finish with a message saying either no integrity violations found or found and repaired or repaired some but was unable to repair all.

EDIT:SFC Scan should be run up to 3 times with a restart after each.

this is 2nd sfc results

To upload the log do this.

You need to go to C:Windows,Logs,CBS,CBS.Log
Right click on the CBS.log, and select copy,
Right click on your Desktop, paste,
Right click on the new CBS.log on your Desktop > Send to > Compressed (zipped) folder
On your next post click on the paperclip icon and browse to the zip file and click upload.
Close the box when done.

If errors are found run SFC 3 times.

not sure I did it correctly but here it is

Some files are not able to be repaired while you are using them that is why you need to restart between runs.
SFC can only repair so many files at a time that is why we ask you to run it 3 times first before uploading your log to us.