Jump to content

Carl S

Members
  • Content Count

    61
  • Joined

  • Last visited

Kudos

  1. Upvote
    Carl S gave kudos to itman in PowerShell/Runner.G   
    Just be careful about deleting stuff from the registry. Either back it up first, or export any keys being modified/deleted prior to any registry cleaning exercise.
  2. Upvote
    Carl S gave kudos to itman in PowerShell/Runner.G   
    I suspect what the malware did was a registry Import or equivalent to get around Eset's detection of the malicious code.
  3. Upvote
    Carl S gave kudos to itman in PowerShell/Runner.G   
    Also checkout this reg key: HKCU:\Software\AppDataLow\Software\Microsoft\D4062752-23C4-26DB-4D48-07BAD1FC2B8E .This is what the PowerShell script was using.
    Have a feeling the "D4062752-23C4-26DB-4D48-07BAD1FC2B8E" sub-key has to go along with possibly the actual D4062752-23C4-26DB-4D48-07BAD1FC2B8E key itself.
  4. Upvote
    Carl S gave kudos to Marcos in Disappointment   
    As for Windows 7 support, we still have products that officially support Windows XP that Microsoft stopped supporting in 2014. That said, we don't plan to stop supporting Windows 7 any time soon and it should continue to be supported in the next few years.
    The certificate issue concerned older products, namely Endpoint 5 being currently in basic support phase and to reach EOL by the end of this year as well as Endpoint 6.5 which is in the limited support phase. In spite of limited and basic support, we treated the issue with priority and worked day and night to deliver fixes to affected users.
×
×
  • Create New...