The MSE console tool MpCmdRun.exe‘s command-line help displays the parameters and flags to be used to initiate a scan. Here is the line that I’m talking about.
-Scan [-ScanType] Scans for malicious software
And the ScanType can be 1 (Quick scan) or 2 (for Full scan)
Anyone who reads the help text would think that the following command-line is to be used for running a scan:
(or)
But that’s not the syntax Microsoft Security Essentials expects. If you had used the above commands, the Microsoft Security Essentials always initiates the default scan type chosen in the Settings page of the Microsoft Security Essentials utility. That is, it defaults to Quick Scan (which is the default setting) regardless of the flag used. You can verify that using the Event Viewer. For every scan initiated, there is an event log entry generated.

Correct Syntax for Command-Line Scan
Here is the correct syntax (via Microsoft Answers forums) for running a command-line scan:
[Quick Scan]
[Full Scan]
Editor’s Note: In case you’re wondering what a "Quick Scan" does…. The "Quick Scan" option scan the areas of your computer that malicious software is most likely to infect. Whereas the "Full Scan" checks the entire hard drive and even scans the files inside ZIP and CAB archives by default.
Related Posts
- How to Disable Updating of Definitions When Running a Command-Line Scan Using MpCmdRun.Exe
- Updating Microsoft Security Essentials Using Command-Line
- Scan USB Drives Using Microsoft Security Essentials via the AutoPlay Dialog
- How to Run the System File Checker (Sfc.exe) Offline in Windows 7 and Vista
- How to Remove Scan Using Spybot-Search&Destroy Option From the Right-Click Menu
If you enjoyed this post, make sure you subscribe to our RSS feed! We feature Tips, Troubleshooting information, Scripts and Utilities for Microsoft Windows Operating Systems!
Prefer an E-mail subscription?





“For some reason -scan -scantype 1 always does a signature update. I’m missing something.”
Same problem here, a signature update is all I cab get it to do from the command line.
@Zane: See http://www.winhelponline.com/blog/disable-update-definitions-running-command-line-scan-mpcmdrun/
For some reason -scan -scantype 1 always does a signature update. I’m missing something.