Skip to main content


Csrss.exe (Client/Server Runtime Subsystem) is a critical Windows Operating System process that manages console windows such as command line interface tools, command line interpreters, and text editors that do not need to display images. Csrss.exe runs in the Windows 2000, Windows XP, Windows 2003, Windows Vista, Windows Server 2008, and Windows 7 operating systems and can be found in the primary hard drive’s C:\Windows\System32 folder.

How Csrss.exe Works

Csrss.exe works bridges the gap between kernel space and user space on the computer. Kernel space refers to an area of the hard drive that is dedicated to running the core system files and maintaining the programming that supports the Windows Operating System. User space refers to an area of the hard drive that is dedicated to applications, programs, tools, and other software on the computer, whether it is system-related or not. By translating information between these two hard drive sectors, Csrss.exe is able to help maintain the Windows Operating System.

Is Csrss.exe Harmful?

Csrss.exe is not harmful, but like any process, malicious software can corrupt or mimic it in order to hide from anti-virus software. If the user suspects that Csrss.exe is a corrupted or malicious file, he/she should run an anti-virus software such as Spyware Terminator, Advanced SystemCare, or Malwarebytes’ Antimalware. The user should also run a registry cleaner, such as CCleaner, in order to check the Windows Registry for errors and fix them. The user should not, however, attempt to remove the file.

How to Remove Csrss.exe

Csrss.exe is a critical Windows process and neither Windows Task Manager nor the popular third party software known as TaskKill can remove it. When the user attempts to remove it, he/she will receive this error message: “This is a critical system process. Task Manager cannot end this process.” However, Csrss.exe can be stopped from running in the Windows Vista Task Manager if it is running in Administrator mode, but doing so causes the Windows Operating System to stop running properly. If the user is experiencing problems with Csrss.exe, such as too much CPU usage, he/she should use the Windows Installation disc to repair the operating system, rather than remove Csrss.exe.

Popular posts from this blog


The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N