Jump to content

dvolokitin

KL Russia
  • Content Count

    196
  • Joined

  • Last visited

3 Followers

About dvolokitin

  • Rank
    Cadet

Recent Profile Visitors

1,241 profile views
  1. Если вы видите сообщения о блокировке, то с чего приходит мысль что защита перестала работать? или я что-то не понимаю...
  2. Аndrei приветствую, Подскажите версию продукта? 1.0.2.349 или 1.0.3.326 ? (чтоб увидеть - достаточно подвести курсор мыши к иконке продукта в трее)
  3. dvolokitin

    Known issues

    List of Known Issues of Kaspersky Safe Kids Beta for Windows (11.07.2016) - Before installing the new build Kaspersky Safe Kids Beta you must uninstall the previous build using standard Windows tools; - Safe Search works if technology implemented in search engines; - If you pause and then resume protection for the child, then control web activity will only work after you restart each open browser; - The reports can be specified by reference to the images and icons of visited web site; - Some websites obvious content can not be blocked by product category; - Sometimes when Safe Kids blocks devices do not come notification; - There are no search requests from Google Chrome in google.com search; - Reports on visited 'Warning' websites can be duplicated; - Yandex video is not completely blocked; - Request for access only works for sites with latin names; - Wrong domain names for non latin sites in reports; - FFx64 does not open https sites; - Help is not opened from tray menu. Warning! When connecting the SafeKids test (beta) version to the My Kaspersky portal (hereinafter referred to as Service), you agree that the Right Owner (Kaspersky Lab AO) provides the functionality of the Service intended for management and interaction with the application for testing ‘AS IS’. THE RIGHT OWNER AND ITS PARTNERS PROVIDE NO WARRANTIES REGARDING ITS USE, PERFORMANCE, AND AVAILABILITY. THE RIGHT OWNER AND ITS PARTNERS PROVIDE NO WARRANTIES, CONDITIONS, REPRESENTATIONS, OR STATEMENTS, EXPRESSED OR IMPLIED, WHATSOEVER, INCLUDING, WITHOUT LIMITATION, NON-INFRINGEMENT OF RIGHTS OF THIRD PARTIES, COMMERCIAL QUALITY, AVAILABILITY, INTEGRABILITY, OR FITNESS FOR PARTICULAR PURPOSE. YOU HEREBY AGREE TO ASSUME LIABILITY FOR SELECTION OF THE SERVICE, USE OF THE SERVICE, AND ANY RESULTS ARISING FROM THE SAID USE. THE RIGHT OWNER AND / OR ITS PARTNERS ASSUME NO LIABILITY FOR ALL AND ANY DAMAGES AND / OR LOSS, INCLUDING THOSE WHICH MAY RESULT FROM LOSS OF PROFIT, LOSS OF REVENUE, BUSINESS INTERRUPTION, LOSS OF INFORMATION, OR OTHER PROPERTY DAMAGE, ARISING FROM USE OR IMPOSSIBILITY OF USE OF THE SERVICE, REGARDLESS OF WHETHER THE RIGHT OWNER AND ITS PARTNERS ARE NOTIFIED OF THE POSSIBILITY OF SUCH LOSS AND / OR DAMAGE. LIMITATIONS HEREIN SHALL NOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW.
  4. Section 6. General Recommendations It would be convenient to use an individual OS or a VM for testing (VmWare products are supported, such as free VmWare Player. Do not use VirtualBox). Do not test beta versions on computers storing important data! Errors that cause hang-ups and instable functioning of the system may sometimes lead to data losses. Make backups! Do not test beta versions on instable systems! In this case, it will be difficult for you to determine which reasons cause which issues, and whether those issues are associated with the product being tested. This is particularly evident for crashes and hang-ups. Please avoid spam the Forum with messages like ‘my system is hanging up, here is a 2 GB full memory dump, tell me what’s wrong’ at any incident. Please appreciate the developers’ time — some occasional hang-up may turn out to be absolutely unrelated. Do your best to reproduce the issue — first with Safe Kids, then without it. When testing a beta version, do not use OS skins other than the default one. Do not confirm and do not disprove issues found by other beta testers if you are not asked to. Remember that each of the testers has a unique hardware and software configuration, which may make errors vary. When publishing the details of an issue, specify the name of your OS, its bit number (32-bit or 64-bit), and the number of the Service Pack (if any). After a new build is published, please do not ask why a certain bug had not been fixed. It is just a matter of priority. Some bugs need more time. Warning! When connecting the SafeKids test (beta) version to the My Kaspersky portal (hereinafter referred to as Service), you agree that the Right Owner (Kaspersky Lab AO) provides the functionality of the Service intended for management and interaction with the application for testing ‘AS IS’. THE RIGHT OWNER AND ITS PARTNERS PROVIDE NO WARRANTIES REGARDING ITS USE, PERFORMANCE, AND AVAILABILITY. THE RIGHT OWNER AND ITS PARTNERS PROVIDE NO WARRANTIES, CONDITIONS, REPRESENTATIONS, OR STATEMENTS, EXPRESSED OR IMPLIED, WHATSOEVER, INCLUDING, WITHOUT LIMITATION, NON-INFRINGEMENT OF RIGHTS OF THIRD PARTIES, COMMERCIAL QUALITY, AVAILABILITY, INTEGRABILITY, OR FITNESS FOR PARTICULAR PURPOSE. YOU HEREBY AGREE TO ASSUME LIABILITY FOR SELECTION OF THE SERVICE, USE OF THE SERVICE, AND ANY RESULTS ARISING FROM THE SAID USE. THE RIGHT OWNER AND / OR ITS PARTNERS ASSUME NO LIABILITY FOR ALL AND ANY DAMAGES AND / OR LOSS, INCLUDING THOSE WHICH MAY RESULT FROM LOSS OF PROFIT, LOSS OF REVENUE, BUSINESS INTERRUPTION, LOSS OF INFORMATION, OR OTHER PROPERTY DAMAGE, ARISING FROM USE OR IMPOSSIBILITY OF USE OF THE SERVICE, REGARDLESS OF WHETHER THE RIGHT OWNER AND ITS PARTNERS ARE NOTIFIED OF THE POSSIBILITY OF SUCH LOSS AND / OR DAMAGE. LIMITATIONS HEREIN SHALL NOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW. --------- This topic will be closed and pinned at the top, marked as important. In case of any remarks, suggestions and comments on how to improve this instruction, or if you found an error or inaccuracy, please feel free to inform Mr. Volokitin.
  5. Section 5. Additional information 5.1. To obtain the logs from Process Monitor utility: 1. Download the utility at http://technet.microsoft.com/ru-ru/sysinternals/bb896645 2. Unpack and run it with the Administrator privileges 3. Enable extended logging 4. Reproduce the issue 5. Save the log 6. Send the log 5.2. Booting Windows in Safe Mode: - For Windows 8 use Shift+F8 instead of F8. Important! If you hold the testing in VmWare, then, right after Windows starts, make a click. This is required to provide the VM with access to the keyboard.
  6. Section 4. Creating a virtual machine 1. Create a new virtual machine 2. Specify that an OS will be installed later 3. Select the system to be installed 4. A virtual machine should be named so that it can be easily identified among other ones. A convenient location should be specified for the VM. By default, it is located at a rather deep level in the profile 5. Specify the maximum disk size. In Win7, 20 GB would be enough. In Windows XP, 10 GB would be enough. The most important point is selecting the disk type. It must be Split! 6. Everything’s OK. If you know that you need to edit some of the virtual hardware settings, you can do it by clicking the customization button. Usually this is not required 7. After creating the VM, just run it and install the system. Do not forget to install the add-ons (VmWare will prompt you to). Obtain the issue to be reproduced, shut down the system, and send the results
  7. Section 3. Sending critical information to Kaspersky Lab developers (MOST IMPORTANT!) To send information required for developers, please use the following file exchange resources: 1. ftp://safekids:safekids@data8.kaspersky-labs.com — logins and passwords for access to KL’s FTP are sent individually. Old credentials are also still valid. 2. cloud.mail.ru — requires registration with mail.ru 3. https://disk.yandex.ru — convenient and fast, but requires registration with Yandex 4. Screenshots should better be directly uploaded to the Forum (it allows this), or use http://savepic.ru with the "Do not resize" option. DO NOT USE Rapidshare and Depositfiles, because these services do not allow downloading multiple files in a row and are overfilled with ads. To upload files to ftp://data8.kaspersky-labs.com, please use the FTP client FileZilla or any convenient file manager (such as FAR or Total Commander). Please avoid using IE and, obviously, the "New -> Folder" option. In the course of testing, cases may occur when the application comes to a failure or the system crashes with the ‘blue screen’. If those crashes have been completely unexpected, please do not panic, try to remember all of your recent actions – you may have modified something or installed some programs. When describing the issue, try to remember when it first occurred, what preceded it, and what steps you took to solve it. Describe the issue in as much detail as possible and attach a memory dump in the ‘crashes and hang-ups’ topic. Do not forget to specify the build number and the OS name; the GSI report will also be welcomed. Kaspersky Lab employees may ask from you the following: 3.1 Traces at the moment the issue is reproduced, i.e., files logging all actions of Safe Kids components that would help developers to localize and solve that issue. Warning! By default, tracing is disabled in beta versions. To enable tracing: Open the settings Select the “Log run-time events” check box Folder to store traces: • For Microsoft Windows Vista/7/8/8.1 - %ALLUSERSPROFILE%\\Kaspersky Lab\ Trace files are created in TXT format with a unique name: SAFEKIDS _[Product version]_[Creation date]_[Creation time]_[Random symbols]_[Tracing type].log For example, SAFEKIDS.1.0.0.416_02.26_15.08_1548.log.SRV.enc1 Discard Safe Kids (by right-clicking the product icon in the tray -> Exit -> Enter valid data of parent account), find the generated trace files, archive them in ZIP, and send to one of the recommended file exchange resources (e.g., the FTP server at KL). After having sent your traces, inform developers by writing the name and the location of your archive in the corresponding topic. 3.2 Safe Kids memory dump. Diagnostics of the product’s crashes and hang-ups requires a memory dump of Safe Kids, i.e., a file where all information about the product’s status is recorded at the moment of a crash. A special notification from the product will inform you of a crash and creation of a memory dump. To send your dump to developers, go to the following folder: For Microsoft Windows Vista/7/8/8.1 - %ALLUSERSPROFILE%\Kaspersky Lab\ Memory dump files are created with the .dmp extension, having a unique name: SAFEKIDS.[Product version]_[Creation date]_[Creation time]_[Random symbols].[Dump type].dmp For example, SAFEKIDS.1.0.0.416_02.26_15.08_1548.GUI.full.dmp Find the memory dump files (they are 3, as a rule), DO archive them, and send to any file exchange service or our corporate FTP server. After having sent the memory dump file, inform developers by writing the name and the location of your archive in the corresponding topic. How to obtain a memory dump when SAFEKIDS is hanging up: Using Task Manager in Windows Vista/7: http://support.kaspersky.ru/wks6mp4/error?qid=208635660 — Windows 7, Vista Using windebug: If you have Debugging Tools for Windows installed, you can obtain a dump of a process that is hanging up by attaching to it with WinDBG and typing the following command: .dump -ma C:\SafeKids.dmp 3.3 System memory dump is a file where all information about the RAM contents is logged, as well as information about the system’s status at the moment of a crash. Diagnostics of reasons of the ‘blue screen’ or a hang-up requires the full system memory dump. Such bug reports will not be approved without dumps. How to obtain a memory dump at a system crash (‘blue screen’): http://support.kaspersky.ru/wks6mp4/error?qid=208636026 — Windows 7/8/8.1, Vista Warning! A swap file is created when creating a dump. Do not disable this swap file and do not make it lower than the size of the RAM, otherwise the dump will be ‘cut down’. In case of a system hang-up, a full memory dump is required. In systems with the RAM size more than 2 GB, you can enable it by limiting the volume of memory to be reserved by means of msconfig. How to obtain a memory dump at a hang-up: 3.3.1 If the system avoided a complete hang-up, you can use a dedicated utility that initiates the ‘blue screen’ on demand: startbluescreen — http://www.nirsoft.net/utils/start_blue_screen.html Enable creation of a dump at a crash of the system and run the command on behalf of the Administrator StartBlueScreen.exe 0 0 0 0 0 The "0 0 0 0 0" zeroes here act as a command prompt parameter that is required to prevent an occasional startup of the utility. Any digits may be inserted instead of those zeroes; they will be shown on the ‘blue screen’ as the error code. 3.3.2 If the system does not respond to the user’s actions, the manual run of the ‘blue screen’ will be used by means of the keyboard driver, by pressing Ctrl-ScrollLock*2 : for a PS/2 keyboard: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters] "CrashOnCtrlScroll"=dword:00000001 for a USB keyboard: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid\Parameters] "CrashOnCtrlScroll"=dword:00000001 The procedure is as follows: add the parameter to the registry, reproduce the hang-up, hold Ctrl and press Scroll Lock twice. The ‘blue screen’ should appear. For more detailed instructions (how to add a parameter to the registry, etc.) see: http://support.kaspersky.ru/kis2010/error?qid=208636405 — Windows 7/8/8.1, Vista After reproducing the case and retrieving a memory dump, go to the folder that you specified when configuring the dump creation, find the file named MEMORY.DMP, DO archive it in ZIP, and send it to a recommended file exchange service (e.g., the FTP server at KL). After having sent the memory dump file, inform developers by writing the name and the location of your archive in the corresponding topic. 3.4 An alternate option is using Debugging Tools for Windows. 3.4.1 How to obtain a dump of a process that is hanging up In XP/Vista/7 (x86/x64). Download this utility: http://www.microsoft.com/whdc/DevTools/Deb...ng/default.mspx Select the right one (x86 or x64) according to the bit number of your OS. Install it. Set windbg as the default debugger. To do this, run cmd with the Administrator privileges, then go to the folder of installed windbg (e.g., cd %programfiles%\Debugging Tools for Windows (x86)), and here you can run windbg with the I parameter: windbg.exe -I A message must report that windbg has been successfully set as the default debugger. When the process hangs up, run windbg (you are recommended to create a shortcut on your desktop) with the Administrator privileges (it is important for UAC, you can specify this right in the shortcut properties), attach it to the process (File -> Attach to process, or just press F6). After it is attached, make a process dump using this command: .dump -ma C:\123.dmp Command ".dump -ma" (starts with a dot), C:\123.dmp — path to the file (name may vary, but the specified folder must exist). WinDBG will inform you of a successful creation of a mini dump, but actually the dump will be full due to the use of the "-ma" options. 3.4.2 How to obtain a dump of a process that crashed As windbg is the default debugger (after it is run with the –I key), it will automatically capture a process crash and display it in its window. Use the same command: .dump -ma C:\procname.dmp 3.5. Installation log for debugging and solving issues that arise when installing or removing the product. See Knowledge Base to know how to retrieve it. After obtaining a trace file, you should archive it and attach it to your new message on the Forum. http://support.kaspersky.ru/faq/?qid=180593905 3.6 GSI report. GetSystemInfo (GSI) is a dedicated utility that collects information about the system, drivers and applications installed, processes run, etc. See Knowledge Base to know how to retrieve a report. GetSystemInfo must be run under an account with the Administrator privileges. DO archive the GetSystemInfo report in ZIP and attach it to your new message on the Forum. Knowledge Base article — How to retrieve a report from GetSystemInfo Video — http://support.kaspersky.fr/camille/videos/GSI/ 3.7 Screenshot is an image of the screen. Please avoid using third-party resources such as Radikal, attach screenshots to your message on the Forum instead.
  8. Section 2. Sending bug reports During the beta testing, the Forum undergoes moderation: messages that are not bug reports will be deleted from dedicated topics. When sending a bug message, please specify the following: 1. Number of the build and name of the OS on which the issue has occurred (attaching a GSI report is recommended) 2. Whether this issue is stable and recurrent, i.e., whether you can reproduce it 3. Steps that you have taken to encounter it again 4. Outcome that you have expected at that 5. Outcome that you have faced (i.e., the nature of the bug) 6. Please save the trace file valid at the time the bug has occurred (see Section 3.1 below). If you test the product on Windows 7/8/8.1, you can record the steps of the bug occurrence by means of “Windows Error Reporting Problem Steps Recorder”. After you have sent a bug report, you may be asked some additional questions (see Section 3). After that, the moderator creates a bug record and specifies its number in an open topic with the issue specified, which means that the bug is under review, with all information required to reproduce and fix it. The release of a next build does not mean that the issue that you had reported on was already fixed: fixing may be postponed or rejected. Bugs are fixed in accordance with their priority: the more crucial a bug is — the more resources are allocated to fix it. Dedicated topics are opened for bug reports and comments on components: Application Control A component designed for: • blocking • collecting statistics on applications run by the child. It also focuses on bugs related to incorrect categorization of applications. Web Control A component designed for: • blocking • warning • collecting statistics • monitoring search queries for the child’s activities in the web browser. It also focuses on bugs related to incorrect categorization of websites and search queries. Device Usage Control A component designed for: • blocking upon a limit or a schedule • soft blocking (warning) upon a limit or a schedule • collecting statistics on the device used by the child. Reproducing crashes of the product (scenarios, dumps) Dumps of crashes of the product and scenarios leading to those crashes and to unexpected exits from it. Interface Interface bugs: misprints, badly fitting items, etc. Issues of bad usability After a new build is published on the server, a ‘main’ topic is created specifying the name and number of the current beta build «Discussion ###». If you do not know for sure in which section you should send your bug report, please post it in this topic with a certain indication of the bug report. Suggestions for improvements Collected here are all sound suggestions for improvements in the functional scope and new features that should be implemented in the final version of the product.
  9. Section 1. Downloading and installing the beta version To start beta testing, do the following: 1. Register with the portal (center.kaspersky.com) 2. Go to the Children (Bета) tab 3. Create a child’s profile 4. Download the distribution package on the “Child’s devices” (setup.exe). The release of each new build of the beta version will be announced in a dedicated topic that will be marked as important in this thread. The topic with the old version will be bumped. After the next beta version is released, you should install it to replace the previous one. To do this, download the distribution package of the latest build, discard the current product, and remove it using the standard scenario (using ‘Uninstall or change a program’). After that, you can start installing the new beta version. Warning! Do not install the new beta build over the old one (unless you have been asked to).
  10. Guidelines on Forum Testing In this section of the Forum, an open beta testing of Kaspersky Safe Kids is held. Beta version is a special, officially released version of a product intended for external testing, which aims at finding errors and bugs in the product, as well as collecting various opinions and comments on it. After the product is finally developed and the technical release is announced, the most active beta testers who have significantly contributed to the result will be rewarded with a one-year free license for the tested product. Features of the beta build: • Tracing and Application Verifier are disabled • Kaspersky Lab (including Technical Support) assumes no liability for the functioning of the beta version • After the beta testing period expires, the beta build goes inoperable, thus lifting off the protection and completely disabling the product’s functionality.
  11. Getting Started Go to http://center.kaspersky.com for registration. Warning! When connecting the SafeKids test (beta) version to the My Kaspersky portal (hereinafter referred to as Service), you agree that the Right Owner (Kaspersky Lab AO) provides the functionality of the Service intended for management and interaction with the application for testing ‘AS IS’. THE RIGHT OWNER AND ITS PARTNERS PROVIDE NO WARRANTIES REGARDING ITS USE, PERFORMANCE, AND AVAILABILITY. THE RIGHT OWNER AND ITS PARTNERS PROVIDE NO WARRANTIES, CONDITIONS, REPRESENTATIONS, OR STATEMENTS, EXPRESSED OR IMPLIED, WHATSOEVER, INCLUDING, WITHOUT LIMITATION, NON-INFRINGEMENT OF RIGHTS OF THIRD PARTIES, COMMERCIAL QUALITY, AVAILABILITY, INTEGRABILITY, OR FITNESS FOR PARTICULAR PURPOSE. YOU HEREBY AGREE TO ASSUME LIABILITY FOR SELECTION OF THE SERVICE, USE OF THE SERVICE, AND ANY RESULTS ARISING FROM THE SAID USE. THE RIGHT OWNER AND / OR ITS PARTNERS ASSUME NO LIABILITY FOR ALL AND ANY DAMAGES AND / OR LOSS, INCLUDING THOSE WHICH MAY RESULT FROM LOSS OF PROFIT, LOSS OF REVENUE, BUSINESS INTERRUPTION, LOSS OF INFORMATION, OR OTHER PROPERTY DAMAGE, ARISING FROM USE OR IMPOSSIBILITY OF USE OF THE SERVICE, REGARDLESS OF WHETHER THE RIGHT OWNER AND ITS PARTNERS ARE NOTIFIED OF THE POSSIBILITY OF SUCH LOSS AND / OR DAMAGE. LIMITATIONS HEREIN SHALL NOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW. Installing Kaspersky Safe Kids 1. Run Setup.exe on the device and install Kaspersky Safe Kids following the Setup Wizard’s instructions. 2. After completing the installation, run Kaspersky Safe Kids. 3. The Protection Setup Wizard runs on the device immediately after the installation completes. At the first step you will be prompted to: - Create a new My Kaspersky account - Log in under an existing My Kaspersky account. 4. Enter your credentials in the corresponding entry fields and click the "Sign in" button. 5. A form opens that contains the newly created profile of your child. The check box next to his or her userpic is selected, which indicates that he or she is currently protected on this device. Click "Add child’s account" if you need to create profiles for other children who have remained unprotected by the system. When all the children are selected, click the “Continue” button. 6. You will then be redirected to a form for selection of the operating system account that the first child on the list will use. Click the "Create new account for this child" button to create a new account that will use the child’s name as the login. 7. If some of the accounts that you have selected had not been password-protected, you will be able to set passwords for them at the next step. In order to ensure a comprehensive protection, each of the children must use the dedicated personal account only, without any access to other ones. 8. In the final window, click the "Finish" button. 9. Now you have to log in to the system under a child’s account in order to enable the protection. Congratulations! You have successfully protected your child! He or she is now protected at the level set for his or her age by default. Let us get acquainted with the restrictions set for your child, and learn how to manage them using My Kaspersky portal. Applying and modifying restrictions for a protected child 1. Open My Kaspersky portal and select a protected child. 2. On the page that opens, select the "Child protection rules" tab. 3. The tab that opens provides the following sections to desktop users: - Internet protection (setting up the access to various websites by categories or using the whitelist/blacklist method) - Applications (setting up the access to installed applications websites by categories or using the whitelist/blacklist method) - Time of use (limiting the device’s use by total time or upon a schedule). 4. Let us specify the following settings, e.g.: - In the "Internet protection" section, we block the "News" category, we enable “Warn” for the "Electronic commerce" category, and we add the website http://www.nbcnews.com/ to the white list. - In the "Applications" section, we block the "Multimedia" category. - In the "Time of use" section, we set the "Warn" action on "Hours a day" and set the restriction on "No more than 30 minutes" on Sunday. Now you can log in to the child’s account and check the restrictions that you have set. 6. Try to open a website from a blocked category using any web browser. Access to the website will be denied, the following warning will be shown: Clicking the "Back" button will return you to the previous page. The “Login for parents” button allows you to pause the protection on the device and obtain access to the website, but this requires entering the credentials of the parent’s My Kaspersky account. After the protection is paused, visiting the website will be allowed. 7. Try to open a website from an ‘unwanted’ category for which the "Warn" action has been specified in the settings. The following warning message appears: Clicking the "Back" button will return you to the previous page. The "Go there anyway" button allows you to open the website, but this action starts an invisible timer that records the time you spend on the website. The timer stops when you close the website, minimize the browser window, or switch to another tab. 8. Try out the entire protection provided by Safe Kids and make sure it is reliable and flexible! Try to run an application from a blocked category, open a website from the white list, wait until the expiration of the time period set for the device’s use. 9. Every child’s action resulting in a blocking will be logged into reports. You can view them in My Kaspersky Personal Cabinet, on the "Reports" tab, as well as in pop-up notifications. Parent mode What to do if you need to change the system account for your child? Or if you need to enable the protection for a second child? Or if you need to add a new profile? The "Parent mode" is provided for all of these cases. 1. Log in to the device under your child’s account. 2. Click the product icon in the tray. 3. In the window that opens and shows information about the active protection of your child, click the "Parent mode" button in the bottom right corner. 4. Enter the credentials of your My Kaspersky account. 5. A window opens where you can: - add a new child - change the active account for a protected child - lift the protection off a child on this device. Warning! As long as you remain in this form, the entire protection is paused for the current account. Uninstalling If you or your children are tired of Safe Kids, you can remove it in any moment using the standard Windows scenario: Control Panel -> Programs and Features -> select Kaspersky Safe Kids. To uninstall the product, you will have to enter the credentials of your My Kaspersky account. This is required to protect you against an unauthorized removal of the product.
×
×
  • 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.