Jump to content

34Dell17

Members
  • Content Count

    6
  • Joined

  • Last visited

About 34Dell17

  • Rank
    Candidate
  1. That worked. It took a second try, as I saw the Safe Money window flashing but there wasn't the bubble asking if I wanted to install the add on the first time.
  2. In previous versions of Firefox, the first time safe money launched it would prompt to install any available add on packages (even those no longer installed in the original web browser). Since reinstalling alongside the new version of Firefox, the same thing occurred except with password manager. This baffled the person in the 24/7 chat even though they previously sorted out manually installing the Kaspersky Certificate.
  3. Also, The only things that will change are a warning in My Kaspersky (which can be ignored) unless another VPN is recognized, and a few Firewall settings (that would start KSC instead of giving you a notification) will become changeable.
  4. Really, I just tried this yesterday where I added the computer to the My Kaspersky account first (remote control might be needed here), and then an option to add that computer to my internet security license appeared. Presumably, this uses the same mechanism that can trigger remote scans and updates, so that 2 minutes after clicking the button a push is sent with the license in it.
  5. Kaspersky doesn't fully support this build of windows yet (hence the large yellow banner on their support site) and, likewise, several drivers haven't been fully integrated. In my case, safe money causes Firefox to run really slowly for a few seconds, presumably as the driver tries to start and then terminates as something goes wrong.
  6. I recently installed the Education version of Windows 10 Build 1607 (anniversary update), but now the Safe Money Screenshot driver will not start regardless of what I attempt. Everything suggested in the help page including BIOS Virtualization, ensuring other processes aren't hogging the virtualizer, checking Task Manager for an "Enabled" status has been checked and found to be in the correct state already. Everything worked fine in the previous build, but this clean install seems to have problems, especially with Low Trust windows files that were only detected 8 days ago.
×
×
  • 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.