I had a problem like this once...
...so I took an valid windows 32 executable that loaded into memory (like the task scheduler in windows 98), and renamed it with all the offending software names that were being loaded.
The task scheduler is a very special executable, because it has a mutex that prevents it to load several times in memory, it doesn't pop any errors when you try to load it dozens of times in a row, and has a small memory footprint. It is like doing that Unix thing with redirecting to > null.
Good'ol times, where you could can any crapware that didn't checksum its own executables.
Biting the hand that feeds IT
