Jump to content

jboursier

Staff
  • Content Count

    878
  • Joined

  • Last visited

Community Reputation

0 Neutral

5 Followers

About jboursier

  • Rank
    Elite Member

Contact Methods

  • Website URL
    https://fr33tux.org
  • Jabber
    fr33tux@jabber.otr.im

Recent Profile Visitors

5,328 profile views
  1. Hello, @CeeBee I got your PM too We'll see what we can do for that in the future based on all the feedback we get. I'll follow up if there is any change in this regard. Regards,
  2. Thanks for your feedback. We indeed have reports that legacy AdwCleaner versions still work on XP, but as explained above we don't recommend it. Instead, please update your operating system as this is the first line of defense. Regards,
  3. Hello, @IanHawk This was a known issue with AdwCleaner 8.0.6, fully resolved in 8.0.7. Please update and let me know if you still face any issue,
  4. Hello, @PharazirAdwCleaner doesn't install anything. To remove it, you simply have to manually delete `AdwCleaner.exe` and the directory (usually C:\AdwCleaner). You can also do it from AdwCleaner directly, with the button at the bottom of the Settings page. Otherwise, for the cmd.exe window that is displayed during a very short period of time (less than a second usually) it is expected. Please see the notes from 8.0.7: There is nothing to worry about with it. Regards,
  5. Hello, We're pleased to share AdwCleaner 8.0.7. Its main additional feature is the new ability to change the working directory location when the default (C:\AdwCleaner) is blocked by some infections preventing AdwCleaner to run. Until now AdwCleaner was defaulting to the "AdwCleaner" directory right in system drive, and since 8.0.7 it is possible to specify other paths as necessary. This is only exposed to the CLI for now as it is an advanced mitigation. To use it, simply pass `/path C:\your\custom\path\to\AdwCleaner\directory` to any CLI calls. Note that you need to enclose the
  6. Hello, To follow up, we've fixed this issue in 8.0.7 that will be released this week. Regards,
  7. Hello, This is fixed in 8.0.7 that will be released shortly. In the meantime, you can find the logfiles manually in C:\AdwCleaner\Logs if needed. Regards,
  8. Ok, thanks for the details, this helps. I'll get back to you shortly.
  9. Hello, Can you give more details? What do you mean by that: ? What works differently? Thanks,
  10. Hello @CeeBee, How long is the cmd window displayed for you? It should be fairly quick. Thanks,
  11. Hello, We indeed don't support XP any longer. Please update your Windows version, as it's impossible to protect a network-connected Windows XP nowadays.. Best regards,
  12. Hello, We are pleased to announce AdwCleaner 8.0.6, which despite its version number is a major milestone that contains a long-awaited feature: the command-line interface. AdwCleaner CLI allows you to programmatically use AdwCleaner without having to interact with the graphical interface. It makes it easy to integrate it with your workflow and environment, even in a GUI-less remote session! The command line interface is consistent with the GUI version, so comes with two modes: Scan: `/scan` Only do a scan, but do not clean. The only difference with the GUI is that Preinsta
  13. Hello! We just released AdwCleaner 8.0.5. This is mostly a maintenance release, focused on modernization for dependencies: ## v8.0.5 [25/05/2020] ### Changes * Update Qt to 5.14.1 * Update OpenSSL to 1.1.1g * Update UPX to 3.96 * Update definitions to 2020.05.13.1 The next release will be focused on actual new (and exciting) features. Stay tuned! As usual, you can download the 8.0.5 from the product page: https://malwarebytes.com/adwcleaner
  14. Hello, Thanks for the suggestion! Same than the first one, I can't commit on an ETA but I've added it to the backlog. Keep your suggestions going, they're helpful 👍 Regards,
Back to top
×
×
  • 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.