I have the latest version (4.0.141842.828) of CIS installed and am having problems opening Se7en_UA. Please see http://www.msfn.org/board/se7en-se7envista-creator-t138899.html. When I try to open the application, I get a brief hourglass and then nothing. Earlier I got AV errors on several files including the Se7en_UA.exe. It is complaining about Huer.pck.yoda@-1 (yoda is a compressor used in the application). I said to ignore all complaints. But the program will not open and gives no errors or CIS pop ups. I tried many things, like placing these files on the Safe List and Exclusions List with no success. Even exiting from CIS did not allow the application to run. The only way it would run was to remove CIS from my machine. I finally setup it up to run in the Sandbox as Unrestricted. This allowed it to open but it soon failed with several errors due to what I have no idea. Using the Sandbox is unacceptable, anyway. I am stuck until I have an answer. I cannot run the application unless I remove CIS and I do not want to do that. What do I have to do to get this program to run? Thanks, John.
dude, right click the CIS tray icon, click close, type your password in if you have set one and try then.
As I stated above, exiting CIS (mine says Exit - same as close?) still does not allow the application to start. The only thing I have found so far is to REMOVE CIS. I don’t think I should even have to close CIS to be able to use any application. I should be able to place it on My Safe List and that’s it. Thanks, John.
Well, the v3 worked better and had installation mode.
Quite bugged v4 :S
All this does is exit the GUI. CIS protection is still in full effect.
Have you tried just disabling the sandbox?
Thanks for that - did not know. I went as far as to uncheck, using msconfig, both references to CIS, then rebooting. There was no tray icon, but the application would not start. I have also tried Disabling each and every CIS function. Anyway, as I pointed out to the previous replier, I should not have to kill CIS, just advise it that I trust this application. I think I did this via My Safe List and Exclusions List. Thanks, John.
I am running XP x64 with SP2 and all current critical updates. No other security SW is installed. Sorry about leaving this information out. Enjoy, John.
EDIT: Because I am a masochist, I installed CIS (828) on a VM (under VMware Server) running Windows 7 x64 Ultimate and installed Se7en_UA, and executed it. It quickly failed but W7 gave some more information. Problem Event Name is APPCRASH with Exception Code C0000005. The file is Se7en_UA.exe which is on my Safe Files list.
Does it work if guard32.dll is disabled (rename it in system32 and reboot) or with D+ permanently disabled?
Disabling guard32.dll only partly disables D+
Also try searching for 00005 (check how many zeros, probably 7) seem to remember something in the CIS forums.
Best wishes
Mouse
Wow, great! Thanks, mouse1, good suggestion. Renaming guard32.dll allows the application to start (restart is not required, it is in my SysWoW64 folder). I am testing on a VM - not crazy to rename DLLs on my real system . I do not have the large files on VM required to run the application, so I cannot say that it will run completely successfully. Disabling D+ does not allow the application to start. I had already done a search here for C0000005 with no luck and I searched for 0000005, also with no hits. This is much more acceptable than removing CIS, but is still not usable. Hopefully this supplies some information to the people that will correct the underling problem. Thanks much for your help. Enjoy, John.
That’s a pleasure. The devs are now aware of this and are working on it. Next release or the one after possibly. (One may already be going through QA)
No I cannot find the post either. The forum search can be quite frustrating at times.
Never mind
Best wishes
Mouse
mouse1, thanks. I am able to run the application with the DLL renamed, CIS closed (modem unplugged), but have not gotten completely through it error free yet - may well be my problem(s). One thing I kept seeing, causing me to close CIS, was an unsigned .exe (dism.exe) that is run out of the temp folder. Each time it is run, CIS SBs it and the program crashes. Taking it out of the SB does not help since the path is different the next time. Still testing. Thanks much, again. Enjoy, John.
If you can discover the program which is running the temp file, you can make it an installer/updater. That will fix the problem. You can either guess that its the main executable, or look for it using microsoft process explorer (Just Google it).
Best wishes
Mouse
OK, mouse1, thanks. I have been using Process Explorer for some time and will try what you suggest. Thanks much, John.
EDIT: I set Se7en_UA.exe (main executable) to run as Installer/Updater, applied the dll name change, turned off AV, SB and D+ and was able to get a successful run. I don’t think disabling D+ was necessary and will try without it next time.
Should not need to turn anything else off really (apart from guard32 for different reasons), unless it is being detected by AV. But I may have misunderstood. What is DB?
Best wishes
Mouse
mouse1, sorry, should have been SB (Sandbox). I have modified the post. AV does go off. I admit that I have not tried all combinations of settings. Thanks, John.
EDIT: I just got notified of a CIS update but see no announcement here.
Thanks - await feedback with interest.
Best wishes
Mouse
mouse1, I made another run today changing only the name of guard32.dll. The application started and run fine. I got no messages from CIS. I closed and opened several times with no problems. Right now I cannot open it again and I do not know why. Thanks for your help. Enjoy, John.
Most probably CIS updated itself and replaced the file. Details on how to do this more permanently here.
Alternatively if renaming, please ensure you rename in all locations system32/64, syswow, CIS repair directory. (In theory I understand Syswow renaming is not required, but maybe best for completeness).
Best wishes
Mouse
mouse1, thanks. A restart corrected the last non-starting condition. I wrote a small batch file to rename guard32.dll and back. I did only the guard32.dll in th SysWoW64 folder because you only mentioned it. I did find the one in the Comodo repair folder, but did not rename it. I also have the guard64.dll in the System32 and repair folders, but never renamed them. Perhaps it has to do with the 32 or 64 bit nature of the executable. Mine is a 32 bit. I am in reassess mode. The application prepares Windows 7 DVD image for install and I have lots of problems trying to do this under XP. I am considering doing a dual boot install of my W7 and running there with no Internet connection and no security SW at all. Many things get better, including performance (dealing with 11 GB size folders). Thanks for all your help. Glad the problem is well understood and hopefully will be corrected soon. Enjoy, John.
Re 32-bit nature yes it is. You should only have to rename guard32.dll if your OS is running in 32 bit mode. The repair folder is a precaution - running Repair, or possibly automatic repair processes might otherwise re-enable.
Think you are wise re Win7, it’s a step forward from XP, which Vista was not for all users.
Best wishes
Mouse