Jump to content
Sign in to follow this  
Armaron.com

STLOG.log file- possible workaround; and slowness, too.

Recommended Posts

You have not kept us posted, what is going on with the fix. approaching 60 days and still can not use what i purchased. Interestingly I read in another post of said problem and it was replied to by one of the KL team that it would be fixed in the next patch which I thought great, but no it was coming out next year and he did not say when, not great. And then to my surprise I revisited that same post again for any possible update and that comment from the KL team member was removed. WHAT IS GOING ON? I HAVE HAD IT. This great product has been turned into a waste and it is a real shame.

 

I have the same problem. Contacted support and they informed me that there is no further patch coming. I downloaded dependable old KeyPass.

Share this post


Link to post
I have the same problem. Contacted support and they informed me that there is no further patch coming. I downloaded dependable old KeyPass.

 

 

Wow isn't that just great!!!!Goodbye Kaspersky. Switched to Lastpass working great with firefox all versions. What a shame, will never recommend kaspersky again spent alot of money over the years with their products. NO MORE!!!!!!

Share this post


Link to post
Hi guys.

We aren't planning to release new patch in 2013 but patch E will be available in the next year.

 

Well that doesn't help much for the present. :ai:

Share this post


Link to post
Well that doesn't help much for the present. :ai:

 

 

Eniac2, I have taken to killing stpass.exe from task manager when I am not currently online. It is a bit of a pain having to start up password manager each time I want to go online, but better than the constant grind of small writes to my hard drive.

 

I note that stpass.exe cannot be killed using taskkill from a command line, regardless of permission levels. I guess this is a bit of over-thinking on Kaspersky's part, but would appreciate finding out just what security risk would be opened up if stpass could be killed from a command line.

Share this post


Link to post
Eniac2, I have taken to killing stpass.exe from task manager when I am not currently online. It is a bit of a pain having to start up password manager each time I want to go online, but better than the constant grind of small writes to my hard drive.

 

I note that stpass.exe cannot be killed using taskkill from a command line, regardless of permission levels. I guess this is a bit of over-thinking on Kaspersky's part, but would appreciate finding out just what security risk would be opened up if stpass could be killed from a command line.

 

I opted for a different approach: disabling write access to '%LOCALAPPDATA%\Temp\splogs'. Unfortunately it causes a memory leak in Chrome's Password Manager plugin 7.0.3.11 but I find that restarting the browser or terminating the extension is less ungainly than terminating the stpass process until this is fixed.

Edited by hoople

Share this post


Link to post

Thank you for the info Don and Hoople. I was killing stpass also via Process Explorer but it was a pain in the butt so for now I have all but abandoned PWM in Pure and downloaded keyPass as an option. I may, however, try "disabling write access to '%LOCALAPPDATA%\Temp\splogs'" if I can figure out how to do that. After all, they don't call me "The Armchair Geek" for nothing LOL. Thanks again

Share this post


Link to post

Hello Kaspersky i also am having trouble with my drive making noise at first i thought it was a bug so i reinstalled and wiped my hard drive then i find out this, could you please fix this problem as i have just paid for two years of Kaspersky and am a week in Thanks in advance team.

 

Share this post


Link to post

1) Please, pause Kaspersky protection and check whether the problem persists. To do that simply right-click the Red & Black Kaspersky icon in System Tray (on the bottom right corner of your screen) and select “Pause Protection”.

 

2) Please, Exit Kaspersky and see whether the problem persists. To do that simply right-click on the Red & Black Kaspersky icon in System Tray (on the bottom right corner of your screen) and select “Exit”.

 

3) Please, try do diagnose which Kaspersky Protection component causes the problem:

 

* Pause Kaspersky Protection. Right-click the Red & Black Kaspersky icon in System Tray and select “Pause Protection”.

* Open the main Kaspersky window and go to “Settings” – here you will find the list of protection components in order. Switch the first component (File Anti-Virus) on by clicking the switch to the right.

* Check whether the problem persists.

* If it doesn’t, turn the second component on (Mail Anti-Virus), but leave the first one enabledl.

