It rather involved being on the other side of this airtight hatchway: Changing administrative settings
The blog post discusses the challenge of changing administrative settings when the action requires already having administrative access, likening it to being on the wrong side of an airtight hatchway and needing to unlock the door from the inside.
Background
- Raymond Chen writes *The Old New Thing*, a long-running Microsoft blog that explains Windows internals, historical design decisions, and quirks of software development, often with dry humor.
- This post’s title references a famous sci-fi/hacker trope: an "airtight hatchway" that can only be unlocked from the other side — a metaphor for a catch-22 in system design.
- The actual content of the post (about modifying Windows administrative settings) is minimal here, but the joke is that to change certain protected settings, you already need the very administrative privileges those settings control — a circular dependency that mirrors the "hatchway" paradox.
- The post would typically walk through a registry or Group Policy trick that lets an admin who is already inside the system (i.e., already has some access) change a setting that normally requires higher privileges, effectively "unlocking the door from the inside."
The article discusses why developers should understand the reasoning behind a software rule before attempting to work around it, emphasizing that knowing the rule's purpose can lead to better solutions or reveal hidden risks.
A developer found that a DLL was no longer in memory even though it hadn't been formally unloaded, tracing the issue to Windows' DLL load ordering. When a DLL is loaded at a base address that conflicts with another DLL loaded earlier, the system may relocate it and then later discard the relocated version without clear notification, confusing developers expecting explicit unload.