Print Spooler won't start (error 1053) after recent wave of updates to Win7 64-bit

Anonymous

Hi, all.

I have exactly the same print spooler symptoms that many seem to have but none of the posted solutions worked. I think the issues started at the end of November when I let Windows Update install the latest .NET updates and security updates.

Yes. I cleared out the \printers directory (nothing there)

Yes. I ran the SFC /scannow. All verified.

Yes. I checked my dependencies (just RPC and http and both running)

Yes. I checked the event log file. (the canon driver crashed a couple of times but the last time was back in March)

I just finished spending the day doing a "repair install" (re-installed the OS as an upgrade on top of itself). That fixed the problem and I had my printer back for about 30 mins, but it broke again as Windows Update caught up with the 110 updates that it needed since SP1.

At this point, I'm almost certain one of the windows or .NET updates is causing this. If anyone could figure out which one it is then I'd just re-install again and skip it.

Any more ideas?

Thanks,

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Fixing this issue is very simple. Here was what I've done to start the Print Spooler:

Click Start, type “services.msc” and hit Enter.
Scroll down to Print spooler.
Right-click Print spooler, then select Properties.
Select the Log On tab, and uncheck the Allow service to interact with desktop setting.

(Microsoft recommends that you do not change the Allow service to interact with desktop setting. If you allow the service to interact with the desktop, any information that the service displays on the desktop will also be displayed on an interactive user's desktop. A malicious user could then take control of the service or attack it from the interactive desktop).

Once you have uncheck this setting, select the General tab and click "Start" (the Print Spooler should be able to start without popping up the Error 1053 again).

Hope this helps!

0 comments

78 additional answers

Anonymous

2012-12-28T08:59:26+00:00

Does the problem relate to the printing of pdf files and / or internet web pages?
Was this answer helpful?

0 comments No comments
Anonymous

2012-12-28T08:49:58+00:00

I have exactly the same problem. First noticed it after the recent Windows update. Rolling back the system fixed the issue immediately.

Then yesterday I noticed that the issue returned. This time I allowed the system to install to the latest Windows update as a test. Once again the printers returned.

Few hours later, the printers are gone again.

Clearly something is crashing my printer services but I have no idea what.
Was this answer helpful?

0 comments No comments
Anonymous

2012-12-28T06:11:36+00:00

Thanks, PStorm.

Good idea. I tried CCleaner. That's a pretty good program and it keeps getting better.

It didn't help me in this case, though.
Was this answer helpful?

0 comments No comments
Anonymous

2012-12-26T07:00:33+00:00
My son came across this 1053 Printer Spool error on the Windows service when attempting to upgrade to iTunes 11. I tried the sfc /scannow command mentioned on other blogs but the scan came out clean. The solution for me was the following:
1. empty out all files from C:\Windows\System32\Spool\PRINTERS
2. download and install CCleaner (free)
3. ran the CCleaner registry cleanup (took 3 passes to get a clean scan - runs quickly)
Once I did this and rebooted, the Printer Spooler service started with the reboot and I was able to print. Spent a few hours on this issue, let me know if this helps anyone.
Was this answer helpful?

0 comments No comments