How to obtain a list of tasks that trigger the automatic opening or closing of cmd windows?
How to obtain a list of tasks that trigger the automatic opening or closing of cmd windows?
Hello
In Windows 11 Home (and even 10)
Occasionally a cmd window appears automatically
to perform a task, usually an update, and it closes on its own in about 2/3 seconds. It’s a brief occurrence.
Question
How can I get a list of tasks that are opened or closed automatically via cmd windows?
Thank You
This CMD window is displaying a message indicating it's running an unspecified task. If it doesn't match any known command, it raises concern.
I believe you're referring to any executable files that display in the console after logging in. It seems there isn't a comprehensive list of executed programs. If the console windows appear after an update, they are likely related to the update. If they show up unexpectedly, these could indicate issues. The only straightforward methods I'm aware of are:
1. Review startup files using tools such as Microsoft internals' Autoruns.
2. Examine the Run Start/Run End/Triggers time in Windows Scheduler via "Task Scheduler (Local) > Task Status/Active Tasks."
If you can't identify the source and suspect something is wrong, BleepingComputer's malware removal help forum might assist in detecting unusual tasks.
I see what you're aiming to achieve. Confirming the need to track every time an *.exe file is initiated—whether through Task Manager, Startup settings, or Task Scheduler, or even when it starts via the Command Window. The goal is to identify any application launching with that extension, especially if it comes from the Command Prompt. You can check the Reliability History/Monitor and Event Viewer for error messages, warnings, and logs related to process launches. The Event Viewer supports custom filters, though flagging tasks launched directly via cmd may require some experimentation. It seems a PowerShell script with administrative privileges could be useful, possibly running in the background at startup to monitor cmd.exe and capture relevant entries. Alternatively, using the Get-EventLog cmdlet to search for "*.exe" in the Event Viewer logs might help. Also, you might need to employ Get-Process to detect when cmd.exe is executed. The Windows Update History file could be another useful resource.