I've seen this before I think. Not specifically with this KB but it happened many months ago. The update came through again but installed in seconds. I think it's a minor glitch and you can ignore it...