jboursier

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..

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,

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,

Hello, Thanks. Can you share the associated scan logfile too? Regards,

Hello, We're looking into it, I will follow up shortly.

Can you retry and tell me how it goes now?

Hello, Investigating again, I will follow up shortly.

Hello, May I ask you to try 8.0.0: https://malwarebytes.box.com/s/osfgq8oxa651kw4o3lvx5885cw3svdsz? Please ignore the prompt inviting to update to 8.0.1. Thanks,

Hello, We are pleased to share the new AdwCleaner 8.0.1! In line to the improvements made in AdwCleaner 8, we've been pushing towards improving detection and remediation capabilities, and this time we focused on Mozilla Firefox. We completely rewrote the way we scan and clean Firefox addons, preferences, search engines, start pages, etc.. This allows to reduce the technology debt, to have a more maintainable codebase, and to gain in detection rate and remediation effectiveness. On top of this major change, we fixed a security vulnerability reported by Günter Born. AdwCleaner 7.0 up to 8.0.1 are vulnerable to DLL hijacking. This has now been fixed. We are very grateful for the report, and we encourage everyone to report us any vulnerabilities in AdwCleaner. We will study them and depending on the severity, act accordingly. This is the last release of 2019. We hope to keep our newly found pace in 2020 to improve quality, speed, and detection rate! Detailled changelog: ## v8.0.1 [18/12/2019] ### New Features - Re-Implement Firefox module. It now properly supports detecting and removing extensions, startpage, searchengines, preferences... ### Changes - Hide debug output - Update telemetry internals. - Update definitions to 2019.12.17.1 ### Bugfixes - Fix a DLL Hijacking vulnerability in AdwCleaner 7.0+, reported by Günter Born. To download AdwCleaner 8.0.1, click here. Please share with us your feedback!

Hello, Yes, this preinstalled detection has been shared to the proper team and it should be correctly classified soonish. In the meantime, feel free to add an exclusion for this family: Malwarebytes AdwCleaner Exclusions setting Thanks!

@PurringtonYes, it should work properly since 7.4.2 (you can use the very fresh 8.0 that we just released this morning): https://malwarebytes.com/adwcleaner Regards,

Closing, AdwCleaner 8 has been released:

Thanks, it has been fixed.

Hello, Thanks! Yes, numerous translations need some love. We'll do a new pass for the next release early December (8.0.1) to fix those issues. Feel free to PM me if you have those fixes in the meantime! Thank you,

Thank you all, I really appreciate your reviews and feedbacks! @bscans @Maurice Naggar Re FP - it will be fixed indeed. It looks like Tuesday will be a go 👍

Hello, Thank you for the feedback and sorry for the delay. We published an update, it will be picked up automatically at the next scan and will make this detection disappear. Thank you for the report,

Hello, We are pleased to share the 8th major release of AdwCleaner! This version has been slowly worked on for a year now, and very actively for a few weeks and provides major improvements: We have upgraded our toolchain to a more modern suite in order to benefit from security improvements, various new compiler optimizations and to use new C++ features to get a cleaner and more efficient code. Although this change is mostly invisible, it has been a critical change to support our future work and to greatly reduce the technical debt. We moved to Qt 5.13 branch which is the latest version to date, and which provides major improvements for native integrations We introduced again a working Chrome scan and remediation module that allows AdwCleaner to scan and clean Chrome in a fully comprehensive manner. Related, we temporarily removed the support for Firefox scanning and cleaning and we will introduce a fully new module to provide a much better support in the version 8.0.1 early December. We have been fixing numerous bugs in the remediation and quarantine logic. This part is now much more robust that it was before. Although we have not officially supported Windows Vista or Windows XP for a few years now, we got reports of successful usage by various users on both Windows versions. We know for sure that AdwCleaner 8 and onward will no longer work on these platforms. A support page will be posted with a link to AdwCleaner 7.4.2 which is the last release to run on those versions. There is no changes to the UI or no new features as to speak. Most of the significant changes are happening under the hood, but that doesn't make them less critical and major to provide performances and stability again as we are aware it has been lagging for the past months. We will release the 8.0.1 before the end of the year as we are now finally back on the "one release every 3 to 4 weeks schedule" to include your feedbacks more quickly (more on that shortly) and to overall improve AdwCleaner's quality. This next "dot-version" will include detection improvements (especially for Browsers) and a major review of the translations. The changelog is as below: ## v8 [26/11/2019] ### Changes - Following the release of MB4, the in-app installer now installs Malwarebytes 4. - Always download the very latest Malwarebytes build - Update Qt to 5.13 branch - Upgrade the build toolchain to Visual Studio 2017 - Update OpenSSL - No longer force the generation of the debug logfile - Support again the very latest versions of the Chrome Browser and allow for proper remediation - Temporarily disable Firefox scanning and remediation - will be added back in the upcoming 8.0.1 release - Update translations - Update definitions to 2019.11.20.1 - Completely drop support for Windows XP and Vista. Refer to https://links.malwarebytes.com/support/adwcleaner_windows_compatibility ### Bugfixes - Crash when the UI is displayed in Arabic - Make the uninstallation process more robust and less likely to leave traces behind - Make the quarantine process more stable and less susceptible to corruption To download AdwCleaner 8, click here. Please share with us your feedback!

