King Grub said:
If engine A has definitions for it, it will detect it first. At least that was how it worked when I tested it (version 2011 I believe). Only if engine A didn't catch it was it passed along to engine B (BitDefender).
Thanks I did not even think of that. I thought it was more of a "which engine can get it first" kind of AV, but your reasoning makes more sense.
Moose said:
Re install G Data IS 2013 will take care of Bitdefender update problem! Everything should run smooth after re installing!
No offense Moose, but I don't believe re-installing G Data will solve this issue. Even if it was the issue, I am going about the test as an average user who is just browsing the internet and stumbles upon a malicious site. As an average user, I would have no way of knowing if engine B was malfunctioning or not, because when both engine A and B successively updated in the beginning of my test, it led me to believe both engines were operating properly at the start of testing.