Ok, that is three of us who have posted this issue. Either we have accidentally done something to the settings to cause this behavior we see (user error) or there is possibly a manufacturing problem?

In my case, I did try updating to the V3 software and then reverting back. I saw this same behavior in both versions.