It may have been fixed with my 4th refresh. Odd.