Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by itshero

  1. On 8/13/2019 at 6:43 AM, Paul said:

    Hi everyone,

    We've released the KES 10 SP2 MR3 to everyone however the in-place upgrade function remains disabled as it's known to cause problems. We've reached to a conclusion with Kaspersky Labs that the following process is safer to upgrade KES 10 SP1 MR3:

    • Uninstall KES 10 SP1 MR3
    • Reboot the computer
    • Upgrade the system to 1903 if it's Windows 10 (if the 1903 update was already installed and it automatically uninstalled KES 10 SP1 MR3 then you need to run the KAV removal tool)
    • Reboot the computer
    • Install Kaspersky (it will automatically deploy KES 10 SP2 MR3)

    Please let me know how this goes for you.



    Are there any issues of doing this?


    Uninstall KES 10 SP1 M3 / REBOOT 


    INSTALL WIN 10 1903?

  2. Here is the response I got from a Pulseway team member:


    Hi [Redacted],
    There are some known issues.
    We are ready with the update and have released to 15 early access customers. 8 out of 15 early access customers have reported that some systems have upgraded correctly and some have encountered problems.

    Here's the list of known issues with the KES 10 SP2 MR3 update:
    a) Fresh installation might fail if the system had KES 10 SP1 MR3 installed, upgraded to 1903, Windows automatically uninstalled KES 10 SP1 MR3. Workaround: Run the KAV removal tool and install all available windows updates,then the KES 10 SP2 MR3 application will install. This only affects Windows 10 1903 systems;
    b) After the upgrade from KES 10 SP1 MR3 to KES 10 SP2 MR3 the system would be stuck at login with the spinner and a black screen. On a particular customer, we've seen 32 systems out of 100 affected,including Windows 10 1809 and Windows Server installations. The fix for this is to uninstall the KES 10 SP2 MR3 completely from the machine. Sometimes the machine hangs in a way that you cannot send the uninstall command from the WebApp forcing you to run the KAV removal tool from safe mode (obviously requiring IP KVM or physical access to the machine);
    c) On a very small number of cases (less than 5 reported), the KES 10 SP2 MR3 update would corrupt the Windows component user32.dll completely breaking the windows installation. No known workaround for this case.

    Kaspersky Labs is aware of all issues and is currently investigating this with our development team. We're going to be making a decision this week on what's the next step here.
    If you still want to proceed further, please let me know. 
  3. On 11/14/2018 at 11:32 AM, PulsedAway said:

    I'm also having the same issue.  I've had the app for years and recently switched from a Pixel 2 XL (running Pie) to a OnePlus 6T (running Pie).  I no longer get notifications.  I have checked both the web app and the settings on the phone.  Nothing helps.  Honestly, the value of the service is greatly diminished without notifications.

     Is Pulseway going to address this?



    Their response has been that it is a bug... WITH the OS itself.  Not the case.  If that were the case my push notifications would be broken on all of my apps (and that is nowhere near true)  Pulseway is the only app with this issue on my phone.  

  4. On 9/28/2018 at 5:43 AM, SyntechCS said:

    Don't know if you managed to solve this but I recently had the same problem and it turned out that my phone had been deleted from the authorised devices in the Pulseway webapp, simply rebooted my phone and it re-registered with the webapp and started receiving notifications.

    Not the case for me.  My device is listed on it.

  5. On 9/14/2018 at 2:18 PM, Paul said:

    Hey everyone,

    I've just found out that this is a more wide spread issue as it's affecting other apps as well. It appears to be due to an update: https://productforums.google.com/forum/#!topic/phone-by-google/Nfqx7JT0J9g.

    Go to Battery – Settings (three vertical dots) – Battery Optimization, open the All apps section from the drop down menu, go to Pulseway, and tap on “Don’t optimize.”. Let me know if this resolves the issue.



    I tried this with no success. Also tried other recommendations on that thread.  

  6. 21 hours ago, Paul said:

    Hi there,

    I've checked your account and I can see that everything is setup properly (I see that it was registered 27 minutes ago). Can you try again to see if PUSH notifications are sent to your Pixel 2 XL or they only reach out your iPhone and iPad?



    I did not receive any notifications when they popped up.

  7. On 4/9/2018 at 8:03 AM, Paul said:

    Hi Jim,

    First of all the Pulseway app doesn't need to be started for you to receive PUSH notifications. The fact that you're not getting any PUSH notifications after you close the app is not intended and we're going to be investigating this issue and come back at you as soon as I get an update.


    I don't get notifications on Pixel 2 XL either... what gives?  Everything is setup on my account fine all other apps on my phone that are setup to receive notifications do.

  • Create New...