@Orlando are you seeing any reports of things like this happening? Where do they go from here if repair updates is creating this scenario?