* Keep turning components on one by one until the problem until the problem kicks in.

 

Please specify which component caused the problem.

Share this post


Link to post
It looks like Patch D did not fully correct the issue with Password Manager component traces being left on. We have a bug created for the issue, 608506, and have word this problem will be fixed in the next patch. I do not know when that patch will be available, nor if this will delay having an installer for PURE 3.0 that works on Windows 8.1. We'll keep you posted.

 

 

1) Please, pause Kaspersky protection and check whether the problem persists. To do that simply right-click the Red & Black Kaspersky icon in System Tray (on the bottom right corner of your screen) and select “Pause Protection”.

 

2) Please, Exit Kaspersky and see whether the problem persists. To do that simply right-click on the Red & Black Kaspersky icon in System Tray (on the bottom right corner of your screen) and select “Exit”.

 

3) Please, try do diagnose which Kaspersky Protection component causes the problem:

 

* Pause Kaspersky Protection. Right-click the Red & Black Kaspersky icon in System Tray and select “Pause Protection”.

* Open the main Kaspersky window and go to “Settings” – here you will find the list of protection components in order. Switch the first component (File Anti-Virus) on by clicking the switch to the right.

* Check whether the problem persists.

* If it doesn’t, turn the second component on (Mail Anti-Virus), but leave the first one enabledl.

* Keep turning components on one by one until the problem until the problem kicks in.

 

Please specify which component caused the problem.

 

 

All systems are normal until one clicks to enable "Pass Word Manager". Once that is done, stpass.exe loads thus starting the "repetitious" write activity to splog.log. As was asked in an earlier post, what good use is the same write data being logged over and over? I had PWM running for less than 20 minutes and the splog.log file had already grown to over 2 megs and that was without using the PW app to log on to any sites. It also causes the PW app to be sluggish because when you try to scroll down the PW lists, the lines blur.

Have a request to support but I think it is confusing to them???

I have all but abandoned PWM but for people unaware of this issue in can cause a lot of unnecessary effort and trouble as indicated in fatilofa's post.

I fear that Kaspersky is going to lose a lot of loyal customers over PWM if they can't get a handle on this bug. (Just my humble opinion of course)

Share this post


Link to post

i have to agree with the armchair geek it seems to write heaps lines every minute i have all protection modules on at highest with password so they cant be changed here is what is happening this is some of the minutes of splog from when it began

 

 

31.12.2013 13:44:59.179 [ACTIVITY_LOG]<3632> Info (10005) Application start

31.12.2013 13:44:59.616 [sTICKY_LOG]<3632> Info (10005) TspSettings.DoLoadSettings Begin

31.12.2013 13:44:59.662 [sTICKY_LOG]<3632> Info (10005) Reading UserExperienceProgram Settings = True

31.12.2013 13:44:59.709 [sTICKY_LOG]<3632> Info (10000) TspSettings.DoLoadSettings() DatabaseFileName=<C:\Users\%UserName%\Documents\Passwords Database\default.spdb> spDefaultDatabaseFileName=<C:\Users\%UserName%\Documents\Passwords Database\default.spdb>

31.12.2013 13:44:59.850 [sTICKY_LOG]<3632> Info (10005) TspSettings.DoLoadSettings End

31.12.2013 13:45:00.006 [sTICKY_LOG]<3632> Info (100200001) Calculated state: NonInitializedFlowState

31.12.2013 13:45:00.052 [sTICKY_LOG]<3632> Info (100200002) Command TProductStartCommand created

31.12.2013 13:45:00.068 [ACTIVITY_LOG]<3632> Info (10005) Product Start command executed

31.12.2013 13:45:00.099 [sTICKY_LOG]<3632> Info (10020) TNonInitializedFlowState.ExecProductStart

31.12.2013 13:45:01.082 [sTICKY_LOG]<3632> Info (10015) Initializing UCPClient with version = 7.0.3.11 locale = en-US

31.12.2013 13:45:04.389 [sTICKY_LOG]<3632> Info (10015) GetUCPClient() - Ok

