6.3 has started this issue all over again, still no fix.