NOD32 (http://www.eset.com/) flags NextSTART as having the NewHeur_PE virus. This is a FALSE positive and Eset has already been contacted about this.

I would like to add that I am impressed by their response time: I got a reply this morning (on a Saturday!), just a few hours after reporting the issue. They're working to prevent NextSTART from being reported as a false positive again.

This situation has been resolved in the most professional and nicest way I have ever seen. Not only did ESET release a NOD32 definition file update as soon as their labs 'cleared' NextSTART (and notice, NOT before. That is THE responsible thing to do) as the whole process was handled extremelly professionaly and expedited as much as possible.

Furthermore, I was contacted by ESET's tech support manager, in a follow up, and given a NOD32 license key to make sure the copy protection mechanism of Winstep applications does not conflict with NOD32 in future releases (so they basically managed to turn me into a NOD32 user ).

I am impressed by this level of service and by their AV software. VERY impressed. Recommended!

I also believe that NOD32 is an excellent peroduct and a very professional company to deal with, although my version (updated daily) is still alerting me to Nextstart.

I will look into it further.

I haven't seen it mentioned recently. But I am seeing this false positive today (July 02). I have the latest sig update but still receive this alert. In fact, when I first installed the WSX update, NOD32 prevented the NextStart portion from installing. That would have been pretty cool had this been an actual emergency.

Thanks! I've sent a message to Eset and, given their past track record, expect to hear from them soon on this subject. Since WorkShelf, which uses the same copy protection method as NextSTART, is not being flagged with a false positive, maybe there is something I can do to the code in NextSTART to help prevent future false positives.

Ok, they say they've fixed the problem for the next update.