The hidden object-oriented architecture that powers the Windows NT kernel
In short: Most users see Windows as a collection of apps, but beneath the surface lies a rigid, object-oriented hierarchy. Every file, process, and hardware resource is treated as a formal object, managed by a central authority that ensures the system remains stable while allowing diverse software to coexist.
The Windows NT architecture is defined by a strict separation between user mode and kernel mode. While user-mode applications are restricted to specific environments—like the Win32 subsystem—the kernel mode has unrestricted access to the system's memory and hardware. This design allows the operating system to maintain stability; user-mode processes must request the kernel to perform critical operations on their behalf, preventing a single app from crashing the entire machine. At the heart of this system is the Executive, a collection of services including the Memory Manager, I/O Manager, and the Security Reference Monitor. One of the most critical components is the Object Manager. This subsystem acts as a universal resource management infrastructure. To reduce duplication and bugs, nearly every system resource—whether a physical device like a file system or a logical entity like a file—is treated as an 'object.' The Object Manager ensures that all other executive subsystems pass through it to gain access to these resources.
The lifecycle of these objects is strictly governed. Creation happens in two phases: first, the allocation of an empty object and reservation of resources (like a name in the namespace); second, the subsystem fills in the data. Once initialized, the object is inserted into the system and becomes accessible via a 'handle'—an opaque identifier. This handle-based system is a key security and efficiency mechanism: while opening an object by name requires a security check, acting through an existing handle is only limited by the permissions granted at the moment of opening. This architecture effectively turns the operating system into a polymorphic, object-oriented environment.
Opens the Intellect+ feed with this card first. Swipe up for the next one.
Sources
- Summary by Intellect · source: Architecture of Windows NT
To cite this card, link to https://intellectplus.co.uk/app/health-architecture-of-windows-nt.
How we source, check and correct cards: Editorial standards.
General information, not professional advice. Spotted an error? Flag the card or see corrections and complaints.
Intellect Plus is a visual educational discovery platform for exploring fascinating facts and ideas. Brain Food, Not Brain Rot. What is Intellect Plus?
Related
More in Future Frontier · More in Health · Latest · A–Z · All topics
