The popup is built into the executable file, so killing the executable that creates the popup also kills the program. You can confirm this if you know how to use the Task Manager and the Open File Location feature. If you are willing to limit yourself to manually starting SASware, you can achieve this but it's a process which some users might find difficulty following- so I won't bother typing it in. I will say that I have implemented it on one of my machines (Windows 7).
Why is an apparent MSDOS version of SAS running (when no antispy software is scheduled to run)? Why the weird *.com name? 30M I/o reads reported in Task Manager (see attached jpegs).