Hello, We are pleased to share a preview of the 8th major release of AdwCleaner! This version has been slowly worked on for a year now, and very actively for a few weeks and provides major improvements: We have upgraded our toolchain to a more modern suite in order to benefit from security improvements, various new compiler optimizations and to use new C++ features to get a cleaner and more efficient code. Although this change is mostly invisible, it has been a critical change to support our future work and to greatly reduce the technical debt. We moved to Qt 5.13 branch which is the latest version to date, and which provides major improvements for native integrations We introduced again a working Chrome scan and remediation module that allows AdwCleaner to scan and clean Chrome in a fully comprehensive manner. Related, we temporarily removed the support for Firefox scanning and cleaning and we will introduce a fully new module to provide a much better support in the version 8.0.1 early December. We have been fixing numerous bugs in the remediation and quarantine logic. This part is now much more robust that it was before. Although we have not officially supported Windows Vista or Windows XP for a few years now, we got reports of successful usage by various users on both Windows versions. We know for sure that AdwCleaner 8 and onward will no longer work on these platforms. A support page will be posted with a link to AdwCleaner 7.4.2 which is the last release to run on those versions. There is no changes to the UI or no new features as to speak. Most of the significant changes are happening under the hood, but that doesn't make them less critical and major to provide performances and stability again as we are aware it has been lagging for the past months. If everything goes well, we expect to release AdwCleaner 8th next Tuesday, and the 8.0.1 a few weeks later as we are now finally back on the "one release every 3 to 4 weeks schedule" to include your feedbacks more quickly (more on that shortly) and to overall improve AdwCleaner's quality. The expected changelog is as below: ## v8 [26/11/2019] ### Changes - Following the release of MB4, the in-app installer now installs Malwarebytes 4. - Always download the very latest Malwarebytes build - Update Qt to 5.13 branch - Upgrade the build toolchain to Visual Studio 2017 - Update OpenSSL - No longer force the generation of the debug logfile - Support again the very latest versions of the Chrome Browser and allow for proper remediation - Temporarily disable Firefox scanning and remediation - will be added back in the upcoming 8.0.1 release - Update translations - Update definitions to 2019.11.20.1 - Completely drop support for Windows XP and Vista. Refer to https://links.malwarebytes.com/support/adwcleaner_windows_compatibility ### Bugfixes - Crash when the UI is displayed in Arabic - Make the uninstallation process more robust and less likely to leave traces behind - Make the quarantine process more stable and less susceptible to corruption To download AdwCleaner 8 beta, click here. Please share with us your feedback!

Hello, @CW58 Thanks for checking with us! Can you share the output of the command `bcdedit`: Open the Windows start menu, type `cmd.exe` Right click on the `cmd.exe` item that shows up > `Open as administrator` In the black window that opens, type `bcdedit` and press <Enter> Please then share the output. Regards,

Hello, This has been fixed, can you confirm?

Hello, Thank you for the feedback! We'll making the necessary change - it is a naming issue only. Regards,

Great! It's a weird case indeed, thank you for the follow-up!

Hello, Yes, we take a special care at keeping the scan as fast as possible

Hello, This is normal, the number shown as scanned might correspond to one or more elements on your system - it is not a file counter. Regards,

Thank you, we are investigating!