31.12.2013 13:45:04.420 [sTICKY_LOG]<3632> Info (10016) TUcpEventHandler.Create >>>

31.12.2013 13:45:04.420 [sTICKY_LOG]<3632> Info (10016) TUcpEventHandler.Create <<<

31.12.2013 13:45:04.420 [sTICKY_LOG]<3632> Info (10015) KpmAgent.Subscribe() - Ok

31.12.2013 13:45:04.420 [sTICKY_LOG]<3632> Info (10015) KpmAgent.GetLicenseStatus() - Ok

31.12.2013 13:45:04.420 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.state = 1

31.12.2013 13:45:04.420 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.expirationDate.dwLowDateTime = -859669120; LicenseStatus.expirationDate.dwHighDateTime = 30490469

31.12.2013 13:45:04.420 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.prolongationStartDate.dwLowDateTime = 2063203712; LicenseStatus.prolongationStartDate.dwHighDateTime = 30487653

31.12.2013 13:45:04.420 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.nextAutoRenewalTime.dwLowDateTime = 0; LicenseStatus.nextAutoRenewalTime.dwHighDateTime = 0

31.12.2013 13:45:04.420 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.maxFreeVersionAccounts = 15

31.12.2013 13:45:04.436 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.maxFreeVersionIdentities = 1

31.12.2013 13:45:05.247 [sTICKY_LOG]<3632> Info (100200002) Command TProductStartCommand received notification

31.12.2013 13:45:05.294 [ACTIVITY_LOG]<3632> Info (10005) Product Start command executed

31.12.2013 13:45:05.294 [sTICKY_LOG]<3632> Info (10015) KpmAgent.GetConnectionStatus(2) - Ok

31.12.2013 13:45:05.310 [sTICKY_LOG]<3632> Info (100200001) Calculated state: NonConfiguredFlowState

31.12.2013 13:45:05.310 [sTICKY_LOG]<3632> Info (10020) TNonConfiguredFlowState.ExecProductStart

31.12.2013 13:45:05.310 [sTICKY_LOG]<3632> Info (10015001)

31.12.2013 13:45:05.310 [sTICKY_LOG]<3632> Info (10015) KpmAgent.GetLicenseStatus() - Ok

31.12.2013 13:45:05.310 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.state = 1

31.12.2013 13:45:05.325 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.expirationDate.dwLowDateTime = -859669120; LicenseStatus.expirationDate.dwHighDateTime = 30490469

31.12.2013 13:45:05.325 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.prolongationStartDate.dwLowDateTime = 2063203712; LicenseStatus.prolongationStartDate.dwHighDateTime = 30487653

31.12.2013 13:45:05.325 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.nextAutoRenewalTime.dwLowDateTime = 0; LicenseStatus.nextAutoRenewalTime.dwHighDateTime = 0

31.12.2013 13:45:05.325 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.maxFreeVersionAccounts = 15

31.12.2013 13:45:05.325 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.maxFreeVersionIdentities = 1

31.12.2013 13:45:05.325 [sTICKY_LOG]<3632> Info (100200002) Command TProductStartCommand received notification

31.12.2013 13:45:05.325 [ACTIVITY_LOG]<3632> Info (10005) Product Start command executed

31.12.2013 13:45:05.325 [sTICKY_LOG]<3632> Info (100200001) Implicit state: SPApplyDatabaseSettingsState

31.12.2013 13:45:05.325 [sTICKY_LOG]<3632> Info (10020) TSPApplyDatabaseSettingsState.DoDefaultOperation

31.12.2013 13:45:05.325 [sTICKY_LOG]<3632> Info (10020) TSPApplyDatabaseSettingsState.DoDefaultOperation - database exists

31.12.2013 13:45:05.341 [sTICKY_LOG]<3632> Info (100200002) Command TProductStartCommand received notification

31.12.2013 13:45:05.341 [ACTIVITY_LOG]<3632> Info (10005) Product Start command executed

