Weird that it wasn't until 4.67 that it started throwing the error. I was on v4.66 prior.