Jump to content

jboursier

Staff
  • Posts

    971
  • Joined

  • Last visited

Everything posted by jboursier

  1. Thanks, that's annoying.. This special 8.0.9 one is heavier, and might be able to go further: https://malwarebytes.box.com/s/52bwgo624sh5hten7zbbj01ulxc4rhee If it still doesn't work, we'll have to investigate together or find a way to reproduce the issue on our side.
  2. For confirmation that it's a different issue than the one I was thinking about, may I ask you to try that one: https://malwarebytes.box.com/s/7vvgbuji02beh9ugan7if9sbuyq4wopx ?
  3. Hello, Thanks for using AdwCleaner! Can you try this version instead: https://malwarebytes.box.com/s/y2u4dfk9kb22jzqkx60pmvthu04qe4yn and let me know if it works? Thanks,
  4. Hello, We're starting 2021 with AdwCleaner 8.0.9 that contains a major new feature and various improvements. Starting from this version, AdwCleaner will no longer force you to reboot every time after cleaning your computer. It will only ask you to reboot if and only if one or more elements require a reboot to be properly quarantined. If this case arises, you will have the choice to wait to reboot immediately or not. We also removed the survey dialog at the end to reduce the number of clicks you have to go through. We might reintroduce it from time to time to hear more from you. We really encourage you to use this forum to share your suggestions, difficulties or questions so that we can work together at improving AdwCleaner. We also added the ability to run a Splashtop remote session even during the cleaning process, and we also improved the translations. The next AdwCleaner release will be 8.1, and should see a major scanning speed-up - stay tuned! As usual, the changelog is available below: ## v8.0.9 [11/01/2021] ### New Features * Only ask for a reboot when needed rather than everytime after cleaning. It is now only required to rebo ot when an element cannot be quarantined without rebooting. ### Changes * Remove the survey dialog to reduce the number of clicks. * Update translations * Update definitions to 2021.11.1 ### Bugfixes * Allow Splashtop remote control to keep running while doing the cleanup. AdwCleaner is available for download: https://malwarebytes.com/adwcleaner
  5. Note: If AdwCleaner doesn't start when you try to launch it, please use this specific build instead and reach out to me in DM. There is an ongoing issue with the packer that impacts very very few users and that we are unable to reproduce internally. Using the unpacked version (link above) appears to solve the issue, but we need your help to find the specific root cause, so please DM me if you're in this case and ready to help! 👍
  6. Hello, For those who have been facing the issue, can you try again with this version: https://malwarebytes.box.com/s/dzbqhy5fymjjm3lhnjzzj2xx5a4usp38 ? Thanks,
  7. Thank you for the feedback. If the specific AdwCleaner version I sent was still crashing there it would have helped us to debug as we are unable to reproduce the "crash" internally so far. The good news is that the unpacked version works fine for you, so you have a workaround until we figure out what's going on :) Sorry for the hassle, but you can keep the link above until I come back to you saying the the issue is fixed and that you can resume the use of the regular AdwCleaner. Regards,
  8. @JorgeBon May I ask you to download and try with this version instead: https://malwarebytes.box.com/s/rf2dl7sr1l09x65da5vk4lifya2dhs29 ? We're hoping it will actually crash so we can debug it with your help
  9. We'll get back to you shortly, sorry for the delay.
  10. Hello @ebloch, To be sure I understand correctly, are you talking about the fact that it's not possible to select individual components of Preinstalled Software detections (as opposed to what is possible to do for PUPs)?
  11. Hello @JorgeBon, Can you confirm that you don't have any C:\AdwCleaner folder on your computer? Also, can you share a screenshot of where you see the eventID 26 being triggered? I can't see it in any of the logs, so I would like to be sure it's the event AdwCleaner triggers. Thanks!
  12. Hello, This is fixed, and will ship in the next release (8.0.9). Thanks for the feedback!
  13. Thanks, I wasn't sure so I wanted to confirm. Please follow @exile360's recommendation so that we can support you until resolution.
  14. Hello @LunaVix, Thanks for using AdwCleaner :) Do you confirm that your issue is gone, or is it still unresolved?
  15. Hello, Yes, contrib-adwc is still in use I received your submissions both email and on the portal, I will reply shortly. Sorry for the delay :/
  16. Hello, Thanks for the suggestion! We hope to tackle that in AdwCleaner 9.1.0 at the latest. Regards,
  17. For now we don't support turning the settings on/off from the CLI. It's something we'll introduce in a future release only.
  18. Hello, Sorry for the delay. We just released 8.0.8 a few minutes ago alongside a new definition package: The delay you saw since July was also due to an backend change we've been working on over the past weeks. Things are resuming as usual from now on.
  19. Hello, I'm pleased to share the announcement of AdwCleaner 8.0.8! It contains various stability improvements and fixes over the 8.0.7: More precisely, we realized that some infections are locking AdwCleaner's working directory to prevent it from running so we now try to update the permissions on the working directory (by default C:\AdwCleaner) before using it, and inform you to use another directory from the command-line if we fail to change the attributes. We also improved the detection and cleanup logics, updated the translations and definitions. Another change we introduced is the ability if we run in a corporate environment or not. This change might sound weird for AdwCleaner as it's mainly aimed for individual users. However, a lot of companies are also using it internally. This change is invisible and doesn't break the way you use AdwCleaner, and the goal is not to change AdwCleaner's usage model or vision, but rather to introduce specific features for these users that serve them better while not bothering others who don't need corporate-specific features. We have exciting plans for the coming months for everyone, stay tuned As usual, the changelog is available below: ## v8.0.8 [09/10/2020] ### New Features * Set the correct attributes to the working directory (usually C:\AdwCleaner) to overcome potential malicious modifications * Detect if AdwCleaner runs in a corporate environment ### Changes * Improve Services detection * Update translations * Update definitions to 2020.09.29.1 ### Bugfixes * Fix an issue preventing shortcut cleanup from working correctly * Fix the QSharedMemory error message AdwCleaner is available for download: https://malwarebytes.com/adwcleaner
  20. Great! Let us know if you need anything with regards to the CLI (which is already available).
  21. Hello, Just to keep you posted, we're still investigating this issue. We will post updates when they come though..
  22. It removes the working directory (by default C:\AdwCleaner, but YMMV) only, as AdwCleaner doesn't use anything less than this working directory. The ability to delete logfiles from the UI will come shortly 👍
  23. Hello, @Tarun Sorry for the delay. We're actually working on the process killing and reboot feature to try to avoid forcing a reboot every time, but rather to ask for it only when needed. It should land in the next release (8.0.9, 8.0.8 is already around the corner). Regards,
  24. 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,
  25. 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,
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.