If somebody tries to hot-patch an already-hot-patched function, how do they avoid conflicts?
Summary
Raymond Chen discusses how Windows hot-patching is designed to support only one authorized hot-patcher. The article explains what happens if a function is already hot-patched, including how rogue patches can cause a file to become not hot-patchable and may require a reboot. It also outlines a race condition where a patch that is prescan-approved might be interrupted by a subsequent patch, potentially leaving a half-patched binary and complicating rollback.