Jump to content

Recommended Posts

  • Staff

Hello,

We silently published a beta build of AdwCleaner 8.1 last night. It has since been downloaded a few hundred times without any issues reported, so we now would like to share it to a broader audience before we move to GA.

The beta version is available to download there, and we plan to release it next week as stable if no issue appears.

AdwCleaner 8.1 brings parallelism in scanning operations, or said differently we rework the scan in order to make it (much much) faster.

Since most of the scanning module are IO-bound (and not CPU-Bound), we now make use of multiple threads depending on what the CPU can offer us so that modules can be run in parallel when possible. This allows to make AdwCleaner's scan even faster than before, even on low-end machines.

Please let us know what you feel and see by testing this beta build!

Edited by jboursier
Link to post
Share on other sites

Yeah it does use a "few more"  threads😀

 

AdwCleaner was pretty fast before, but now zips through

image.thumb.png.a0951496d3dafa05078e756c37954100.png

 

  • Like 1
Link to post
Share on other sites
  • jboursier unpinned this topic
  • 2 weeks later...

I apologise for not reporting this earlier. I suspect that mandatory ASLR is to blame for "NTLayer DLL has stopped working".  Running under Windows 8.1 at least produces an error message box as just below.

AdwCleaner-error.jpg.ef83fdfeff60c373b441bd05fecd7fbe.jpg

AdwCleaner 8.1 runs under Windows 7 with mandatory ASLR without issues.  Running AdwCleaber 8.1 under Windows 10 with mandatory ASLR results in no visible effects, not even a UAC.  I tried exempting the executable in PC settings->Update & Security->Windows Security->App & browser control but apart from seeing a UAC nothing else happens.

I guess that the beta tests were carried out on Windows 10 and Windows 8.1 systems with default ASLR settings.  I like to harden mine by making ASLR mandatory and ensuring that bottom-up ASLR is in use for maximum randomisation.

Edited by hake
Link to post
Share on other sites

Thanks jboursier.  The mandatory ASLR issue with AdwCleaner and Windows 8.1/Windows 10 has been resolved and now works fine.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

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.