After installing the beta on another computer I came to notice a few things I'd change or add with regards to the initial scan.
1) Upon installation, ask the user if they want to run the initial scan (with all the information as to it's purpose, and that it may take a long time, etc) upon reboot, rather than instantly starting the scan, to which can also ask if they may want to reboot at that moment or not. Since some users may not want the initial scan to start just yet (don't have the time, or would rather start the scan from a reset state, need to uninstall things, etc). This would save users from going into the pause menu to set it to pause until reboot and then closing the scan window; instead would get two actions in a single window, as well as warning new users about the initial scan before it happens so it is not a surprise.
2) When the initial scan is paused, the rotating animation around the SecureAPlus icon should also be paused, and the text "Full System Scanning is in progress..." should probably be changed to "Full System Scan is Paused."
3) This window will be a users first experience with SecureAPlus, along which some users of which may not particularly be technologically literate (i.e. elderly quite often), but may have been recommended to use this program (which I'm assuming you'd want). Right now some of the messages in the lower section come off more as advertisements, which shouldn't really be necessary when a user has already installed the program. So, since this initial scan will likely take quite awhile, and since some of these new users might watch, why not make the lower section give more of a walk through of the SecureAPlus interface and features (with arrows or some other way to go back). This way a more interactive tutorial for these non-tech users shouldn't be necessary, tech users can ignore it (not be annoyed) if they want to, and all the usual information about the features and the application interface is presented before ever actually opening it. Although of course would need to ensure each image would updated with each interface update, so this might not be something until after the interface is 100% complete for the next public build.