31.12.2013 13:45:05.341 [sTICKY_LOG]<3632> Info (10020) TNonConfiguredFlowState.ExecProductStart

31.12.2013 13:45:05.341 [sTICKY_LOG]<3632> Info (10015004)

31.12.2013 13:45:05.341 [sTICKY_LOG]<3632> Info (10016000) AddRecipient

31.12.2013 13:45:05.341 [sTICKY_LOG]<3632> Info (10016001) [1]

31.12.2013 13:45:06.402 [sTICKY_LOG]<3632> Info (10000) TfrmCommonSPMain.spmTraceConfiguration

31.12.2013 13:45:06.526 [sTICKY_LOG]<3632> Info (10007) TspIEAutofillPlugin.DoUpdateInstalledRelativeSettings() IsEnhancedProtectedModeSupported: <False> EnhancedProtectedModeEnabled: <False>

31.12.2013 13:45:06.651 [sTICKY_LOG]<3632> Info (10007) TspGeckoAutofillPlugin.IsNPAPIPluginInstalled() Start

31.12.2013 13:45:06.698 [sTICKY_LOG]<3632> Info (10007) TspGeckoAutofillPlugin.GetNPAPIPluginInfo() NPAPIPluginFileName: <C:\PROGRA~1\KASPER~1\KASPER~1.0\KASPER~2\npkpmAutofill.dll>, NPAPIPluginKey: <\Software\MozillaPlugins\@kaspersky.com/Kaspersky PURE>, NPAPIPluginMimeType: <application/x-npkpmautofillplugin>

31.12.2013 13:45:06.729 [sTICKY_LOG]<3632> Info (10007) TspGeckoAutofillPlugin.IsNPAPIPluginInstalled() InstalledFileName: <C:\PROGRA~1\KASPER~1\KASPER~1.0\KASPER~2\npkpmAutofill.dll>, NPAPIPluginFileName: <C:\PROGRA~1\KASPER~1\KASPER~1.0\KASPER~2\npkpmAutofill.dll>

31.12.2013 13:45:06.776 [sTICKY_LOG]<3632> Info (10007) TspGeckoAutofillPlugin.IsNPAPIPluginInstalled() End; Result = True

31.12.2013 13:45:06.792 [sTICKY_LOG]<3632> Info (100200002) Command TProductStartCommand received notification

31.12.2013 13:45:06.823 [ACTIVITY_LOG]<3632> Info (10005) Product Start command executed

31.12.2013 13:45:06.854 [sTICKY_LOG]<3632> Info (10000) TfrmCommonSPMain.spmTraceConfiguration

31.12.2013 13:45:07.026 [sTICKY_LOG]<3632> Info (10000) TfrmCommonSPMain.spmTraceConfiguration

31.12.2013 13:45:07.587 [sTICKY_LOG]<3632> Info (10000) TfrmCommonSPMain.spmTraceConfiguration

31.12.2013 13:45:07.899 [sTICKY_LOG]<3632> Info (10000) TfrmCommonSPMain.spmTraceConfiguration

31.12.2013 13:45:08.008 [sTICKY_LOG]<3632> Info (10016005) Begin NotifyLockStateChange IsLocked: True

31.12.2013 13:45:08.040 [sTICKY_LOG]<3632> Info (10016005) 1 recipients

31.12.2013 13:45:08.071 [sTICKY_LOG]<3632> Info (10015) KpmAgent.GetLicenseStatus() - Ok

31.12.2013 13:45:08.071 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.state = 1

31.12.2013 13:45:08.071 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.expirationDate.dwLowDateTime = -859669120; LicenseStatus.expirationDate.dwHighDateTime = 30490469

31.12.2013 13:45:08.071 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.prolongationStartDate.dwLowDateTime = 2063203712; LicenseStatus.prolongationStartDate.dwHighDateTime = 30487653

31.12.2013 13:45:08.071 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.nextAutoRenewalTime.dwLowDateTime = 0; LicenseStatus.nextAutoRenewalTime.dwHighDateTime = 0

31.12.2013 13:45:08.071 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.maxFreeVersionAccounts = 15

