Jump to content

x64

Members
  • Content Count

    25
  • Joined

  • Last visited

About x64

  • Rank
    Candidate

Recent Profile Visitors

229 profile views
  1. You can select the target folder for detect spam, but the settings are accessed through plug-in options within the Outlook application as opposed to through the main KIS/KTS interface. The following is for Outlook 2016 but as I'd imagine it or something very similar would work for you in 365. You need to find the "Add-in options" dialog. For Outllok 2016, that is found on the "File" tab under "options" which brings up the "Outlook Options" dialog. Select "Add-ins"on the left hand side and click the "Add-in options" button. The "Add-in options" dialog appears. On that dialog, you should have an "Anti-Spam" tab on which you can select the target folder seaprately for "Spam" and "Probable spam", and whether to mark it as read. Change the target folder to your desired spam folder in whichever account you wish. It probably currently has a legacy setting from before your email change. x64
  2. In general yes (they work together). MWB Real time protection might have a conflict with Safe Money (I've had safe money disabled for a long time, from since well before MWB 3 came out. The issue back in MBAM 2 days was that safe money would not tolerate the MBAM modules monitoring processes protected by Safe money). It's also worth researching the compatibility at the Malwarebytes forums, as some of the staff and mods there recommend adding mutual exclusions in the products as part of ruggedising MWB 3 against the random protection disabling issues that have plagued MWB 3. Also ensure that you are on the latest MWB 3 - see the post at the top of the MWB 3 section of the Malwarebytes forum. I've implemented the exclusions but am in two minds as to whether they are actually helping (I'm only very mildly affected by the MWB protection issues, and in the process of moving to Mac, so my Windows box will be used less frequently from now on). To put my report in context, my Windows system is Win10 v1703 x64 on current branch, and I'm using KTS 2017, MWB3 (latest release with lifetime premium sub), and I use Firefox as my main browser on it and Outlook 2016 for email). x64
  3. See the links from this article https://www.bleepingcomputer.com/news/hardw...ental-keylogger/ The second link appears to point to a driver version 10.0.931.90 x64
  4. See: https://www.help.barclays.co.uk/faq/securit...d/software.html for options. The original free three user licence for Internet security has been cut back to just two users but you can upgrade to a five user copy of Total security for £6.99. Even if you dont need the extras that KTS gives you it's still a cheap way to get the extra licence. x64
  5. One final suggestion from me. I might also suggest searching your C: for softwareupdate.exe (use the search box in Windows explorer) to see if there are remnants of an previous version of the sioftware remaining in another folder. Some help for the Software updater exclusions list is found at https://help.kaspersky.com/KTS/2017/en-EN/127697.htm That suggests that if you skip the an update rather than attempting to let it run, it gets added to the list. x64
  6. One of the things that I was trying to suggest was once we found that file, to check the version of it to see if it is indeed an old version. To do that, right click the file and choose properties. Choose the "Details" tab and check the file version listed there. If it is the newer version (v2.2.0.150) then there may be another older inactive copy of the file somewhere on your system that is triggering the warning. If we really cannot find the downlevel version of the Updater then there appears t be another option. I'm not a fan of disabling protection components. dh27564 above suggested disabling the Software Updater component. Instead of disabling the Software Updater outright as suggested, there is also an "Exclusions" list on "Settings/Protection/Software Updater" page, which could probably be used to mask the warning just for the Apple software updater. The Apple Software updater just makes outbound calls to apple servers to check for, and download new software. Whilst not ideal, the risk of ignoring the downlevel version is probably minimal. x64
  7. The picture that you attached shows that the software that ie being detected as downlevel is in fact the Apple Software Updater (aka "ASU") itself. It recommends updating to v2.2.0.150 (which happens to be the version that I have on my PC). It says you are on v2.1.4.131, so it IS looking at an old version. I checked the properties of the executable on my PC to determine the version that I have. My system is 64bit and I found the executable at: "C:\Program Files (x86)\Apple Software Update\SoftwareUpdate.exe". I suppose the next thing to do is to see if you have more than one version of that file on your PC (an old one and a new one)... Do you run the Apple Software updater to update your software or use the update menu item in iTunes?. Maybe (if the latter) you could run the updater itself - it might (hopefully???) self update!... x64
  8. Also, There were some Apple updates last week - it's worth checking that you really do have them. iTunes bumped to v12.5.3 and iCloud desktop app bumped to v6.0.1. Also ensure that you don't have an old copy of Quicktime installed. Quicktime for Windows has been discontinuned, so there is not a secure version availble. x64
  9. The "[!! SPAM]" suggests that Kaspersky DID detect that it was spam. The question it what to do with it then.. In Antispam settings within the main KTS app you can set the labels to insert into the subject lines - that is where the "[!! SPAM]" comes from. Depending on your email client you may be able to redirect the message into junk mail. In (full)MS outlook for instance you can set the actions witin the KTS outlook plug-in. I don't know whaic options are available to other email clients (but I suppose, if there is no plug-in you could look for "[!! SPAM]" in the subject using a rule of some kind and trash the spam on that?). x64
  10. As Adam 1972 says, the upgrade to KIS2017 is free fot thelicence that you have, and (since the recent issue of "Patch B") is the recommended version for the Anniversary edition. If on KIS 2017 - you should check that you are on version 17.0.0.611(b) If you choose to remain on KIS2016, then to need to be on 16.0.1.445(e) The minor updates (the letter at the end of the version number) will happen along with regular definition updates, but take effect on the following reboot. x64
  11. I use Outlook 2016, so you will need to translate my suggestion into the same settings in outlook2010 (I'm aware they are quite different). I think that the setting that you need is in the Outlook plug-in itself rather than the KTS main application. You need to find the "Add-in options" dialog. For Outllok 2016, that is found on the "File" tab under "options" which brings up the "Outlook Options" dialog. Select "Add-ins"on the left hand side and click the "Add-in options" button. The "Add-in options" dialog appears. On that dialog, you should have an "Anti-Spam" tab on which you can select the target folder seaprately for "Spam" and "Probable spam", and whether to mark it as read. x64
  12. I'm on Zen, and whilst I use a separate email provider, Zen's pop/smtp server works fine for me through KTS 17 and Outlook 2016. OK - different products, but they prove the basic point. The "Relay" message suggests that authentication against Zen's SMTP server is failing. x64
  13. It's been several days now. Do we know if this goal (from beta testing forum) of patch e has been achieved? ... "• Requirement 1709338:[bRQ][Win10]Full support for RS1"... And if so, does it supersede the RS1 compatibility warning on the support site? The wprds "full support" would seem to imply that it would. x64
  14. Also, See a similar thread I started about Kaspersky 2015 and even raised a support incident about it. https://forum.kaspersky.com/index.php?showtopic=306819 I too thought that adding exclusions would allow me to deconflict the applictions, however it seems that "Safe Money" has other ideas. Look at the last post in that topic, (the one by Nikita Shembel. ) Basically MBAM is examining Safe Money's memory ares, and Safemoney is taking exception to that (as it's job is to prevent any and all snooping of the data it is protecting). The information in the thread is for KIS2015, but from the responses that I received - it did not sound as if KL were considering changing the absolutely "no snooping on safe money's memory" policy. x64
  15. Working for me now as well, but I suspect that one or more servers in that array was missed when the certificate was renewed... x64
×
×
  • 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.