Killing winlogon.exe remotely

No, not usually a good idea, I know. However, I was asked last night a “what would happen if….” question. Using taskkill, the process is identified as a critical system process. However, if you use pskill from sysinternals to kill winlogon on a remote box, I got an immediate unclean re-boot. Now you know!

Comments (2)

  1. . says:

    Guranteed Blue screen, same for pulling the plug on mounted drives as folders. Man Windows XP sure is shite. not to mention the WMP bug that prevents the network tab from opening and ANY application depending on WMP controls.

    Talk about stupid!

  2. Howard hoy says:

    I tried that once, just to see what would happen. Yup.. a nice nasty non-clean reboot happened.