31.12.2013 13:45:08.071 [sTICKY_LOG]<3632> Info (10015) LicenseStatus.maxFreeVersionIdentities = 1

31.12.2013 13:45:08.071 [sTICKY_LOG]<3632> Info (10015003) [0]

31.12.2013 13:45:08.071 [sTICKY_LOG]<3632> Info (10016005) End NotifyLockStateChange

31.12.2013 13:45:08.071 [sTICKY_LOG]<3632> Info (100200001) Calculated state: LockedFlowState

31.12.2013 13:45:08.071 [sTICKY_LOG]<3632> Info (10020) TLockedFlowState.ExecUnlock

31.12.2013 13:45:08.289 [sTICKY_LOG]<3632> Info (10003) TfrmMasterPassword.Create ThreadID: 3632

31.12.2013 13:45:08.414 [sTICKY_LOG]<3632> Info (10015003) [0]

31.12.2013 13:45:08.430 [sTICKY_LOG]<3632> Info (10015024) GetRecentAccounts()

31.12.2013 13:45:09.459 [sTICKY_LOG]<1628> Info (10016) TUcpEventHandler.OnConnectionStatusChanged >>>

31.12.2013 13:45:09.522 [sTICKY_LOG]<3632> Info (10015003) [0]

31.12.2013 13:45:09.522 [sTICKY_LOG]<3632> Info (10015024) GetRecentAccounts()

31.12.2013 13:45:09.522 [sTICKY_LOG]<1628> Info (10016) TUcpEventHandler.OnConnectionStatusChanged <<<

31.12.2013 13:45:09.522 [sTICKY_LOG]<1628> Info (10016) TUcpEventHandler.OnSynchronizationStatusChanged >>>

31.12.2013 13:45:09.522 [sTICKY_LOG]<1628> Info (10016) TUcpEventHandler.OnSynchronizationStatusChanged <<<

31.12.2013 13:45:09.537 [sTICKY_LOG]<3632> Info (10015) PrepareSynchronizationStatus()

31.12.2013 13:45:09.537 [sTICKY_LOG]<3632> Info (10015) KpmAgent.GetActivationStatus() - Ok

31.12.2013 13:45:09.537 [sTICKY_LOG]<3632> Info (10015) KpmAgent.GetAccountId() - Ok

31.12.2013 13:45:09.537 [sTICKY_LOG]<3632> Info (10015) KpmAgent.GetLastSuccessfulSyncTime() - Ok

31.12.2013 13:45:09.537 [sTICKY_LOG]<3632> Info (10015) SyncStatus.HasAccount = True

31.12.2013 13:45:09.537 [sTICKY_LOG]<3632> Info (10015) SyncStatus.IsAccountActivated = True

31.12.2013 13:45:09.537 [sTICKY_LOG]<3632> Info (10015) SyncStatus.AccountId = curtisashbrook@yahoo.co.nz

31.12.2013 13:45:09.537 [sTICKY_LOG]<3632> Info (10015) SyncStatus.ActivateAccountUntil = 30/12/1899

31.12.2013 13:45:09.537 [sTICKY_LOG]<3632> Info (10015) SyncStatus.LastSuccessfulSync = 30/12/2013 5:57:24 p.m.

31.12.2013 13:45:09.537 [sTICKY_LOG]<3632> Info (10015) KpmAgent.GetSynchronizationStatus() - Ok

31.12.2013 13:45:09.537 [sTICKY_LOG]<3632> Info (10015) SyncStatus.SynchronizationState = 0

31.12.2013 13:45:09.537 [sTICKY_LOG]<3632> Info (10016010) NotifySynchronizationStatusChange Begin

31.12.2013 13:45:09.537 [sTICKY_LOG]<3632> Info (10016010) 1 recipients

31.12.2013 13:45:09.537 [sTICKY_LOG]<3632> Info (10016) Sending OnSynchronizationStatusChange() notification

 

 

