beginner

Registry & configuration

How Windows stores system and application configuration in hierarchical hives.

Official Microsoft docs

Closest official references related to this topic on Microsoft Learn.

Why it matters

The registry is the configuration backbone of Windows. Boot settings, service definitions, driver parameters, and countless application settings live there.

Mental model

Think of the registry as a structured configuration database split into hives, keys, and values rather than a flat text file.

Windows building blocks

Names and paths you can look for in Task Manager, Explorer, or documentation.

  • FileSYSTEM, SOFTWARE, SAM, SECURITY

    %SystemRoot%\System32\config

    On-disk hive files

Go one level deeper

Extra detail for readers who want more precision before opening a child topic.

  • HKLM\SYSTEM\CurrentControlSet holds services, Control sets, and driver config.
  • Transaction logs (.LOG) protect hive consistency across crashes during writes.

How it works

  1. 1Hives back the persistent storage of configuration data.
  2. 2Keys organize data hierarchically and values hold typed content.
  3. 3Kernel and user-mode components read from and write to these structures through registry APIs.

Key terms

Hive
A top-level registry data store backed by files and memory structures.
Key
A container node in the registry hierarchy.
Value
A named piece of typed data stored under a key.

Where service startup definitions live

The Service Control Manager reads service configuration from registry locations rather than from a separate service-only database.

Common misconception

The registry is not one giant in-memory blob. It is segmented into hives with their own load and persistence behavior.

Go deeper

You should read next

Ranked from your current topic, related links, branch depth, and any active guided path.

Related topics