Having had a dreadful time working with my ISP sorting out bandwidth issues, specifically the "bursting" showing when using Ookla Speedtest and manifesting itself in awful streaming using YouTube, iPlayer etc. I finally found out the problem was bdtl.dll.
Renaming it bdtl.dl_ in Safe Mode completely resolves the problem in both BD 2012 and BD 2013 on two different versions of Windows (have different versions on Windows 7 and Vista, so no one can say it's an isolated problem). But to my annoyance, Bitdefender decides to fill in the gaps, and puts bdtl.dll back in place, resulting in the problem rearing its ugly head. I have no choice but to rename the file again and again. Have resorted to creating a fake bdtl.dll text file, but I'm pretty sure it will get overwritten.
In short, how can a problem that is so clearly down to one specific module, with such a wide range of problems (I heard it corrupts downloads as well), not be dealt with. Just scrap the module until it works properly rather than obfusicate constantly with such rubbish as "were working on it" or "Microsoft have been informed". It's a Bitdefender problem, and it always has been, for years.
Having moved over from Kaspersky to see what a different product could do for a change, it looks as though I will be installing MSSE or AVG, and dumping Bitdefender. As a computer service provider with lots of customers, I certainly won't be recommending Bitdefender to anyone unless the problem is fixed once and for all!
