Hi Guys, the latest SecureAPlus Version 2.0.18 is finally released Good news is we have fixed the Sandboxie problem faced by some users previously. Now the Sandboxie will not freeze if you run the web browser inside it. An important note to those users whose default software update is "Automatic update". You have to update the software manually due to the auto update crashing problem in the earlier version. We have already fixed this crashing problem in this version. So subsequent update does not require you to do it manually. We have also fixed the display problem of "Show all trust level" menu option and SecureAPlus system tray icon. We have added "git.exe" and "tortoisegitproc.exe" to the "Restricted Application" list. You can view the release note at https://secureaplus.secureage.com/Main/release.php for more information on the changes. Last but not least, please feel free to give us as many feedback as possible
Hi: Today I decided to install secureaplus and the pc went to reboot crash and windows would not load. So after reverting to a good snapshot and testing I found out that secureaplus conflicts or incompatible with toolwiz time-freeze. So when I had turned time freeze on and finished my work and rebooted to get back to normal windows thats when the crash happened. Therefore I was forced not to use secureaplus since I need time freeze. So you guys need to check this out. So instead I had to use online armor free to compensate the secureaplus whitelist.
Hi taleblou, Sorry for the problem you are facing right now. Did you install the latest version 2.0.18? We have just tested this version together with toolwiz time-freeze in XP SP3 and Windows 7 (32-bit and 64-bit) but it works perfectly fine. Please refer to the screen capture below. We are unable to reproduce the problem you are facing. The testing steps are as follows: 1. Install Time Freeze on the computer and reboot it since rebooting is necessary after installation. 2. Set Time Freeze to "Frozen Mode". 3. Install SecureAPlus Version 2.0.18. 4. SecureAPlus is running fine. Which OS are you using? If you have not installed the latest version 2.0.18, you may try to install it and see whether you are still facing the same problem. If you are still facing the same problem, please send us the "MEMORY.DMP" file. You can find it at "C:\Windows\" . As it is a very huge file, please email us at secureaplus@secureage.com to request for the ftp path to upload the dump file.
sinlam, why should he put TF to "Frozen mode" before installing SAP? SAP would be gone after reboot...
Hi taleblou, after further testing, we are able to reproduce your problem. Let us investigate further and will keep you posted once we are able to find a solution. Sorry for the inconvenience caused
The Sandboxie conflict with SecureAPlus is indeed fixed (at least it appears so far from my limited usage). Thank you, Sinlam. Almost forgot. What SecureAPlus applications require internet access (I assume CheckUpdate.exe is one of them)? This is for Windows Firewall rules. This is on Win 8 Pro 64 bit and I installed SecureAPlusNoAV. Regards, Bob
Hi Bob, good to know Sandboxie and SecureAPlus are working fine together Besides CheckUpdate.exe, SecureAPlusService.exe and SecureAPlus.exe also require internet access.
Hi sinlam: To test the issue I had here is what I had when it happened. I had these ruuning at the time: 360 internet security plus toolwiz timefreeze, trusteer rapport and k9 web security and securitykiss VPN and when I installed secureaplus plus AV and when the above were active and then rebooted pc faced with the loop reboot problem crash. My system is win 7 ultimate 64bit. So if you set these up and test to see if you can reproduce the issue.
Hi sinlam: Well I tried the now secureaplus with av on a system of mine with win 7 ultimate 64 that had comodo internet security and trusteer rapport active. As soon as I installed secureaplus and afterward rebooted the pc went again to reboot loop and each time it rebooted to the windows saying windows repair. I tried to go to safemode but it would reboot. So there was noway for me to get the dump as windows would not load. SO had to revert back to a good snapshot via comodo time machine. So it might not be toolwiz time freeze and the only thing in common on both system is the comodo time machines and trusteer rapport. I do not know whys ecureaplus causes this bad crash when installed??
Hi taleblou, thank you for your valuable feedback and truly appreciate your patience We will further investigate on the problem you are facing. Which version are you using for Comodo Time machine? Is it Comodo Time Machine 2.9.161985.187 Beta?
Hi taleblou, we have tried Comodo Time Machine and our machine crash. Based on the memory dump file, the crash seems to be at Comodo Time Machine driver. Below is an excerpt of the memory dump file for your reference. ---------------------------------------------------------------------------------------------------------- BugCheck 7E, {ffffffffc0000005, fffff88001875198, fffff880035f3948, fffff880035f31a0} *** ERROR: Module load completed but symbols could not be loaded for CTMSHD.sys Probably caused by : CTMSHD.sys ( CTMSHD+4422 ) …. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff88001875198, The address that the exception occurred at Arg3: fffff880035f3948, Exception Record Address Arg4: fffff880035f31a0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. …. PROCESS_NAME: System CURRENT_IRQL: 2 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 000000000000002c READ_ADDRESS: 000000000000002c FOLLOWUP_IP: CTMSHD+4422 fffff880`0183e422 4883c428 add rsp,28h BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from fffff88001875975 to fffff88001875198 STACK_TEXT: fffff880`035f3b80 fffff880`01875975 : fffffa80`03359060 00000000`00000000 00000000`00000000 fffffa80`00000000 : CLASSPNP!ServiceTransferRequest+0xa8 fffff880`035f3c20 fffff880`0183e422 : fffffa80`04bc8010 00000000`00000000 00000000`00000000 00000000`00000000 : CLASSPNP!ClassReadWrite+0xd5 fffff880`035f3c70 fffff880`0183b680 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`03358100 : CTMSHD+0x4422 fffff880`035f3ca0 fffff800`02b7ccce : fffff880`01853320 fffffa80`0336bb60 00000000`00000080 fffffa80`0336bb60 : CTMSHD+0x1680 fffff880`035f3d00 fffff800`028d0fe6 : fffff880`009e9180 fffffa80`0336bb60 fffff880`009f3f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`035f3d40 00000000`00000000 : fffff880`035f4000 fffff880`035ee000 fffff880`035f39f0 00000000`00000000 : nt!KiStartSystemThread+0x16 …. MODULE_NAME: CTMSHD IMAGE_NAME: CTMSHD.sys ---------
Also, CTM 2.9 beta seems to be in eternal beta stage, so the user should install latest stable version, which is 2.8. Looks like the product is on longer hold cause they moved most of the resources to CIS development.
Does whitelisting work as AppLocker Publisher and Hash rules? If wish the initial whitelisting procedure had some progress bar.
Well Its true its beta and 2.8 never worked for me. But since many years that ever 2.9 came out I had it on and never had any issue on my multiple pcs. Also I had no issue with installing anything except this happen whens ecureaplus install, heck I even tested it with comod internet security, online armor, shadow defender and several other bothersome apps and never found any issue with CTM and them. Its actualy the first time I see something like this happens when using secureaplus. Even voodo shield worked great with CTM. Anyway I have never had any issues with CTM 2.9 all these years and no crashes on several pcs. Thats what is strange.
