

Remove-Item -Recurse -Force "C:\Program Files\NortonInstaller" Remove-Item -Recurse -Force "C:\ProgramData\NortonInstaller" Remove-Item -Recurse -Force "C:\ProgramData\Norton" Import-Module $env:SyncroModule -DisableNameChecking On even rarer occasion with some machines I’ve had to download the full size installer and run it as for some reason the stub installer would fail to download what it needed. Occasionally I’ve had to go into c:\programdata\syncro\bin and delete the BD installer and let Syncro redownload/retry installing. AV install is triggered every 2 hours sync. Also keep in mind Syncro’s AV status is not real time by any means, I’m not sure which sync type it’s connected to but it could be 15mins up to 6 hours depending. If there are just a few remnants, I have a script that should take care of them. You may also need to run the removal tool if the uninstall wasn’t fully successful.

After uninstall it’s a good idea to reboot before trying reinstall. Bitdefender is probably detecting remnants of itself. Keywords for google: BEST_uninstallTool.I’ve never needed to disable Defender to get BD to install, nor is that what the message is saying. From there, I removed BitDefender as normal password free on all computers automatically without going into safe mode on each machine one by one. This forced all computers to downgrade to an older version of BitDefender and it actively removed unknown the password. Instead, I took a BitDefender installer package (espkit_圆4.exe), modified the installer.xml file and removed the encrypted password set within the file, and re-deployed the installer without password. I was not going to boot 50 machines into safe mode to remove it one by one. I reached out to BitDefender, who were smug, but said "Nope, safe mode is the only way to do it" even though I had the installer and the encrypted password from within it, they were not prepared to help.īrute force guessing forces the installer to lockout indefinitely after only a handful of attempts, and attempts to decrypt the base64 looking password failed. Switched away to another solution, and it turns out there's an uninstall password on BitDefender that I've never known was set.

I had BitDefender installed on some 50 machines. Hopefully they don't patch this out.Įdit: it now appears to have been patched. I'm writing this as a resource for other people who have this problem and are unhappy with the recommended "boot into safe mode" given by BitDefender.
