CLO Centro de Ayuda
downgrading to CLO 6.0 "solved" the problem, until further notice i am not upgrading