Content deleted Content added
CSRSS does not run on top of unix. implying that terminating CSRSS would cause a kernel panic on unix based devices is not correct. |
m Dating maintenance tags: {{Update}} |
||
Line 1:
{{update|reason=csrss.exe is still active in Windows 10 (or beyond) in 2023, with no content below explaining its role or consequences of terminating it|date=September 2023}}
'''Client Server Runtime Subsystem''', or <code>csrss.exe</code>, is a component of the [[Windows NT]] family of [[operating system]]s that provides the [[User space|user mode]] side of the [[Windows API|Win32 subsystem]] and is included in [[Windows NT 3.1]] and later.<ref name="GDI" /> Because most of the Win32 subsystem operations have been moved to [[kernel mode]] [[Device driver|drivers]] in [[Windows NT 4]] and later, CSRSS is mainly responsible for [[Win32 console]] handling and GUI shutdown. It is critical to system operation; therefore, terminating this [[Process (computing)|process]] will result in system failure. Under normal circumstances, CSRSS cannot be terminated with the ''[[kill (command)#Microsoft_Windows_and_ReactOS|taskkill]]'' command or with [[Windows Task Manager]], although it is possible in [[Windows Vista]] if the Task Manager is run in Administrator mode. On [[Windows 7]] and later, Task Manager will inform the user that terminating the process may result in system failure, and prompt if they want to continue. In Windows NT 4.0 however, terminating CSRSS without the [[Session Manager Subsystem]] (SMSS) watching will not crash the system.<ref>{{YouTube|id=h1dBNTkL75A|t=0m31s|title=Winlogon.exe pt.II}}</ref> However, in [[Windows XP]], terminating CSRSS without SMSS watching will crash the system due to the critical bit being set in RAM for csrss.exe.
| |||