The warning first appeared in version 5.4.0.2581 (released on Jan. 18, 2010) and is probably still working not correctly up to version 5.4.1.2597 (released today).
We are aware of the problem and are working on a fix. It should become available soon.