OK, I've searched through the forums and there have been a few posts regarding how to stop S&D from startup at system startup; however, the solution isn't my issue. Been there, done that.

In fact, I have been using S&D for close to 10 years now, and have always had the "No automation" selected, and all options below unchecked as I don't want time wasted when booting. I would rather manually do a scan at the end of the day than to have to wait for a scan at the beginning.

Starting around Feb. 2012, on my weekly updates and immunizations I started having a problem with the program making changes to my automation options without my physically going into the options to change them myself. I would do an update, immunize, check for problems and then shut down. The next time I would boot, a scan would begin. Attempting to stop the scan would only lock up my computer forcing me to do a manual shut-down so I could reboot and then recheck my settings in S&D. Lo and behold, even though the main "No automation" button under System start would be checked, the "Run check on program start" would be checked. I DID NOT highlight this myself.

Since this has happened so frequently, I have begun to check these settings before I close out the program just to make sure the "Run check on program start" is NOT checked. It's NOT; however, this is getting checked once I close the program. Not sure why this is occurring. It seems to occur when there are items added to the immunization files. Last week when I did an update and then an immunization, there were no new immunization files and the next time I opened the program, it didn't attempt to scan at start up. Today, there were new immunization files that got updated, and you guest it, S&D decided to start a scan at a start up. I even checked my settings to see if the "Run check on program start" was checked before I closed the program and it WASN'T; yet, the next time I started up my computer, a scan started.

This is getting extremely annoying to say the least. If you had an option to "scan at close of program" and have the program automatically shut down the computer, I wouldn't mind so much. The option to shut down the computer is extremely handy on my Defrag program. I can start a defrag and walk away knowing that the computer will shut down automatically. I don't need to wait around. I think most people would prefer to not have time wasted getting on the computer first thing. A scan at the end would be just as effective as one at the beginning; just would be taking up anyone's time in the process.

I can't understand why this is happening and how I can keep this from happening.