Anyone else experiencing issues with a/v Defender showing in an error state?

Getting this error - The maximum number of attempts to install has been reached. Install has been attempted 3 times. Please refer to KBA91002 for troubleshooting procedures.

Have been told by SolarWinds to try this tool - Uninstall_Tool_6.6.11.164.zip

Then run cmd prompt as admin to execute the tool with these parameters -

UninstallTool.exe /bdparams /bruteForce /unSafe /noWait

Clean registry keys - keys and delete them if they exist:

HKEY_LOCAL_MACHINE\SOFTWARE\N-Able Technologies\AVDefender
HKEY_LOCAL_MACHINE\SOFTWARE\AVDefender
HKEY_LOCAL_MACHINE\SOFTWARE\BitDefender

Then re-install a/v

9 Spice ups

Are there no other error logs ?

I would not use this sub-par AV where even details like these are written in registry…so one of the way to disable the AV is to modify a few registry settings ??

1 Spice up

A few things I would suggest. Are you deploying this from N-Central? Looks like it seeing those registry keys. I would first uncheck the box that says basically “install AVdefender” under the security manager tab, then save to stop that old install.

Next, check that the admin credentials you have entered are correct for that agent/computer… make sure you are including the DOMAIN\ qualifier before the username if on a domain and make sure that user has sufficient rights. I would expect to be an admin with this type of low level install.

Once you’re sure the creds are in there and saved, check to make sure that you can access the ADMIN$ share on the machine you’re trying to install to. If you don’t know you can try \ipaddress\ADMIN$ or \computername\ADMIN$ (obviously replace those with the real info) and see if you can access the hidden ADMIN$ share on that machine with the creds you supplied earlier from another machine on the LAN.

Also, make sure the computer’s firewall is off or configured to accept incoming connections. I’d just temporarily cut it off while troubleshooting. Windows File and Printer Sharing will be important to allow in.

Next, try and clear your temp folders:

c:\windows\temp and wherever %temp% points to.

Finally, another common cause of this is another anti-virus or anti-malware program still installed on the machine. AVDefender’s antivirus cleanup (option on the install screen) is usually pretty good, but it doesn’t always take care of everything. Sometimes manual intervention is required. Make sure you look through your installed programs and see if there are any in there… anything remotely along the lines of an antivirus/anti spyware or security program and it will bomb out.

Make sure you reboot (do I really need to say this?) and then try deploying it again.

I’m betting it’s the machine’s firewall blocking it, another antivirus program or wrong credentials supplied. Those have been the main 3 every time I’ve had a failed deployment.

I do these deployments all the time so let me know if you have any other questions.

1 Spice up

Hi All, thanks for the feedback. Per SolarWinds, this is a known bug that they are working to address.