Why? Because you lose agency. You are no longer deciding to revert; Microsoft is deciding to un-brick you on their timeline. If a patch breaks your obscure RAID controller or your legacy audio interface, you aren't waiting for a new patch. You are waiting for Microsoft to admit the patch was bad and push the KIR.
Your machine isn't broken. It's been patched . And now, you need to perform the ancient, arcane ritual of the revert. revert windows update
Security updates are sacred. You should install them. But the sheer difficulty of removing a cumulative update that breaks printing or networking reveals a design flaw. If a patch breaks your obscure RAID controller
This is the Windows Update Standalone Installer. It bypasses the Settings app’s permission checks. It ignores the "cleanup" flags. It reaches into the WinSxS (Side-by-Side) store and forcibly rips out the component manifest. It's been patched
In practice, System Restore fails silently. You’ll wait 20 minutes, only to see: "System Restore did not complete successfully. Your computer's system files and settings were not changed."