When you take the time to look at all the little details in Windows, you often find little curiosities. Like why, for example, are Process Identification Numbers 1, 2, and 3 never assigned to anything in the Windows Task Manager?

今天的问答环节是由SuperUser提供的，SuperUser是Stack Exchange的一个分支，是一个由社区驱动的问答网站分组。

问题

超级用户读者Agovizer仔细查看了Windows任务管理器中的表进程显示表，并提出了一些问题，特别是：

What processes, if any, exist between PIDs 0 and 4 on Windows 7? Just out of curiosity what are the processes between 0 and 4, and also between 4 and 200 something.

我们跳到机器上的任务管理器中，确信在插槽1、2和3中没有分配任何进程—尽管我们的PID从4跳到了340，而他的PID从4跳到了200。

答案

超级用户贡献者G Koe一举结案：

There is no Process ID 1, 2, or 3 because of how the NT kernel handle table works.

Handles are always multiples of four. The Kernel handle process object is used for both process handles and process/thread IDs. It happens that handle values all start at 0x4 (bit 2), and the InitialSystemProcess is the first process to be created, so it gets a PID of 4. Idle process isn’t actually a process and you can’t open it. It probably doesn’t have a real PID but most tools c***ider it to be 0.

More on the NT handle table here although this is only accurate for NT3-5(xp) , as Windows 7 now requires that you only reference kernel handles if attached to PsInitialSystemProcess.

More on Windows 7/8 Handle limits from Mark Russinovich

More on the “multiples of four” in PIDs

他所建议的一切都得到了验证：我们缺少1、2和3（不是4的倍数），从340到13136的每个PID值都可以被4整除。

有什么要补充的解释吗？在评论中发出声音。想从其他精通技术的Stack Exchange用户那里了解更多答案吗？在这里查看完整的讨论主题。