This software is a nice concept, a HIPS that may be even for ordinary users but i am smelling something not good.
I had a very bad experience with this yesterday. I'm dual booting, Windows XP and Windows 7. I was booted up on XP. I installed SecureAPlus. It was doing the first initial scan, it started scanning my W7 drive, I didn't want that scanned, so I stopped it in the middle of scanning. Later on, I rebooted to get into W7 and BSOD. I couldn't repair it with the repair disc, I tried restoring a image from AX64 TM. Nothing worked, I had to reformat and install W7 again. I'm just glad I had everything backed up on a external drive. I'm not sure why this happened. Just letting people know.
No, I uninstalled it after this happened. I know there wasn't a virus or anything, I've ran several scans with HMP, MBam, TDS Killer and such. Or would there be another reason to look into quarantine?
this program does not interfere with the mbr or partition structure so i don't see why you think restoring an image from AX64 failed due to SAV. i am not very knowledgeable on these matters but as far as i know, if a program does not mess with the mbr, partition structure or any of the like than a failed restore is due to the method or restoration program itself. maybe someone can correct me. a blessing in disguise to show that AX64 cannot protect you from software failures maybe? after all, whats the point in imaging program when it cant save you from a botched software incident
never seen that myself, maybe because it is running it at that moment. where is Sinlam's replacement representative??
Yeah, just seems odd it stopped booting right after I interrupted the first scan and it was scanning my W7 drive at the time. It's ok though, my W7 is up and running now, just installing the updates.
A false positive like when MS Windows defender quarantined google chromes files a while ago. McAfee before that, goosed windows
That was it! Thanks! Still...it's annoying....should be something like "Running..." without blinking.
glad you sorted it, i have found another GUI bug within the options area. un-ticking it and applying the settings re-ticks the check box. however it still behaves in the intended manner so its just a GUI bug and not a usability one
I'm very sorry for not able to keep you all updated. Recently we are quite busy with a project to enhance SecureAPlus for enterprise. Yes, we have just updated SecureAPlus website recently. treehouse786, you are a good observant . Don't worry, we will keep maintaining the freemium version as well. In fact, we are scheduling to release a new update by the end of this month.
We had a user reported a similar issue to our support team previously. We were not able to reproduce it on our side. It seems that this issue happen in some machines. We actually have tried to fix it, and the fix suppose to be already done in v3.2.4. Never mind, we will try to take a look into it again.
Just would like to confirm with you. I think the previous fix that we've made is only can prevent the blinking after initial system scan is completed. If the status is "Never", then the blinking will still occur. Did you still see the blinking after initial system scan completed? We are going to implement the same fix, so that it will not blink when the status is "Never".
We are not able to reproduce it. Could it be because you accidentally click on "Cancel" instead of "Apply" button?
I'm sorry to hear about what happened to your machine. Was SecureAPlus only installed in the XP partition? If it is not installed in W7 partition, SecureAPlus will not be loaded when switch to bootup to W7.
Thank you treehouse786 and Austerity for providing us the feedback. We will take a look into this issue.
What happen if you close the dialog and go back to the settings again? Will it show the correct status?
