csrss.exe is a legitimate, protected Windows process when it runs from C:\Windows\System32\csrss.exe and carries a Microsoft signature. Do not end or delete that file. A same-named copy in AppData, Temp, Downloads, or another user-writable folder can be a Trojan or miner impostor; verify the path and signature first. Two or more System32 instances can be normal because Windows runs separate sessions.
A process-library entry describing a Trojan with this name does not identify the file on your PC. Check the actual running file before choosing cleanup or Windows repair.
If a suspicious copy is running from the wrong path, use the fake csrss.exe removal steps below and check what starts the file after reboot. If the genuine System32 process was deleted or a blue screen started after you tried to end it, skip to the Windows recovery steps instead of deleting more system files.
Is csrss.exe safe or a Trojan virus?
- Expected Windows process: the running file is in your Windows installation’s
System32directory, its digital signature validates to Microsoft, and there is no related security alert. Leave it running. Two or more instances alone are not a reason to scan or delete anything. - Access denied or missing details: follow the protected-process check. An unavailable path or signature field is an incomplete check, not a malware detection.
- Unexpected running path or a security alert: record the exact file and alert, then use the scan and cleanup workflow. A file merely stored in a backup or installation folder is different from a process running from that folder.
- Verified system file but sustained high CPU/GPU: use the performance checks. A busy Windows component needs a cause identified; do not end the critical process to test it.

