- Jul 3, 2015
- 8,153
@ForgottenSeer 58943 mentioned that he has a few lifetime licenses, maybe he will sell you one? Try PMing him.if anyone have LTL for 1 pc for exchange or selling
contact me plz
@ForgottenSeer 58943 mentioned that he has a few lifetime licenses, maybe he will sell you one? Try PMing him.if anyone have LTL for 1 pc for exchange or selling
contact me plz
@ForgottenSeer 58943 mentioned that he has a few lifetime licenses, maybe he will sell you one? Try PMing him.
What about excluding C:\ProgramData\Microsoft\Windows Defender\Definition Updates from SS protection?Services.exe loads the Malware Protection Kernel Services Library driver with every definitions update.
Research it.
For me...not needed but maybe for you necessary becuse of some issue. If not - exclude only connected with such folder processes...or/and make rule allow for all action...or/and exclude important processes in keystroke encryption settings.What about excluding C:\ProgramData\Microsoft\Windows Defender\Definition Updates from SS protection?
Actually, this didn't work.What about excluding C:\ProgramData\Microsoft\Windows Defender\Definition Updates from SS protection?
Actually, this didn't work.
When you exclude a folder, what it really does is exclude all the files that are in the folder at that time. It does not exclude files that will be created in the future.
SS support told me a trick: you sort rules by path, hold down shift, select the rules, and delete them.Plus, there is no way to "un-exclude" a folder.
SS support told me a trick: you sort rules by path, hold down shift, select the rules, and delete them.
Excluding services.exe doesn't sound so good. Better to put up with the minor headache of a daily prompt, it seems to me.@shmu26
To get no alert for the Windows Defender signature driver load during an update, you would have to disable monitoring for services.exe - and not exclude the ProgramData folder. Services.exe is doing the executing and not MpKls*.sys. So excluding the folder does nothing.
Excluding services.exe doesn't sound so good. Better to put up with the minor headache of a daily prompt, it seems to me.
What rules for services.exe you have?...maybe some number of action?Excluding services.exe doesn't sound so good. Better to put up with the minor headache of a daily prompt, it seems to me.
services.exe does not exist as such in the list of rules.What rules for services.exe you have?...maybe some number of action?
Reports were sent.@shmu26
I would send a report to support about the way SpyShelter is behaving between the two accounts and also the spooler folder.
There is some kind of issue with SpyShelter in a standard account, but I am not exactly sure what it is. Member @marzametal knows.
If you re-activate SpyShelter more than 3 or 6 times (I can't remember which), they have been known to deactivate the license. They've done it to me so I can confirm.
Reports were sent.
Thanks for the heads-up about license deactivation.
That's why I've asked about rules/numbers of actions.services.exe does not exist as such in the list of rules.
Did you try to enable option "Launch the program as a service (early start)"?But the strange thing is that after a clean reinstall of SpyShelter, the other user account now has a completely separate set of rules. I even had to re-enter my license, it is treating the second user as completely separate.
It was not this way with the first installation.
1 Sorry, I still don't understand how to answer your question. I have lots of rules, each with its own number. And in the list of monitored actions, all actions are enabled.That's why I've asked about rules/numbers of actions.
Did you try to enable option "Launch the program as a service (early start)"?
1 Sorry, I still don't understand how to answer your question. I have lots of rules, each with its own number. And in the list of monitored actions, all actions are enabled.
What specific info are you asking?
2 I have enabled launch as service.
Although the SUA is maintaining its own rules list, and its own level of protection (auto-allow versus ask user), nevertheless it shares the same restricted apps rules. Weird. This might actually be to my advantage, because I can put the SUA on a lower level of protection (less prompts to spook the noobs).Datpol will tell you that they don't officially\completely support the standard user account. There is some kind of limitation or issue when using it in a SUA.