I have also had this problem but the v1.5.1.16 update does indeed resolve the issue. My only point would be that v1.5.1.15 is still being offered for download and no mention is made of the problem (or resolution) unless you go digging through the forum.
Regards