Stucks “deleting”

I found the error after trying many different ways: when I reactivate the plugin and went to reset, it tells me can’t access .htaaccess archive that should be inside “wp-includes” folder, but there was not any file with this name there!
i had to create a blank one to put there and, so, I could remove it.
Not easy, not funny, removed and intend to never install it again.

• This reply was modified 3 years, 10 months ago by Geovane Souza.

Hey there @geovanesou, thank you for taking the time to rate Defender.

I’m really sorry that you experienced this issue and was wondering if you would be willing to give it a try again, I mentioned this because in some cases there could be permission issues which might cause Defender to fail or in this case, say that it couldn’t find that file.

Once you install it again, feel free to start a support topic here so one of my colleagues can take a look if you experience the same issue.

Thanks in advance!

Regards,

Jorge

Hello @geovanesou

I trust you’re doing well!

We really appreciate your feedback! Please let us know for how long the Malware Scanning was stuck? For sites large in size, it may seem that the scanning has stuck, although it needs more time to scan all files. The speed depends on the PHP memory available on your server.

About Setting Reset, Defender places an .htaccess file inside the wp-include directory, and it will only harden the security of your site, to prevent PHP Execution. It is one of the Security Tweaks that can be enabled inside the Defender’s settings. If the error message was about that .htaccess file, most likely your hosting (or another plugin) has changed files and folder permissions, to prevent any plugin from accessing it, therefore it could not be deleted. We have tested Reset Settings on our end and we couldn’t replicate this issue.

Some hosting providers hide an .htaccess file and it is not visible, so this would explain why it couldn’t be detected

To clarify what is the exact issue, we would really like to assist you with this issue to resolve it, please open a support thread with us, per Jorge suggestion. We are always happy to assist!

Kind regards,
Nastia