nzorn
Expert
Expert

If the user logs off and logs back into a clean machine it fixes the problem, but no one wants to do that.

Killing the splwow64.exe process does the trick as well. 

Someone already mentioned to me that they did not get any resolution with that KB article I listed, and they just ended up placing a VBS script on everyone's desktop to kill the process.

Reply
0 Kudos