An investigation by Ed Bott casts doubt on KB3xxxx being the problem, and points instead to an Office update that affected Office