Jump to content


  • Content Count

  • Joined

  • Last visited

About paulderdash

  • Rank
    Regular Member

Recent Profile Visitors

964 profile views
  1. That Agomo key does exist now, but it's not detected, so the previous one was bad but the new one is OK.
  2. Scanned again and now it's not detected, so cleanup was good. Seems to be picked up during memory scan. Well done MB3. Thanks Ms Moes.
  3. I did have CCleaner 5.33 installed, but x64 version so I do not believe I was compromised. These keys seem to be due to CCleaner Cloud. I presume I did have the compromised version of that, but it has been auto-updated to clean version. If I quarantine these keys, after a restart I have to login to CCleaner Cloud account again and looks like keys are recreated. I will run scan again to see if it gets picked up again.
  4. Actually it may have been a temporary problem. Seems to be working now, but very slow!
  5. Updated two machines to using Ninite updater. Everything is working but when I try and access 'My Account' I get this pop-up on both machines: Unable to contact license server. Check your network settings or contact your system administrator for help. I have previously had a similar problem (below) but now I am getting this on both machines, different software. Is the license server down, or is there a simple solution.
  6. I have Windows x64 and (now) CCleaner 5.34 - and up-to-date CCleaner Cloud(!) - and do not have the HKLM/SOFTWARE/Piriform/Agomo key. But MB3 scan now picks up the following threats: Registry Key: 1 Trojan.Floxif.Trace, HKLM\SOFTWARE\WOW6432NODE\PIRIFORM\AGOMO Registry Value: 1 Trojan.Floxif.Trace, HKLM\SOFTWARE\WOW6432NODE\PIRIFORM\AGOMO|TCID But these appear to be related to CCleaner Cloud (previously Agomo) account, because after quarantining these, I had to re-sign in to my account, so I suspect these may be FPs. MB3.txt
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.