bug in the new update.    disable the service in services.msc, and set recovery options to 'take no action' for now, until they fix this horrendous bug  See my post for how i killed the service altogether