This is a known bug in V3a7.

To correct the problem for sure, you must use software version 2.0 final. No word yet on whether this has changed in V3a9, since that only just came out a couple of hours ago.