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

Anonymous
2012-12-14T05:57:12+00:00

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,

Windows for home | Previous Windows versions | Devices and drivers

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
2012-12-29T07:45:18+00:00

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

  1. Click Start, type “services.msc” and hit Enter.
  2. Scroll down to Print spooler.
  3. Right-click Print spooler, then select Properties.
  4. 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).

  1. 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!

Was this answer helpful?

10+ people found this answer helpful.
0 comments

78 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2012-12-18T23:07:06+00:00

    Thanks for the help, Rharkrider.

    I tried to install just the .NET 1.1 version, but it wouldn't install. That did force me to uninstall the .NET 3.5 that comes with Win7 and the .NET 4.0.

    That alone did not fix my problem, but when I also tried removing Print Services and re-installing it (another trick I heard about), I got my printers back. Then...after the next re-boot...they are gone again. Same symptoms as before.

    I swear, as a Windows PC user, the cost of the computer is a small part of the cost. I've probably spent 100 hours of my life trying to fix this problem with Microsoft's "self-help" attitude.

    You have to be a computer expert to keep a Windows PC running. Everything is "xxxx Error. Please contact your system administrator." WHO THE **** IS MY SYSTEM ADMINISTRATOR?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-12-18T15:46:34+00:00

    Here's the link to the ServicePack I used....

    http://www.microsoft.com/en-us/download/details.aspx?id=33&ppud=4

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-12-18T15:44:12+00:00

    I also tried everything to fix this problem.  I was finally able to fix "error 1053" today.

    I first installed the Microsoft.NET Framework 1 service pack 1.1 from 2004, (not the more recently published versions)

    I then restarted the Print Spooler at Control Panel/Administrative Tools/Services/Print Spooler --  you can simple restart by right-clicking.

    Finally, I reinstalled my printer's drivers and everything worked as normal.....

    I hope to have lucked into solving a very confusing MS issue.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-12-18T03:14:59+00:00

    I also have the exact same problem, have done all of the above, still cannot print or start spooler.

    Was this answer helpful?

    0 comments