SSM-"Incorrect Shutdown"

I just installed the current version of SSM and now everytime I start up Windows I get this message from SSM:

"Incorrect Shutdown-SSM has detected that your previous session was not finished correctly, Since this may be caused by SSM, it was disabled in the current session. Please investigate this problem and uninstall SSM if needed."

 

Your best bet is to go to Max Computing and get some help from Max, the author.

 

In the SSM folder, there should be a file called shutdown.ssm which is created by SSM when it starts running. If you delete this and rerun SSM it should start normally (answering "Yes" to the incorrect shutdown prompt will also delete this file, allowing you to restart SSM).

It may be worth checking that nothing else on your system is interfering with SSM and preventing it from closing normally during system shutdown (Process Guard notably - if you use this ensure that SSM is authorised to Terminate protected applications and don't enable Secure Message Handling).

 

I just posted a question at Max's forum so it will probably be awhile.

I dont have PG installed so that couldnt be a problem. What other stuff I have running at the same time are Nod32, OutPost 2.5, Klipfolio, Trojan Hunter (Guard), SpySweeper, Admuncher, and Trillian. I dont know what SSM may be conflicting with. So probably the next thing I should do is disable those apps one by one.

One thing I did notice was the notification window from SSM when I was shutting down Windows. It said something about SSM not able to write to process ...something, I dont know. I uninstalled it temporarily right now so I could diagnose the problem. I will be back with the exact message once I have it installed again.

 

SSM does try to gain write access on all running processes so programs that include self-protection would seem a likely source of conflict - TrojanHunter would be the most likely candidate from your list. However SSM is still a beta so this could be an issue with it also.

 

I some SSM issues but the only LOG file that contains any info on my machine is
s.app.log

(18:17:06) Internal Error while processing directive 24 : Can't get the name of target process, which is accessed by E:\SSM_INSTALL\ORI\SYSSAFE.EXE
(18:16:45) Internal Error while processing directive 24 : Can't get the name of target process, which is accessed by E:\SSM_INSTALL\ORI\SYSSAFE.EXE
(18:14:27) Internal Error while processing directive 24 : Can't get the name of target process, which is accessed by E:\SSM_INSTALL\ORI\SYSSAFE.EXE

 

Subferno

appears we share one program in common. Spysweeper.

Maybe this is the one?

Maybe we can look at our Windows LOGS and see something.

Bruce

 

Can you do the following:

1. Which beta have you installed
2. Can you go to configuration of SSM to options - debugging - and click on "write log file"
3. I had trouble with Trojan hunter too, but beta 196 fixed that completely. If not set the guard to allow everything, exepcially Terminate process api

Ruben

 

The SSM log will be written to the C:\ folder - so if you do not have write access there, it will be necessary to create the ssmlog.log file manually and enable Write permissions on it. Also, the details in this file are likely only to make sense to Max himself.

 

Yes, but knowing him and as I said having had the same problem he will ask for them --))

Ruben

 

This was the message I get from SSM when I shut down Windows:
"cannot activate window station while waiting for user input" or something like it since it only appears for a few seconds.

As for the log, what do you want me to look for?