Any other people using SCCM and experiencing this problem? 

Support Tip: ConfigMgr 2012 update scan fails and causes incorrect compliance status