ErnstK

Members
  • Content count

    531
  • Joined

  • Last visited

About ErnstK

  • Rank
    Commentator
  1. @Sylver Cheetah 53 As I experienced with my system of WinXP-Home-32bit-SP3 with CPU of 'AMD AthlonXP 2800+' and RAM of only 2GB the KIS/KAV 2016 (MR0 and also MR1) and the KIS/KAV 2017 was installable and running well under that system as long as the SSE2 CPU issue was not present. So in my opinion I don't believe that the only 2GB size of RAM should be a reason for your issue. (My system for example is using about 1GB maximum) Maybe some other software is taking a lot of memsize. Take a look into your windows task manager (use the administrator mode/account) about RAM space consuming. Before installing KIS you should close all other programs to ensure that there is no additional RAM usage. Also ensure to have enough unused size (free space) on your system drive (normally drive 'c'). Maybe it is helpful to create a systeminfo log and to post the URL of the report with your reply. For instruction look at here: https://forum.kaspersky.com/index.php?showtopic=915
  2. Your type of CPU supports the SSE2 instruction set. So it should not be the reason for your issue.
  3. In addition to what vBDKv said: What type of CPU is used? There is a need that CPU supports the SSE2 instruction set. Unfortunately some oldfashioned CPU types do not support SSE2 but only SSE (for example the AMD AthlonXP CPU).
  4. Hello KeZaX Also, in addition to richbuff's post above this post: Please take a look into the following thread 'KIS 2017 how to switch FW to manual' https://forum.kaspersky.com/index.php?showt...t&p=2669909 Maybe it helps you to configure your KIS application control settings like you want to do.
  5. Also, in addition to what richbuff indicates in the post located above this post, Dual boot license: For instance you will find the current EULA of KIS 2017 in English version on the following Kaspersky online support page: http://support.kaspersky.com/12741 Inside this EULA please take a look at point 1.3, 2.2 and 2.3: "1.3. Computer — the operating system, virtual machine or hardware, including the workstation, mobile device or server for which the Software is intended and/or on which the Software is to be installed and/or used." ..... "2.2. If the Software was acquired on a physical medium You have the right to use the Software for the number of Computer(s) and/or User Accounts as is specified on the Software package." 2.3. If the Software was received/acquired via the Internet You have the right to use the Software for the number of Computers and/or User Accounts as was specified when You acquired the License to the Software." Essential note: Inside the current EULA of KIS 2016 the definition of the term "Computer" is another one than inside the EULA of KIS 2017: 1.3. Computer(s) means hardware, including personal computers, laptops, workstations, personal digital assistants, "smart phones", handheld devices, or other electronic devices for which the Software was designed where the Software will be installed and/or used.
  6. Added: For SSE2 requirement of i.e. KIS v2017 please take a look here: https://help.kaspersky.com/KIS/2017/en-EN/43520.htm
  7. Yes, both are still supported. But please note that for XP you need NTFS formated systemdrive instead FAT32. Please take a look into the Kaspersky online support pages concerning your Kaspersky product. For instance about KIS v2017: http://support.kaspersky.com/12743 Yes, every system needs its own Kaspersky installation. The count is of one licence for both boot systems together when the boot systems are placed on only one platform which guarantees that only one Kaspersky installation can be used at the same time (instead: Installation on a virtual machine needs an additional licence) One additional point: Please take also care about the used type of CPU. The CPU must support the SSE2 instruction set. For example the older AMD AthlonXP CPU does not support the SSE2 but only the SSE instruction set which causes the Kaspersky product to malfunction. What type of CPU do you use?
  8. P.S.: As I had asked for nonSSE2 continuance I've got following answer at first: Guten Tag, ErnstK, Benutzer Taras Zakrepa hat gleich im Thema geantwortet, das Sie abonniert haben. Thema: "Update APU, APD, Kjim, klavemu, kimul.drv, oSSL, SystemWatcher, VLNS3". ---------------------------------------------------------------------- QUOTE(ErnstK @ 25.01.2017 21:08) If possible, please provide me with message when released update is available by public server. Because of total system freezing when I make current update by public server. This concerns the Win7 system with KIS2016 as also the WinXP system with KAV2017. Thanks. P.S.: Is there any ensurance on Kaspersky side that all modules will be created nonSSE2 compatible in future? Otherwise Kaspersky should officially discontinue the nonSSE2 compatibility. ----------------------------- Sure, you'll be notified. Kaspersky products should remain nonSSE2 compatible as you can see, the fixes being applied as a reaction to your needs. ---------------------------------------------------------------------- Link zum Thema: https://forum.kaspersky.com/index.php?showt...view=getnewpost Look also the afterwards corrected answer under: https://forum.kaspersky.com/index.php?showt...t&p=2670056
  9. Also on my side: KIS 16.0.0.614 (h) was running well until easter this year. Then I were away on leave and came back at home after easter realizing that KIS made new patch update and KIS was no more running after that because the KIS service starts and after a short time it breaks itself and restarts itself again - an endless loop. This error behavior concerns all the new patched versions (as far as I have tested it on my system) of KIS 2015, 2016 and 2017. So there is no chance for me by using alternative version. Only to stay with an working unpatched version (e.g. KIS 16.0.614 h) which must not get any new patches and/or signature updates. Up to now I have uninstalled KIS on my Win7 system and instead installed Microsoft Security Essentials which works very fine on my none-SSE2 system. Also I have installed an additional Personal Firewall to check/control the network traffic. This also works very well. So what should I say now: Kaspersky please come back to me??? Badly that I have a KIS license of 176 rest days and a KAV unused license of 365 days. 'Damned' patching virus!! Sorry. I'm tired of beta-testing nonSSE2-compatibility year for year, patch for patch.
  10. Folglich müsste bei den anderen drei Systemen von Feechen eine ältere KIS-Version installiert oder KSecC deinstalliert sein bzw. eine entsprechende KIS-Einstellung vorgenommen sein.
  11. Hinweis: Das Thema gab es schon einmal mit KIS2015. Siehe diesen Thread hier: -> https://forum.kaspersky.com/index.php?showt...t&p=2307768 ,in welchem die Zusammenhänge recht gut beleuchtet werden. @Feechen: Warum diese Meldung bei Dir mit einem Mal sporadisch auftaucht, kann ich nicht sagen. Möglicherweise hat sich da aufgrund der vor wenigen Tagen erfolgten Verteilung des KIS-Patch 'd' (oder auch anderer KIS Datenbankupdates) etwas verändert/verhakt. Ich würde die aktuelle WLAN-Netzwerkvertrauenseinstufung (evtl. sogar das Netzwerk nochmal neu einrichten) bei Deinem Windows wie auch bei Deinem KIS manuell nochmals neu zuordnen und danach den PC komplett herunterfahren/ausschalten und wieder neu hochfahren. Tritt die Meldung danach dann noch auf? Wenn ja, dann kannst Du die Meldung ignorieren, da Du Dein eigenes privates WLAN benützt und dieses ja hoffentlich mit abgesichertem (passwortgeschütztem) Zugang in aktuell empfohlener Verschlüsselungsmethode "WPA2" betreibst.
  12. Richtig, aber KIS 'routet' sozusagen die Vertrauensstufe Typ "öffentlich" bei Internetanwendung durch die gesamte Verbindungskette rückwirkend durch. Siehe hierzu auch den Post von Schulte in einem anderen Thema -> https://forum.kaspersky.com/index.php?showt...t&p=2594699 Gute Frage, denn: KIS ist möglicherweise nicht in der Lage, anhand des von Windows vorgegebenen Netzwerktyps (öffentlich/privat) sich darauf einzustellen und entsprechend zu handeln. Warten wir auf die Antwort von Feechen!
  13. Ich vermute, dass KIS das lokale WLAN-Netz zum Router als unsicher einstuft, da dieses Netz zum einen dem als "öffentlich" eingestuften Internetzugang dient, und zum anderen als vertrauenswürdig (d.h. ohne sicherheitsbedingte Einschränkungen) definiert ist. Vorschlag: Einstellungen -> Schutz -> Firewall -> Option "Schwachstellen bei Verbindung mit einem WLAN-Netzwerk melden" deaktivieren und/oder Einstellungen -> Schutz -> Firewall -> Netzwerke -> Netzwerktyp des Netzes "Charlie" ebenfalls auf "öffentliches Netzwerk" oder alternativ auf "lokales Netzwerk" umstellen.
  14. Also, Please take a look at the following post(s) in the thread under https://forum.kaspersky.com/index.php?showt...t&p=2386728 Note: The rootkit scan automatically starts 30 minutes after the start of Kaspersky produkt in case of last rootkit scan start is at least 24 hours in the past. Otherwise the scan automatically will be started in the running session immediately as soon as the 24-hours distance time is full filled. If the rootkit scan provides a loss of system performance you might disable the rootkit scan in general. There will be no loss of protection level because the realtime protection and also the manually full scan will examine rootkit objects too.