You guys once had this bug within the known issues on the update page. Seems ya'll neglecting us again some more...