I might be beating a dead horse, but is there a work-around for a system that already has KB4056892 installed?

Thanks!
--Dave