• Content count

  • Joined

  • Last visited


About fr33tux

  • Rank
    Advanced Member

Contact Methods

  • Website URL
  • Jabber

Recent Profile Visitors

1,182 profile views
  1. Hello, Thanks. Just let me some time to review them and I'll answer by Tuesday night (sorry in advance for the delay).
  2. Hello, Thank you, it's fixed. Sorry for the inconvenience.
  3. Hello, Ok, it's better but not sufficient, so we'll begin by the basics: Relaunch frst Right-click on the file -> "Execute as Administrator" Click on the "Scan" button The logfile is saved as FRST.txt , and additional informations are in Addition.txt. Please host them on Up2Share and share the generated link Thanks,
  4. Hello, Sorry, it's my fault - Can you do the same procedure than my previous message, but using this fixlist.txt file? Thanks,
  5. Hello, Thanks. Download FRST Download fixlist.txt file and save it to the Desktop (with the name "fixlist.txt") NOTE. It's important that both files, FRST/FRST64 and fixlist.txt are in the same location or the fix will not work. NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system. Run FRST/FRST64 and press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished FRST will generate a log on the Desktop (Fixlog.txt). Please post it to your reply. Thanks,
  6. Hello, Thanks. Can you use the latest MB3.1 and re-do a scan with it? Thanks,
  7. Hello, @scuzzyfuzzy Can you share MB3 logfile if you tried it? Thanks,
  8. Hello, Can you do the cleaning process with this service unchecked?
  9. Hello, AdwCleaner 6.047 has been released! ///////// v6.047 - 19/05/17 //////// [UPD] - Database 2017-05-19.1 [ADD] - Add informative message for Chrome synchronization Once again, this version brings a lot of new detections. Thus I really encourage all users to update, especially those using AdwCleaner offline. It also backports a feature from v7: when Chrome has been infected with malicious extensions or settings, an informative message will be shown in the logfile to explain how to reset the Chrome Synchronization. It can be a necessary manual step in order to fully complete the cleaning process. AdwCleaner v7 release will follow. The rules migration from the legacy system to the new one takes some time, but it's an important step which we'll really benefit from after the release. The new/refreshed UI will stay private for now (but stay tuned! :)), but please see below a screencast of the scanning speed as tested on one of our test machine. It's in real conditions, without any optimizations or whatever. It should be really close to the scanner speed we'll see as the public release: The private beta should open pretty soon - we'll keep you informed. As usual, you can get AdwCleaner from the download page:
  10. Hello, Thanks. So I encourage you to clean everything. If ever you would still like to keep Acestream, simply uncheck the related elements.
  11. Hello, Cam you provide the logfile? Usually from C:\AdwCleaner. Thanks!
  12. Hello, Thanks for the feedback.
  13. Hello, Sorry, it's my fault. It's now fixed!
  14. Hello, Please stay friendly and welcome to each other Please contact them for this FP, I'm doing the same. Thanks,