Editing Process identifier (section)

== Microsoft Windows ==
On the [[Windows]] family of operating systems, one can get the current process's ID using the <code>GetCurrentProcessId()</code> function of the [[Windows API]],<ref>{{citation |title=GetCurrentProcessId Function |website=Windows Dev Center |publisher=[[Microsoft]] |url=https://docs.microsoft.com/windows/win32/api/processthreadsapi/nf-processthreadsapi-getcurrentprocessid |date=5 December 2018}}</ref> and ID of other processes using <code>GetProcessId()</code>.<ref>{{citation |title=GetProcessId function |website=Windows Dev Center |publisher=[[Microsoft]] |url=https://docs.microsoft.com/windows/win32/api/processthreadsapi/nf-processthreadsapi-getprocessid |date=5 December 2018}}</ref> Internally, process ID is called a ''client ID'', and is allocated from the same namespace as [[Thread (computer science)|thread]] IDs, so these two never overlap. The [[System Idle Process]] is given process ID 0. The [[Architecture of Windows NT|System Process]] is given the process ID 8 on [[Windows 2000]] and 4 on [[Windows XP]] and [[Windows Server 2003]].<ref>{{citation | title = Microsoft Windows Internals | edition = 4th | chapter = Chapter 2: System Architecture | page = [https://archive.org/details/isbn_9780735619173/page/76 76] | last = Russinovich | first = Mark | author-link = Mark Russinovich | author2 = David A. Solomon | year = 2005 | publisher = Microsoft Press | isbn = 0-7356-1917-4 | url-access = registration | url = https://archive.org/details/isbn_9780735619173/page/76 }}</ref> On the [[Windows NT family]] of operating systems, process and thread identifiers are all multiples of 4, but it is not part of the specification.<ref>{{citation |last=Chen|first=Raymond|title=Why are process and thread IDs multiples of four?|website=The Old New Thing|date=2008-02-28|publisher=[[Microsoft]]|url=https://devblogs.microsoft.com/oldnewthing/?p=23283}}</ref>