this boomerangs back to firmware updates that should not be happening, microsoft claims they cant find a connection between updates and the damages being discussed.

It would be interesting to see what the state of these corrupted systems were before corruption. were they compromised in some way that makes bork when MS applies an update, or was system configured in a non MS way.

Quite cavalier to the fact the firmware doesnt belong to MS, and updating firmware is not a one update fits all scenario.