Jump to content
Bubba1

SSUPDATE.EXE proper launch path?

Recommended Posts

Hi,

I've SAS Pro with XP Pro SP2 .. I'm running SAS resident (real time protection enabled). I'm also running KIS 6.0 b621.

In the install directory of SAS, I find SSUPDATE.EXE .. this is not the file that SAS chooses to use, when updating! Nooooooo .. SAS is using a different SSUPDATE.EXE file, which lives here: C:\Documents and Settings\ME\Local Settings\Temp. This is the file that forces net access clearance from KIS, for updating, and which I've granted full access.

Each, and every, time I login ... KIS cries about the "TEMP" directory SSUPDATE.EXE being different/changing! I've added SAS Pro to KIS' trusted. I've added KIS to SAS "don't scan" (no trusted available, that I can find).

My question .. is it "normal", by design, for SSUPDATE.EXE to run from the TEMP directory above? Any idea why SSUPDATE.EXE is appearing to KIS, constantly, as having changed/being new? Why isn't SAS Pro using the SSUPDATE.EXE file residing in it's own install directory?

Thanks.

Share this post


Link to post
Share on other sites
Hi,

I've SAS Pro with XP Pro SP2 .. I'm running SAS resident (real time protection enabled). I'm also running KIS 6.0 b621.

In the install directory of SAS, I find SSUPDATE.EXE .. this is not the file that SAS chooses to use, when updating! Nooooooo .. SAS is using a different SSUPDATE.EXE file, which lives here: C:\Documents and Settings\ME\Local Settings\Temp. This is the file that forces net access clearance from KIS, for updating, and which I've granted full access.

Each, and every, time I login ... KIS cries about the "TEMP" directory SSUPDATE.EXE being different/changing! I've added SAS Pro to KIS' trusted. I've added KIS to SAS "don't scan" (no trusted available, that I can find).

My question .. is it "normal", by design, for SSUPDATE.EXE to run from the TEMP directory above? Any idea why SSUPDATE.EXE is appearing to KIS, constantly, as having changed/being new? Why isn't SAS Pro using the SSUPDATE.EXE file residing in it's own install directory?

Thanks.

SUPERAntiSpyware copies the SSUPDATE.EXE to the temp folder an executes the file from the temp folder so it can update itself without the need to reboot - you should be able to tell KIS to allow it and you won't be prompted each time.

Share this post


Link to post
Share on other sites

SUPERAntiSpyware copies the SSUPDATE.EXE to the temp folder an executes the file from the temp folder so it can update itself without the need to reboot - you should be able to tell KIS to allow it and you won't be prompted each time.

Well, it's the constant copying that triggers a, not to be fooled for one second, KIS. It appears that most KIS users running SAS are doing so on demand, not utilizing real time protection. I'm, at this point, fairly confident there remain no untried switches in KIS that'll impact this behavior. I was given suggestions for settings which lessen/lowered KIS' capabilities, and I've rejected such suggestions. I won't hamstring KIS to not get this SSUPDATE.EXE complaint. I too will probably move to using SAS on demand.

I appreciate your reply. Thanks.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×