The one "fix" was to change the compile requirement to use non-free tools. But the previous one has languished for three months with no technical fixes. These two problems might have the same solution. The commonality is that code is getting committed without checking to see if it builds correctly in a reference build environment, but that's not a technical issue. This one is about a build problem with paths set up incorrectly. #2599 is actually about ATL versions, because the old version just doesn't work.
This update brings a bunch of features, all of which you were able to try first in our latest development build. We are happy to announce the release of Adblock Plus 1.6 for Internet Explorer. I guess it makes sense to close #2599, if we have this now. Adblock Plus and (a little) more Adblock Plus 1.6 for Internet Explorer released 18:06 by Oleksandr Paraska. In any case this and #2599 are almost identical, and I really don't think we need both. I consider it shoddy testing that this change was even committed in the first place. The most proximate cause is that the path to the ATL headers are not set up correctly in a project that did not previously require them. The only ATL class in the offending code that's not compiling is CComBSTR which is already used extensively in another project. The present issue is not about ATL versions. There is a requirement for a different ATL then the one in the WDK, however. Apparently it does compile in VS Pro, since that's what it was developed with.
All it says is that it doesn't compile in VS Express. The description does not say there is a requirement for it to be installed. There is no requirement for Visual Studio Professional to be installed. It doesn't look like the description is correct.