Turns out there were twenty or so Scheduled Tasks running mshta.exe at one hour intervals.
Thats why killing the processes seemed to temporarily fix the issue. At least until the next scheduled task that invokes it again.
--Check your Scheduled Tasks in Control Panel--
Edited by Orange Blossom, 20 December 2010 - 02:03 AM.
Deactivate link. ~ OB