2nd the post above, but if you are running something as a Windows service, you should be aware that you could be introducing a privilege escalation vulnerability. If a user on the system can change the configuration of your service and cause it to run as SYSTEM, they can run any code they want at that privilege. Luckily, locking it down is easy using the built-in SC.EXE. The best reference I've seen on the subject is Best practices and guidance for writers of service discretionary control lists from Microsoft.