Quick answer: Task Manager only shows a snapshot. To log every new process, enable Audit Process Creation and read Event ID 4688 in the Security log, or use Sysmon. Neither sends alerts. SysPulse sends a Telegram alert, with the full file path and RAM usage, shortly after a new process starts.
Every time you start your PC, Windows launches dozens of processes. Most are safeβsystem services, drivers, and your everyday apps. But occasionally, something new appears that you weren't expecting. A legitimate updater, a background installer, or something more suspicious.
A Windows process monitor that sends a new process alert Telegram message can be the difference between noticing a threat early and discovering it weeks later.
Task Manager's Processes tab hides the detail that matters most for security: the full file path. These methods show it:
tasklist /v lists every process with its user and status.Windows can write a Security log entry (Event ID 4688) each time a process starts. It records the new process name, its parent process, the user, and optionally the command line. It is off by default. To turn it on, run these in an administrator PowerShell window:
Then read the newest events with:
Be aware that this generates a large number of events, and the log only records; it does not notify you. Sysmon (Sysinternals) is a more detailed alternative that logs process creation as Event ID 1, including file hashes, but it needs its own installation and configuration.
svchost.exe runs from C:\Windows\System32. The same name running from a Temp, Downloads or AppData folder is a warning sign.Get-AuthenticodeSignature "C:\path\to\file.exe" shows whether the file is signed and by whom.Get-FileHash "C:\path\to\file.exe" gives a SHA-256 you can look up on VirusTotal.Malware often disguises itself with innocent-looking names like svchost.exe or winupdate.exe. The filename alone doesn't tell you much. But the full file path reveals a lot:
C:\Windows\System32\ β likely legitimateC:\Users\Name\AppData\Local\Temp\ β warrants investigationC:\ProgramData\ β depends on the applicationKnowing when a new process appears, where it's running from, and how much RAM it's using gives you a head start if something is wrong.
Windows keeps a few traces you can check without extra software. Start with these:
Win + R, run shell:recent and look for files you did not open.Event ID 6005 means Windows started, 6006 means it shut down cleanly, and 1074 records a restart or shutdown request. These logs show that the PC was used, not what was done. For that, you need to catch new programs, USB drives and startup changes as they happen, and that is exactly what automatic alerts are for: you find out while you are still away.
Monitoring tells you what started. These built-in options reduce what can start in the first place:
No prevention is perfect, so pair it with detection. A process alert shows you whatever slipped through.
You can check processes manually with Task Manager (Ctrl+Shift+Esc), but that only shows a snapshot. You can't stare at it all day.
Event Viewer logs process starts, but finding that information is slow and confusing for non-admins. Both are useful tools, but they don't offer real-time awareness unless you're actively watching.
Some advanced users write WMI event scripts to capture process creation. While possible, these require ongoing maintenance, don't always survive reboots, and integrating Telegram notifications adds complexity. They're a great learning exercise but rarely a reliable long-term solution for most people.
If you want continuous process monitoring without the hassle, SysPulse offers a practical alternative. It's a compact Windows tool (under 30 MB RAM) that watches for new processes, records their full file paths, and sends a concise Telegram alert shortly after.
Run.bat to launch SysPulse. It runs silently in the background without opening a visible window.You can whitelist known safe applications, set custom thresholds for CPU/RAM, and combine it with USB and startup monitoringβall from a single config file. See the full Configuration Guide for every available option, including the whitelist system.
Antivirus focuses on known malware signatures. A process monitor complements this by alerting you to anything new, whether it's malicious or just unexpected. The combination gives you layered awareness without bloat.
During development, I accidentally ran a bundled installer that quietly added a startup entry and launched a hidden updater. SysPulse caught it before I even finished my coffee. The alert showed the temp folder path, which I immediately recognized as suspicious. Without that notification, the unwanted software might have stayed on my machine for days.
If you only use your PC for basic tasks and never install new software, you might not need it. But if you're a developer, tester, IT admin, or simply security-conscious, a Windows process monitor is one of the simplest layers you can add to your defense.
Two processes can share the exact same file name, like svchost.exe, but a legitimate one usually runs from C:\Windows\System32 while a suspicious one might run from a temp or download folder. The full path is what actually tells you where the process came from.
Open Task Manager (Ctrl+Shift+Esc) and use the Processes and Details tabs, run tasklist /v in Command Prompt, or run Get-Process in PowerShell to include each process's full file path.
Event ID 4688 is a Security log entry written each time a new process is created, provided Audit Process Creation is enabled. It records the process name, parent process and user, and can include the command line.
Windows has no built-in alert for this. You can log process creation with Event ID 4688, but to receive a notification you need a monitor such as SysPulse, which sends a Telegram alert with the process name, full path and RAM usage.
Check the System log for Event IDs 6005, 6006 and 1074 to see unexpected startups and shutdowns, and the Security log for Event ID 4624 to see sign-ins. Also review shell:recent for files you did not open. For live notifications while you are away, a monitor like SysPulse can send Telegram alerts for new processes, USB drives and startup changes.
Open Event Viewer, go to Windows Logs, System, and filter for Event IDs 6005 (startup), 6006 (clean shutdown) and 1074 (restart or shutdown request), or run Get-WinEvent -FilterHashtable @{LogName='System'; Id=6005,6006,1074} -MaxEvents 20 in PowerShell.
Keep Microsoft Defender SmartScreen enabled, use Smart App Control where available, work from a standard user account, and on managed PCs use AppLocker or Windows Defender Application Control. Add a process monitor to be alerted about anything that still starts.
See the full FAQ page for more questions about SysPulse.
Pay with crypto: no card or bank details required, available worldwide. 7-day refund.