I did not get this error until I updated to 1.175. I am thinking about going back to 1.170 and see if it gose away. Anyone think this is a good idea or not?