i have had my computer on now for about 2 hours and 45 minutes and it is 12 megabytes big and counting it just keeps writing and does not stop also i have this happening this is in protection centre this is from today 31 12 2013

 

 

Kaspersky PURE 3.0 c:\program files\kaspersky lab\kaspersky pure 3.0\ Protection is not running 31/12/2013 3:36:19 p.m.

under this one is this

 

Kaspersky PURE 3.0 c:\program files\kaspersky lab\kaspersky pure 3.0\ Custom Scan Task completed 31/12/2013 3:04:24 p.m.

 

these are some more of this same thing happening

Kaspersky PURE 3.0 c:\program files\kaspersky lab\kaspersky pure 3.0\ Protection is not running 31/12/2013 1:43:40 p.m.

 

Kaspersky PURE 3.0 c:\program files\kaspersky lab\kaspersky pure 3.0\ Protection is not running 31/12/2013 1:31:47 p.m.

 

and also when i start my system up it takes Kaspersky a while to start in the toolbar even though it is running in task manager then i get a message that protection is started, in compatibility mode the only one ticked is enable advanced disinfection technology shouldn`t Kaspersky be starting with windows does this seem normal to the team or what confused

 

and in the time it took to do this message the splog is nearly 15 megs

 

i also did what u said but i cant seem to get it to do what it is doing with my had drive it does it when it wants and it hasn`t done it since i paused it for five minutes sorry.

 

Share this post


Link to post

I had this issue with pure 3.0 stpass hammering the hard drive. Here is how you can get around it - if it's worth the hassle to you:

 

1) install a RAM drive - go to http://memory.dataram.com/products-and-ser...oftware/ramdisk and install the lite version.

2) go to sysinternals and download junction http://technet.microsoft.com/en-us/sysinternals/bb896768 junction is used to create a symbolic link from the splogs directory to your ramdrive. In other words you erase the actual splogs directory and replace it with a filesystem symbolic link to the root directory on your ram disk. Stpass will continue to hit the splogs file, but now it's in RAM.

 

HTH

Share this post


Link to post
I had this issue with pure 3.0 stpass hammering the hard drive. Here is how you can get around it - if it's worth the hassle to you:

 

1) install a RAM drive - go to http://memory.dataram.com/products-and-ser...oftware/ramdisk and install the lite version.

2) go to sysinternals and download junction http://technet.microsoft.com/en-us/sysinternals/bb896768 junction is used to create a symbolic link from the splogs directory to your ramdrive. In other words you erase the actual splogs directory and replace it with a filesystem symbolic link to the root directory on your ram disk. Stpass will continue to hit the splogs file, but now it's in RAM.

 

HTH

I have attempted to get this resolved through tech support but it seems we are going in circles. The last reply from them was to disable "Traces" then delete all Kaspersky log files. Traces never have been enabled as I have explained to them a few times.

Thank you for the info Mandrews. I will look into trying that.

Edited by ENIAC 2

Share this post


Link to post

I crunched some numbers from the log file in question, representing about thirty minutes of data. The average time between writes was 120 milliseconds. The longest interval was 1.279 seconds. If windows were not buffering the writes the disc would be in constant use.

 

I have been having the same run-around from "tech support." I have a particular distaste for being infantilized, told to do things again and again that I have already done. Ditto "Traces", for at least third time I have re-installed. (Could their installation program be that volatile?) I know we are being kicked around from one tech to another, without any sign of anyone seriously looking into the problem. I find it particularly patronizing to find Narognov pop up again in this discussion without anything new to say since last month. "Please submit a request to technical support." May as well be "Keep breathing." "Don't play in traffic."

 

I have found that SysInternal's pskill routine will stop stpass, so have been using it. I will look into mandrews' solution also for the machines that are constantly on and off the web. Can I ask, mandrews, what size ramdisk you use? Are there problems foreseeable if you start overflowing the disk?

Share this post


Link to post

Also please see this thread. I have tried the solution there and it worked for me. It not a permanent solution, as it requires being redone on every reboot, whereas denying permission to the directory should only need to be done once. It's just a matter of which solution you prefer.

Share this post


