Floydd

Exactly, I purchased ESET Nod 32 Antivirus because of this problem. Now they said an 'update' or 'fix has been issued and this problem is now 'resolved' So me standing by BitDefender, I re-installed BitDefender (even after purchasing another antivirus) and did the update and I thought 'well at least it is fixed' and it…

I read 16 pages of complaints about services not responding and the alleged "fix". I have uninstalled all other anti spyware software. This is really frustrating because we purchase 10 user licenses and between the non responding, the cpu hogging, and generally slow internet and computer speed in general, bit defender has…

It "was " even Longer , in the 2009 Version too !, So after 2 Versions finally the fix but will first have to see it before believing it Yep, kind of a joke..way too long to be fixed. Is it fixed for you? Anyone else??

Just as I switch Antivirus's after waiting so long..finally a 'fix'. Will wait for more posts to confirm this is solved. Any explanation 'DanyDan' what caused this problem? And 'Desertrider" 10 months is a very long time to a fix a critical problem..(that's if it is indeed fixed) don't you think?

I really like BitDefender but I've had to move AV's.. :/ there's just no fix for this and the developers don't seem to care. Ah well..

Hmm, what's everyone's BitDefender Antivirus 2010 Build?? Just realised the two working Bitdefender Antivirus 2010 that don't get this error have a Build of 13.0.21.347 and the Bitdefender Antivirus that receives this error has a build of 13.0.17.343. I could be onto something here.. Will try and update the Build and see…

That's not a bad idea JeffW, old Anti-Virus entries could be causing problems but it really seems like trail and error. I have three PC's running BitDefender 2010 Anti-Virus. Two with Windows XP Professional and one with Windows 7. The one with Windows 7 never ever has this issue and one of the PC's with Windows XP Pro…