Ok great. It looks as though some how your Scan Properties got changed. You mentioned in your email you don't think anyone there changed it, so on the very next build we'll add a sanity check on startup just in case, until we can nail this down. Thankfully this is a minor issue that shouldn't show up for most users.
If anyone has this exact issue, please let us know here.