Link to post
I crunched some numbers from the log file in question, representing about thirty minutes of data. The average time between writes was 120 milliseconds. The longest interval was 1.279 seconds. If windows were not buffering the writes the disc would be in constant use.

 

I have been having the same run-around from "tech support." I have a particular distaste for being infantilized, told to do things again and again that I have already done. Ditto "Traces", for at least third time I have re-installed. (Could their installation program be that volatile?) I know we are being kicked around from one tech to another, without any sign of anyone seriously looking into the problem. I find it particularly patronizing to find Narognov pop up again in this discussion without anything new to say since last month. "Please submit a request to technical support." May as well be "Keep breathing." "Don't play in traffic."

 

I have found that SysInternal's pskill routine will stop stpass, so have been using it. I will look into mandrews' solution also for the machines that are constantly on and off the web. Can I ask, mandrews, what size ramdisk you use? Are there problems foreseeable if you start overflowing the disk?

 

 

First of all, a hat tip to mandrews for his suggestion.

 

I have an old, noisy wd raptor drive I was using for my temp folder and the constant writes were driving me crazy. I was also already using Dataram cache for my temp internet files so I decided to give mandrews tip a try. It works, but it requires supervision and tweaking.

 

To begin with, Dataram cache's default setting is FAT32, which means a junction or symlink, which needs NTFS, wouldn't work for me. I created a new 1GB ram cache as unformatted, rebooted and formatted the new ram cache as NTFS in the windows 7 disk management plugin. I don't believe the cache's NTFS format would 'stick' after a reboot, so I saved an image of the new ram cache (with the symlink I talk about below) and used the Dataram option option to reload the image on startup. The NTFS format now 'sticks' after a reboot.

 

After the NTFS cache disk was in place I used mklink (built in windows 7/vista command) to create a symlink to the ram cache. My temp folder had been f:\temp\splogs and I wanted it to be h:\temp\splogs, which is the ram cache.

 

The command for me was, after changing the directory to C: at a command prompt .... mklink /D h:/temp/splogs f:/temp/splogs.

 

That symlink also survived a reboot, but in any case I wrote a small bat file to invoke it just in cache.

 

As for file size, it's too early for me to say, but I did notice that after unlocking an existing splog.log with unlocker and deleting it, the new splog.log file that was created has not been written to. That's probably not a good thing, however password manger seems to be working.

 

It's definitely not elegant. as mandrews seems to allude to. I run password manager manually so I'd say this tweak works well, but is only manageable on a machine with a user comfortable with such procedures. I wouldn't say it's a set it and forget it fix, because of the file splog.log file size increase before I unlocked it, but it is better than what I had before.

 

 

Share this post


Link to post
I crunched some numbers from the log file in question, representing about thirty minutes of data. The average time between writes was 120 milliseconds. The longest interval was 1.279 seconds. If windows were not buffering the writes the disc would be in constant use.

 

I have been having the same run-around from "tech support." I have a particular distaste for being infantilized, told to do things again and again that I have already done. Ditto "Traces", for at least third time I have re-installed. (Could their installation program be that volatile?) I know we are being kicked around from one tech to another, without any sign of anyone seriously looking into the problem. I find it particularly patronizing to find Narognov pop up again in this discussion without anything new to say since last month. "Please submit a request to technical support." May as well be "Keep breathing." "Don't play in traffic."

 

I have found that SysInternal's pskill routine will stop stpass, so have been using it. I will look into mandrews' solution also for the machines that are constantly on and off the web. Can I ask, mandrews, what size ramdisk you use? Are there problems foreseeable if you start overflowing the disk?

 

I use a 1GB ramdisk, but that amount of RAM is not required for stpass - the ramdisk is used for browser temp folders and so on.

For stpass - i actually pointed junction at a folder on the ramdisk named 'splogs' but i didn't actually create the folder. stpass keeps running without issue, so presumably it does a check for the existence of the folder, and simply skips writing to the log file if the splogs folder does not exist. That's nice - no overflow concerns, no superfluous logging. If i ever needed the log, i would simply create the folder splog on the fly - no need to stop stpass - and stpass.exe starts writing to the spLog.log file from that point on.