What is csrss.exe?
csrss.exe is the Client Server Run-Time Subsystem, displayed in Task Manager as Client Server Runtime Process. It is a critical Windows subsystem component involved in user sessions and console-related behavior. Its responsibilities have changed across Windows versions. On modern Windows, it works alongside other system components such as conhost.exe, but it remains essential to normal operation. Microsoft documents it as protected starting with Windows 10. [1]
Do not end or delete the real System32 copy. Trying to terminate a critical Windows process can force instability, logoff, or a blue screen. If your concern is high CPU, a security alert, or a duplicate file name, diagnose the cause instead of attacking the protected Windows file.
How to check csrss.exe safely
- Find the running process. Press
Ctrl+Shift+Esc. Look for Client Server Runtime Process under Processes orcsrss.exeunder Details. Record the PID if several entries appear. - Open its file location if available. Right-click that entry and choose Open file location. The usual path is
C:\Windows\System32\csrss.exe. If Windows is installed elsewhere, use that installation’sSystem32directory. Capitalization such asCSRSS.EXEalone does not identify malware;crss.exeorcsrr.exeis a different spelling and needs its own check. - Verify the signature, not just the description. In the file’s Properties, use Digital Signatures if available, select the Microsoft signature, and inspect its details. The publisher or company text on the Details tab is editable file metadata, not a signature-validation result. If the signature tab is absent or unclear, use the PowerShell check below.
- Compare the actual symptom. Note whether an alert identifies this exact path, whether load stays high at idle, and whether it began after an app or driver change. A normal filename, SYSTEM account or quiet CPU reading does not override a specific security-tool alert.
If Task Manager says access denied
CSRSS is a protected process, so some inspection operations can be restricted even for an administrator. Do not take ownership of the system file, disable protection or force termination to get past that restriction. Microsoft Sysinternals Process Explorer can provide process, account, handle and DLL information, but protection can also limit what it shows. Check its current system requirements before downloading it; the current release lists Windows 11 and later for client systems. [1] [3]
You can separately examine the expected file on disk: paste %SystemRoot%\System32 into File Explorer and locate csrss.exe. This does not establish that an inaccessible Task Manager entry is running that same file. If an alert is involved, use the path recorded in the security tool instead; do not substitute the System32 file for the alerted file.
Verify the file with Windows PowerShell
For the expected Windows file, open Windows PowerShell and run the read-only check below. It retrieves Authenticode information and supports Windows catalog signatures. To examine a different file, replace the quoted path with the exact path you recorded; the command does not run that file. [4]
Get-AuthenticodeSignature -LiteralPath "$env:SystemRoot\System32\csrss.exe" |
Format-List Status, StatusMessage, SignerCertificate, Path
Read both the status and signer: Valid plus a Microsoft signer supports the file’s authenticity. NotSigned, a mismatch, an untrusted certificate or a verification error calls for investigation; keep the status message and scan the specific file. A valid signature on disk does not prove the whole PC is uncompromised. If the running path remains unavailable and there are suspicious symptoms, use a full scan or ask your administrator to investigate that PID.
Why csrss.exe can use high CPU or GPU
High CPU from the legitimate Client Server Runtime Process does not automatically mean malware. It can be a symptom of another problem that is pushing Windows session or console handling too hard.
- Console-heavy apps: terminals, scripts, debuggers, or tools that print continuous output can keep console-related components busy.
- Driver or peripheral issues: GPU, printer, webcam, USB, storage, and input drivers can trigger repeated session notifications or UI work.
- Corrupted user profile: a damaged profile can cause recurring session problems that disappear under a new Windows account.
- System file corruption: incomplete updates or damaged files can make Windows components behave unpredictably.
- Malware impersonation: a fake
csrss.exeoutside System32 can mine cryptocurrency, download payloads, or persist through startup tasks.
First confirm that the busy entry is the expected Windows file. Then work through these checks, observing whether the same symptom returns after each change:
- Separate a spike from a persistent load. Save your work, restart once and let sign-in activity settle. In Task Manager, sort by CPU; for a GPU complaint also inspect the GPU and GPU engine columns. Record what remains busy and what action reproduces it. There is no universal percentage that diagnoses a csrss.exe infection.
- Isolate the trigger. Close ordinary apps one at a time, especially a terminal, script, game or capture tool involved when the load starts. If closing one app consistently lowers the load, update or troubleshoot that app. Do not close CSRSS. Disconnect a nonessential peripheral only when its use coincides with the problem.
- Review recent changes. Install pending Windows updates and check the relevant device manufacturer’s driver fixes. If the issue began immediately after a specific driver update, use its supported rollback path when available. Avoid changing every driver at once.
- Test another Windows account if the problem is session-specific. Keep the original profile and files. If the symptom occurs only in one account, investigate that account’s startup apps and settings; do not delete the profile as a first step.
- Repair system files for persistent, broader Windows problems. If several components malfunction or corruption is suspected, open Command Prompt as administrator. Run DISM first; after it completes successfully, run SFC. [5]
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
If SFC repairs files, restart and repeat the activity that caused the load. If it finds no integrity violations, do not keep rerunning it as a CPU fix; return to the app, driver or session trigger. If DISM fails or SFC cannot repair files, retain the exact error and seek Windows repair assistance. If a scan instead identifies an impostor, follow the cleanup branch below.
csrss.exe BSOD: how to recover safely
Forcibly ending a critical process can crash the current Windows session without damaging the file on disk. After a one-time crash, first restart normally. If Windows starts and works, no file replacement is indicated solely by that crash. Use the recovery steps below if Windows will not start, keeps crashing, or the real csrss.exe file was deleted or modified. Do not keep trying to remove it.
- Enter Windows Recovery Environment and try Troubleshoot → Advanced options → Startup Repair. If the device requests a BitLocker recovery key, obtain your own recovery key before proceeding; do not format the drive to bypass the prompt.
- If Startup Repair cannot resolve it, consider a known-good restore point or backup. Advanced users can open Command Prompt for offline SFC, but must identify the actual Windows and boot directories first. Recovery drive letters can differ from those in normal Windows.
The following is an example only for an offline boot directory of C:\ and an offline Windows directory of C:\Windows. Microsoft’s SFC documentation defines these as separate parameters; do not assume both point to C: on your computer. If the layout is unclear, get help identifying it before running the command. [2]
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
After a successful repair, restart Windows. Do not download a replacement csrss.exe from a file-download website. If the crash followed a malware alert, retain that alert and scan after Windows starts; system-file repair does not remove an unrelated malicious startup mechanism.
Why are there two or more csrss.exe processes?
Seeing more than one Client Server Runtime Process is not automatically suspicious. Windows can create separate instances for different sessions. The important checks are still location, signature, owner, and behavior. Multiple instances that all point to C:\Windows\System32\csrss.exe and show normal low usage are usually expected. A duplicate in AppData, Temp, or another user-writable folder is a different story.
What if csrss.exe is in AppData, Temp, or Downloads?
A same-named file in a user-writable folder should be treated as suspicious. Malware often borrows trusted Windows filenames to look harmless in Task Manager. Do not move it into System32, do not mark it as safe, and do not focus only on deleting the visible file. A returning copy usually means a startup entry, scheduled task, script, service, or installer remains active.
Record the full path and any security alert, then scan. You do not need to hunt through registry keys, tasks and services before using the cleanup workflow. For recurring detections, nearby scripts and the command that launches that path become useful evidence.
How to remove a fake csrss.exe virus safely
This branch is for a suspicious running copy or a security-tool alert, not for the normal presence of Client Server Runtime Process. An unexpected path or invalid signature warrants investigation; let the alert details and scan results guide quarantine rather than deleting a Windows-looking file by name.
- Record the exact file and alert. Keep its full path, detection name and time. If an alert names the signed System32 file, keep protection enabled and request the security vendor’s review instead of manually deleting it or adding an exclusion.
- Limit active compromise. If you observe unauthorized remote access or suspicious outbound activity, disconnect the affected PC and stop entering passwords on it. Arrange cleanup from a trusted device or with your IT administrator if needed.
- Run a full scan. Download and install Gridinsoft Anti-Malware from its official site using the link below, update its detection databases, and select Full Scan. Review the reported paths and detections, then apply the appropriate cleanup actions. You may also use your installed security tool’s full scan.
- Restart and check the original symptom. Confirm whether the same wrong-path file or alert returns. A normal Microsoft csrss.exe will still be present in Task Manager; its presence is not a cleanup failure.
- Escalate recurrence with evidence. If the same detection returns, keep the scan report and path. The suspicious startup apps checklist can help an experienced user identify a task, service, script or installer launching that exact file. Manual changes are an optional targeted follow-up, not a prerequisite to scanning; remove an entry only after confirming its role.
- Protect accounts when exposure is plausible. If the incident involved credential theft or an untrusted remote session, change important passwords from a clean device and revoke affected sessions. Removing a file does not revoke stolen credentials.
A security tool may quarantine the visible file while a loader, scheduled task, service or bundled installer remains and recreates it. Gridinsoft Anti-Malware can check the suspicious copy together with startup entries and other persistence points. A clean scan does not guarantee that no compromise occurred, and it does not replace Windows repair if the real System32 file was damaged.
Known impostor behavior
Older malware samples have used the csrss.exe name to disguise coin miners and other payloads. In a historical example previously covered here, a miner dropped files under a Windows-looking folder and used scripts such as Auto.bat, Start.vbs, and Hide.bat to launch and conceal activity. These historical script names are clues from that example, not universal detection rules. The pattern remains useful: a trusted Windows filename appears in the wrong place, launches through scripts or startup entries, and consumes resources or reconnects after reboot.
That is why the safest rule is not “delete every csrss.exe” and not “trust every csrss.exe.” Verify the specific file on the machine: path, signature, parent process, startup source, and behavior.
When should you run a malware scan?
Run a full scan when any of these are true:
- A
csrss.exeprocess is running from an unexpected location outside your Windows installation’sSystem32directory, or a security tool identifies a specific suspicious copy. - The file is unsigned, has an invalid signature, or has a suspicious publisher.
- High CPU/GPU continues at idle after updates and basic repairs.
- The suspicious file returns after you delete or quarantine it.
- You recently opened a cracked installer, game mod, fake update, archive, or email attachment.
- A firewall or antivirus alert ties the process to unknown outbound traffic.
If the scan flags the System32 copy despite a valid Microsoft signature, a false positive is one possibility, but the alert still needs review. Keep protection enabled, record the exact detection and request vendor analysis; do not restore or exclude the file just because its name looks familiar. For a detected user-folder copy, follow the security tool’s quarantine guidance and recheck after restart.
How to avoid csrss.exe impostors
- Download drivers and utilities from official vendor websites, not driver-pack mirrors or “optimizer” bundles.
- Avoid cracked installers, game cheats, and mod packs that request administrator rights.
- Keep Windows, browsers, and GPU/chipset drivers updated.
- Review startup entries after installing unfamiliar software.
- Use a separate standard user account for daily work when possible.
- Back up important files so repair or reset decisions are less risky.
If your concern is a busy Console Window Host rather than Client Server Runtime, use the Conhost.exe high CPU checklist to verify the file path, parent process, and suspicious script behavior without deleting Windows files.
If you are checking Windows shell files, compare this with our sihost.exe safety guide; it uses the same path-and-signature method for deciding whether a process is safe or suspicious. For another protected component, the Wininit.exe safety and restart-event guide explains why the signed System32 process must not be ended or deleted.
FAQ
What is the csrss.exe Trojan virus?
The name can describe malware that impersonates the real Client Server Runtime Process. The protected Microsoft file at C:\Windows\System32\csrss.exe is legitimate; a same-named file in AppData, Temp, Downloads, or another unusual folder can be a Trojan, miner, or loader.
Is csrss.exe safe?
Yes, when it is the Microsoft-signed Windows process in C:\Windows\System32. Do not end or delete that copy. Check the full path, signature, parent process, and startup source before treating any same-named file as malware.
Why are there two csrss.exe processes running?
Two or more instances can be normal because Windows can run a separate Client Server Runtime Process for different sessions. They are usually safe when every instance points to C:\Windows\System32\csrss.exe, carries a valid Microsoft signature, and has normal low resource use.
How do I remove a fake csrss.exe virus?
Record the suspicious path, run an updated full scan, review detections and apply cleanup, then restart and check for the same alert or wrong-path copy. Inspect its startup source only if recurrence needs further investigation. Do not delete the legitimate Windows process.
Can I end csrss.exe in Task Manager?
Do not end the real Client Server Runtime Process. It is critical to Windows sessions, and terminating or deleting it can cause a forced shutdown, instability, or a blue screen.
Why does csrss.exe use high CPU or GPU?
Possible causes include console-heavy apps, driver or peripheral problems, a damaged user profile, system-file corruption, or a fake same-named file. Check the path and signature first, then troubleshoot updates, drivers, DISM followed by SFC when corruption is suspected, and the user profile.
What should I do if a suspicious csrss.exe keeps coming back?
Run an updated full scan and retain its report. If the same wrong-path detection returns after cleanup and restart, investigate what launches it, such as a task, startup entry, service or installer. Use the exact path to guide that investigation instead of deleting every similarly named file.
References
- Microsoft. “Debugging CSRSS.” Windows drivers, updated December 23, 2021, accessed November 8, 2026. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/debugging-csrss
- Microsoft. “sfc.” Windows commands, updated November 1, 2024, accessed November 8, 2026. https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc
- Mark Russinovich. “Process Explorer.” Microsoft Sysinternals, updated November 5, 2026, accessed November 8, 2026. https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer
- Microsoft. “Get-AuthenticodeSignature.” Windows PowerShell documentation, accessed November 8, 2026. Signature status and Windows catalog signing.
- Microsoft. “Use the System File Checker tool to repair missing or corrupted system files.” Microsoft Support, accessed November 8, 2026. DISM and SFC repair order and result messages.

