I/O system
How Windows turns API requests into IRPs, driver stack work, and device operations.
Guided paths in this branch
Follow a short sequence step by step. Each path links to the first topic; use Read next on each page to continue.
I/O & drivers
From I/O Manager and IRPs through driver stacks and PnP power.
Step 1 of 5 in this path
Follow this pathOfficial Microsoft docs
Closest official references related to this topic on Microsoft Learn.
Why it matters
The I/O system is where user intent meets devices and drivers. If you want to understand files, disks, keyboards, or networking, you eventually need the I/O pipeline.
Mental model
Windows I/O is a routed request system: an application asks for work, the I/O manager packages that request, and layered drivers cooperate to complete it.
Windows building blocks
Names and paths you can look for in Task Manager, Explorer, or documentation.
- ComponentI/O Manager
IRP routing and completion
Go one level deeper
Extra detail for readers who want more precision before opening a child topic.
- IRPs can be completed synchronously, pending with a callback, or forwarded down the stack.
- I/O completion ports scale thread pools for high-concurrency servers.
How it works
- 1A user-mode API call crosses into the kernel and becomes an I/O request packet (IRP).
- 2The I/O manager sends the IRP through one or more device stacks.
- 3Drivers either handle, transform, forward, or complete the request depending on their role.
Key terms
- IRP
- I/O Request Packet; the main kernel structure representing an I/O operation.
- Driver stack
- The ordered set of drivers that cooperate to handle a device request.
- Device object
- The kernel object representing a device instance inside the I/O system.
Opening a file from an app
A simple file open looks like one API call from user mode, but Windows turns it into an I/O request that traverses several layers before the file system or device responds.
Common misconception
A driver is not always the final owner of a request. Many requests pass through several drivers before completion.
Go deeper
You should read next
Ranked from your current topic, related links, branch depth, and any active guided path.
intermediate
I/O Manager
The kernel component that builds, routes, and completes I/O requests.
Next step in your guided path
intermediate
Drivers & device stacks
Function, filter, bus, class, and miniport drivers in layered request handling.
Go deeper in this branch
expert
Plug and Play & power
How devices appear, initialize, and change power state without manual kernel bookkeeping.
Go deeper in this branch
Related topics
Storage & file systems
Disks, volumes, cache, and the file-system layers that make persistence usable.
Services & background infrastructure
How Windows launches, groups, isolates, and supervises long-running background components.
ETW tracing
Real-time sessions, controllers, and consumers for higher-volume tracing.