NET updates and security updates. I checked the event log file. 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 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. Scroll down to Print spooler. Right-click Print spooler , then select Properties. There is a Microsoft support page with information about this error that can be found here. This resolution does work for some and allows the service to return to proper functionality. However, I would like to provide some workaround steps incase this option does not work for some.
I have confirmation that this workaround solution does work for some users. The link below will take you to a thread where this information solved this error for a user in these forums:. Below is the video where the workaround steps, listed above, were found.
The video also gives a graphical representation of these steps for those that prefer visual instructions. Go to Solution. View solution in original post. Didn't find what you were looking for? Ask the community. This is not a printer issue as I haven't had a printer powered on, plugged in or installed for over 2 weeks and 2 clean installs. Hope someone can please help, this is driving me to drink!
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 again. That was almost too easy.
Did as you suggested and service started and works fine. At this point, I'm not real confident the solution will last, but, this is the only time I have been able to start the service without some type of restore.
I can confirm that after 10 days, my problem has never returned. Simply unchecking that checkbox and I was able to start the spooler immediately. Since then it has never failed. I continue to allow automatic updates and have installed a printer with no issues what so ever. Thanks again for the help. I was going to mark your reply as the answer, but, I see that it is already marked as such by the moderator on Feb 5th. On a side note; I have three other Windows 7 x64 compters that all have that same box checked.
They all can connect to my home network and never experience a problem. Any idea why one has to have this interaction turned off, but, the other three don't?
Networking is a complicated subject and not one I fully understand. The network comprised 4 computers and a number of printers. Hari April 21, at Anonymous April 26, at Abinash May 12, at Brandy May 29, at Charity June 6, at Thanks again!! Anonymous June 11, at Richard June 16, at This is the only fix that I have found that actually works. Thank you.
Sl June 20, at Veles June 26, at Anonymous June 28, at Relfe August 9, at
0コメント