Jump to content

jboursier

Staff
  • Content Count

    871
  • Joined

  • Last visited

Everything posted by jboursier

  1. Ok, thanks for the details, this helps. I'll get back to you shortly.
  2. Hello, Can you give more details? What do you mean by that: ? What works differently? Thanks,
  3. Hello @CeeBee, How long is the cmd window displayed for you? It should be fairly quick. Thanks,
  4. 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,
  5. 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 Preinstalled Applications will not be listed and thus not selected for being quarantined - see `/preinstalled` below. Clean: `/clean` Scan and automatically clean all detected elements. This will also automatically reboot the computer afterwards to complete the cleaning process. Help: `/?` Display the CLI usage information. In addition, several options are available: `/eula`: Accept the EULA. This is only needed once per machine. `/noreboot`: Do not automatically reboot after the cleaning process. `/preinstalled`: Include Preinstalled Application in the detections and move them automatically to quarantine during cleaning. Use with care. The location of the log files and quarantine are not changed compared with the GUI. They are usually located in C:\AdwCleaner. This path will be customizable in the next release, so you will be able to choose the logfile location. If no command line arguments are present, then the usual GUI will show up. Usage example: * Scan only: AdwCleaner.exe /eula /scan * Scan, then clean and reboot: AdwCleaner.exe /eula /clean * Scan, then clean but do not reboot: AdwCleaner.exe /eula /clean /noreboot * Use the Graphical interface (same executable): AdwCleaner.exe We hope that this version will help you to make your work easier. We will add more features in the next releases (ability to customize the logfile output, to empty the quarantine, etc..) but we want to hear from your usage and experience with AdwCleaner CLI. As usual, the whole changelog is available below: ## v8.0.6 [01/07/2020] ### New Features * Command line interface to scan and clean without the GUI. More details in the release announcement. ### Bugfixes * Fix reintroduction of DLL loading vulnerability reintroduced in 8.0.5. AdwCleaner (both CLI and GUI) can be downloaded from the usual place: https://www.malwarebytes.com/adwcleaner
  6. 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
  7. 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,
  8. Hello, Thanks for the suggestion! We'll see what we can do in this regard, but not ETA for its implementation unfortunately. Regards,
  9. @hake Can you share any details regarding AdwCleaner's behavior in this case? Is there any error message or anything else? And you're saying that with ASLR disabled AdwCleaner runs fine?
  10. Hello, @hake Thanks! It's an interesting one.. We're looking into why this is happening.
  11. Hello, it's ok now, sorry for the issue.
  12. Hello, We are pleased to release AdwCleaner 8.0.4! This versions is purely focused on maintenance to fix a bug that got reintroduced ( CVE-2020-11507) We updated the test suite to avoid this to happen again. See the full changelog below: ## v8.0.4 [03/04/2020] ### Changes * Update definitions to 2020.04.03.1 ### Bugfixes * Fix reintroduction of DLL loading vulnerability reintroduced in 8.0.3 (CVE-2020-11507) To download AdwCleaner 8.0.4, click here.
  13. Hello, Can you reach me by email and share more details into your requirements? (mailto:jboursier{AT}malwarebytes[dot]com) Thanks,
  14. Hello, As usual, thank you for the feedbacks, be sure they are very well appreciated. At first I wasn't convinced it was a FP since this GUID is related to an existing infection. But looking deeper at the detection rule actually showed that it had a FP effect which is now fixed (updated definitions are already published). Thanks for your help,
  15. Hello, We are pleased to release AdwCleaner 8.0.3! This mostly bring internal changes so it's not as we can call an exciting release, but it paves the way for what's coming next in a few weeks. We introduced the web extension ID in the logfile alongside its name. This will make it easier to manually identify the extension and look it up on the related web browser addon catalog. In parallel, we have been tracking various isolated crashes for the past months and they tend to be hard to properly identify. This release thus ship with an improved crash handler that will be trigger in the case AdwCleaner doesn't work properly. And related, we have been working on the internal unit test suite to improve its coverage in the hope that the new crash handler will never be put in good use See the full changelog below: ## v8.0.3 [02/03/2020] ### New Features * The logfiles now contains webextensions ID in addition to their name. ### Changes * Improve the error handler to (hopefully) catch more isolated crashes as they occur. * Update definitions to 2020.03.02.1 * Improved unit tests. To download AdwCleaner 8.0.3, click here. We expect the next release to happen later this month. Please share with us your feedback!
  16. Hello, We are pleased to announce that AdwCleaner 8.0.2 is now released! This release brings exciting new features, as well as important bug fixes. The new capability to put under a spotlight is the reintroduction of the Hosts file scanner in order to detect any malicious redirections. Theses new detections are quarantined and each deleted line can be restored individually later on using the Quarantine. We also took a major stab at refining the translations compared to the previous releases, as some of these were starting to age - we covered the most used languages for this release, but the full-coverage should be done by next release. This version also introduces a 3 months-free MB4 license key for new AdwCleaner users. You may see it at the end of the cleaning process. As usual, the changelog is available below: ## v8.0.2 [30/01/2020] ### New Features * Ability to scan Host files for Malicious Entries. * Enhanced URL scanning for Chrome and Firefox extensions. ### Changes * Integrated new marketing campaign to provide new AdwCleaner users with a 3 month Premium Malwarebytes 4 key. * Update definitions to 2020.01.24.1 ### Bugfixes * Fixed issue in windows restoration point getting listed correctly. * Major translation update. To download AdwCleaner 8.0.2, click here. We expect the next release to happen sometimes around the third week of February. Please share with us your feedback!
  17. @HempOil Thanks for your questions. 1. Yes, it gathers logs for all Malwarebytes products, including AdwCleaner. It also provides us diagnostic information that we hope can help to pinpoint the issue. 2. Sure, feel free to send me a private message instead. (The content will only be shared with AdwCleaner development team afterwards) Thanks!
  18. Hello, Can you follow those steps to use MBST and generate more logs for us to investigate: https://support.malwarebytes.com/docs/DOC-2396? Please attach the generated archive in your next reply. Regards,
  19. Hello, Are you using any security software or proxy? There is no issue on the servers, I strongly believe it comes from something that sits in between..
  20. Hello, On top of that, can you: In the start menu, type and look for "Windows PowerShell (Admin)". When the PowerShell prompt opens, type Get-Hotfix and press Enter to get a list of installed updates and their installation dates. Copy-paste the output in your next reply. Regards,
  21. Hello, Can you share a picture of your screen showing exactly the step with the Hightail reinstallation screen? To be sure I understand your first post: are you able to login to your session using SafeMode or not? Thanks,
  22. Hello, Thanks. Can you share the associated scan logfile too? Regards,
  23. Hello, We're looking into it, I will follow up shortly.
×
×
  • 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.