Having had this problem myself and having spent 8hrs with 3 different Global Escalation Engineers after complaining to Steve Balmer & Bill Gates, I have found a temporary solution to the spoolersv.exe problem.
Part of the problem is the multitude of environmental temp & tmp folders - any file left in one can cause this problem! The solution is to use regedit to change Environment in [HKEY_CURRENT_USER\Environment], [HKEY_USERS\.DEFAULT\Environment], [HKEY_USERS\S-1-5-18\Environment], [HKEY_USERS\S-1-5-19\Environment], [HKEY_USERS\S-1-5-20\Environment]
and [HKEY_USERS\S-1-5-21-156684348-2512871704-1280440115-1001\Environment] to point to c:\temp. I then created a standard batch file, which has to be run in an Administrator Command Prompt, which stops Spooler service, removes the files from c:\temp,
checks for the presence of spool.exe.org, removes the faulty spoolsv.exe, renames spool.exe.org spoolsv.exe and then restarts Spooler service.
This works every time on my machine and takes as long as the file run time to cure the problem.
I cannot upload the files to this forum,unless someone can help in this respect, but please contact me for copies of the files.
Why the multitude of temp files are needed only the original builders back to Win 1 know! I have suggested that ALL Microsoft help staff are given copies of these files so that, at least temporarily, this problem can be sorted easily.