If you want to keep the spLog.log around all the time, overflow becomes an issue. I haven't done this, but you could create a shell script to 1) stop the stpass service, 2) delete the splogs.log file and 3) restart stpass. Run this batch file periodically using task scheduler in windows - Control Panel\All Control Panel Items\Administrative Tools\Task Scheduler. The task scheduler wizard will run you through the setup; be sure to specify the Action->settings->start in folder or the task might not run (this isn't obvious and trips some people up)

Share this post


Link to post
I use a 1GB ramdisk, but that amount of RAM is not required for stpass - the ramdisk is used for browser temp folders and so on.

For stpass - i actually pointed junction at a folder on the ramdisk named 'splogs' but i didn't actually create the folder. stpass keeps running without issue, so presumably it does a check for the existence of the folder, and simply skips writing to the log file if the splogs folder does not exist. That's nice - no overflow concerns, no superfluous logging. If i ever needed the log, i would simply create the folder splog on the fly - no need to stop stpass - and stpass.exe starts writing to the spLog.log file from that point on.

If you want to keep the spLog.log around all the time, overflow becomes an issue. I haven't done this, but you could create a shell script to 1) stop the stpass service, 2) delete the splogs.log file and 3) restart stpass. Run this batch file periodically using task scheduler in windows - Control Panel\All Control Panel Items\Administrative Tools\Task Scheduler. The task scheduler wizard will run you through the setup; be sure to specify the Action->settings->start in folder or the task might not run (this isn't obvious and trips some people up)

 

Apologies for not being clearer on this: if you don't care about keeping the log file at all, there is no need to setup a RAM drive. Simply use junction to point from the default splogs folder to any non-existent folder, and the log file never gets written - problem solved. If you ever decide you need the log file for some reason, it's probably easiest to just delete the junction, recreate the actual splogs folder, and let stpass write to it. When done with the logging, delete splogs folder and recreate the junction pointing to nowhere

Edited by mandrews

Share this post


Link to post

Thanks mandrews, I'll give that a try.

 

Here's the latest in my struggle with Kapsperky's tech support. It is hilarious.

 

Hello ,

 

The splog.log files are needed by the Password Manager application and will constantly work if you are using said application.

 

The system information file still shows missing Kaspersky components, please run the Kaspersky product removal tool and then install Kaspersky.

Instructions on running the tool can be found here at Article ID 1464: http://support2.kaspersky.com/1464

 

As if I haven't tried this already, and told this guy that I have.

 

Also apparently, if this tech is to be trusted at all, the D patch still doesn't install correctly, at least not for 64-bit Windows 8.1. If I am unhappy with the way Laspersky works now, do I really want the "missing components?"

 

Have I mentioned how much I hate being lied to? The log file is needed by the process? Only someone who never actually looked at the contents of the file could think it held useful information.

Share this post


Link to post
Hello ,

 

The splog.log files are needed by the Password Manager application and will constantly work if you are using said application.

 

Also apparently, if this tech is to be trusted at all, the D patch still doesn't install correctly, at least not for 64-bit Windows 8.1. If I am unhappy with the way Laspersky works now, do I really want the "missing components?"

 

Have I mentioned how much I hate being lied to? The log file is needed by the process? Only someone who never actually looked at the contents of the file could think it held useful information.

The techs name must be "Auto Reply" because that's almost the same responses I am getting. Still waiting on the next reply just to humor myself since I have given up and abandoned Kasper PWM and moved on to good old dependable KeePass. Adding to the frustration, Safe Money is screwing up too so that's history now. Not even going to attempt to seek help on that one. And I'm only running Win 8 / x64. The wife thought I lost my mind when she heard me bad mouth Kaspersky because I have always spoken praise for it in the past.

Share this post


Link to post

Ticket re-opened, 315159729, four months since acknowledged the problem continues in 'd'.

Share this post


Link to post
Sign in to follow this  

×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.