Has anyone with this issue been able to test 1.0.72 yet? I didn't see specific mention of this issue in the changelog, but I could have missed something. Unfortunately I won't be home to test any time soon.