Apparently an update has resolved this issue. Thanks.