Recurring pop-up BitFefender Threat Scanner errors

Just confirming that the solution works.

I have another problem that appears to be related to unchecking the option to install the Windows Security Centre integration when doing this installation, but I'll raise that elsewhere - just a warning to not do that.
 
Same problem, Spybot Portable

I use Spybot Portable on a datakey, downloaded (and kept current) from the PortableApps repository. Scanned my computer last week with no problems: today the BitDefender recurring pop-up appeared...

Obviously, I've removed the portable instance, and on restart the problem's gone.

Do we have any idea when Spybot Portable will be safe to use again?
 
Do we have any idea when Spybot Portable will be safe to use again?
I don't know. I would presume that the bitdefender reoccurring popup will be fixed in some later version of Spybot, so then the error will be gone after the later version of Spybot is updated as a portable app by the portableapps person/people. But that's rather a lot of presuming on my part, so it might be best to ask Spybot support:
https://www.safer-networking.org/support/ticket/

And/or, if you are able to do a custom installation with portableapps, then there is a workaround posted here:
https://forums.spybot.info/showthre...17060480000256&p=476629&viewfull=1#post476629
 
yup, i get this as well after installing the latest version of spybot on windows 7 (a fresh reinstall), as well as the 4 unprotected host files.
 
There's a workaround listed here that Marcel6969 got from support, if you are using the free edition of Spybot (the home and pro versions would need the files necessary for antivirus scanning):
https://forums.spybot.info/showthre...17060480000256&p=476629&viewfull=1#post476629

So, you did a clean reinstall of Windows 7, where you have to re-add your programs again? You installed the latest version of Spybot, have you installed other programs as well? Did you install an antivirus and/or a firewall? If so, I have two posts from others on here about the 4 unprotected in the hosts file that you can look at, and see if they are applicable to you. :)
 
There's a workaround listed here that Marcel6969 got from support, if you are using the free edition of Spybot (the home and pro versions would need the files necessary for antivirus scanning):
https://forums.spybot.info/showthre...17060480000256&p=476629&viewfull=1#post476629

So, you did a clean reinstall of Windows 7, where you have to re-add your programs again? You installed the latest version of Spybot, have you installed other programs as well? Did you install an antivirus and/or a firewall? If so, I have two posts from others on here about the 4 unprotected in the hosts file that you can look at, and see if they are applicable to you. :)

from the above link i did a reinstall of spyboy and that solved the bitdefender issue (why is the free version installing stuff the free version doesnt come with, they need to fix that).

but anyways

did a full reinstall of windows 7
downloaded the chrome browser
installed spybot, and avast
installed steam and gog galaxy
and this is where i am right now.

the exact same 4 items just will not immunize as with the old install of windows 7, and i started noticing it happening since august of 2017 (who knows when it actually started happening).
 
Last edited:
I'm glad the bit defender workaround worked. :)

Sueska has a post here about the Spybot Hosts File entries and Avast, as well as a post from BobxT that might be helpful:
https://forums.spybot.info/showthre...y-Immunization&p=478688&viewfull=1#post478688
There's no workaround posted there for re-immunizing and having it "stick" other than uninstalling Avast. By linking to that I'm not suggesting that you uninstall Avast or anything like that, I'm just linking to it so that you can get an idea about what is going on with the four unimmunized entries and why it is happening. The four sites that are allegedly removed from the host file entries by Avast are listed there by BobxT. Note that Sueska says in their last post that Web of Trust has negative reviews of the sites and that they checked Whois and cannot validate that these websites are associated with Avast:
https://forums.spybot.info/showthre...y-Immunization&p=478734&viewfull=1#post478734
(As an aside, I thought that was a really great and well worded post.) :)

Sorry there's no workaround for that one that I know of, but at least you have some idea of what might be going on.
 
I'm glad the bit defender workaround worked. :)

Sueska has a post here about the Spybot Hosts File entries and Avast, as well as a post from BobxT that might be helpful:
https://forums.spybot.info/showthre...y-Immunization&p=478688&viewfull=1#post478688
There's no workaround posted there for re-immunizing and having it "stick" other than uninstalling Avast. By linking to that I'm not suggesting that you uninstall Avast or anything like that, I'm just linking to it so that you can get an idea about what is going on with the four unimmunized entries and why it is happening. The four sites that are allegedly removed from the host file entries by Avast are listed there by BobxT. Note that Sueska says in their last post that Web of Trust has negative reviews of the sites and that they checked Whois and cannot validate that these websites are associated with Avast:
https://forums.spybot.info/showthre...y-Immunization&p=478734&viewfull=1#post478734
(As an aside, I thought that was a really great and well worded post.) :)

Sorry there's no workaround for that one that I know of, but at least you have some idea of what might be going on.

seems like the devs at spybot need to get into contact with the people at avast to find out whats what and find a solution. if those urls are indeed malicious and avast is blocking the changes then the people at avast need made aware of it, if the URLs are indeed avast URLs then something needs done on spybots side to keep it from immunizing against them. those two are the only logical outcomes i can see.
 
It's possible they might have contacted Avast already if Avast is removing the hosts file entries, though I don't know if that happened or not. Traveler11 also had four unimmunized hosts file entries, and they found it was due to Zone Alarm, so perhaps the reasons for the 4 unimmunized hosts file entries varies. I don't know for sure if Team Spybot saw Sueska's post or not, or if it is a plausible scenario. But you could tell them about it if you would like to be sure they know, and thank you for doing so if you do. :)

I'm not exactly sure which form to use in this case, it seems sort of a grey area.
https://www.safer-networking.org/support/ticket/
I think perhaps feedback would be best.
 
bitdefender error

one year later and the issue is still not handled by spybot? SB knows it's an issue and for an amateur like myself it's frustrating. would I recommend SB -NO! I'll pay for a service. (btw, posting a work around is NOT fixing the issue!)
 
Still no fix or update for Reocurring pop-up BitDefender Threat Scanner issue

one year later and the issue is still not handled by spybot? SB knows it's an issue and for an amateur like myself it's frustrating. would I recommend SB -NO! I'll pay for a service. (btw, posting a work around is NOT fixing the issue!)

I'm very disappointed in Spybot not addressing this issue considering it is 1 year on. I have just discovered 2.7 beta so maybe this has addressed this? I shall see.
Safer networking should be fixing these issues far quicker if they are to stay on top of people wanting to use their software.
 
Back
Top