Jump to content

itshero

Members
  • Content Count

    40
  • Joined

  • Last visited

About itshero

  • Rank
    IT Sidekick

Profile Information

  • Gender
    Male
  • Location
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Paul Are there any issues of doing this? Uninstall KES 10 SP1 M3 / REBOOT INSTALL KES 10 SP2 MR3 INSTALL WIN 10 1903?
  2. Here is the response I got from a Pulseway team member: Hi [Redacted], There are some known issues. Note- 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. Paul confirmed that it is rolling out next week to me in a PM. Hope it's true!
  4. I have yet to see this work in our environment! Please help! I cannot deploy a PC without AV on it!
  5. @Paul That didn't do anything. Edit: It works after getting pushed the update... Thanks!
  6. @Paull this doesn't work. My device is indeed listed.
  7. @PulsedAway 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.
  8. @kelton5020 Indeed. I posted on another thread because I never got a reply from a pulseway employee. Apparently they acknowlege the issue, but they aren't getting a reply from their app devs. Obviously a big disconnect between support and their outsourced app developers!
  9. @Paul Any heads up on this issue? It's been over a month.
  10. @Chris This isn't the case. That post is from 2017. Current version of Android is 9.0 and in 2017 it was 8.1.
  11. @Paul I would appreciate to know what they have to say if it will be addressed.
  12. Not the case for me. My device is listed on it.
×
×
  • Create New...