Thanks for the explanation. Please be advised that the load time at my log on is substantially increased by the addition of ZeroSpyware, and I do not have an excessive number of items in startup. I will try the new version as soon as it is available and report the results here. What flexibility? The second user only has the flexibility not to start ZeroSpware. If the second user wants ZeroSpyware, it must be started manually. Since ZeroSpyware is installed on the computer, it is safe to assume that is is wanted. So I repeat my question: What flexibility? Also note that the startup of ZeroSpyware by the 2nd user de facto increases his/her log on time, so the long log on time ZeroSpyware is now trying to shorten is daisy chained to all subsequent users. Doesn't seem logical to me. I do not quite understand what you are saying, so let me state what I think you mean. The number of components in quarantine may be increased by items found in subsequent scans, but not necessarily by the total number of items found, because some of those items will be killed/terminated. I understand this completely, and it means the total net number of components in quarantine may increase as a result. However, this does not apply to my situation because the number of components decreased in my case. This lack of communication is my fault because I did not make that clear in my question. Understand the reasoning behind the startup selection, but as Blue Zanetti pointed out, and lotuseclat79 illustrated, wouldn't starting as a service both accomplish, and improve, ZeroSpyware's startup goal and eliminate the conflict with, I'll name it now, Window's Defender? Please note that it is my opinion that this is a Window's Defender problem, not ZeroSpyware's. Again, thank you for your comprehensive response AshleyH.