Difference between revisions of "WinSecCenter"
(New page: Identifies ''Windows Security Center'' entries. ==Usage== WinSecCenter:<type>,<field>,<data> ===Examples=== WinSecCenter:"av","guid","{3207EF9A-E64B-40A0-B897-3F2B9D794816}" Detects a...) |
(added info box) |
||
| Line 1: | Line 1: | ||
| − | Identifies ''Windows Security Center'' entries. | + | {{SbiCmdInfo |
| + | |SYNTAX = WinSecCenter | ||
| + | |PENAME = SpybotSD.exe | ||
| + | |PEVERSION = 1.3 or later | ||
| + | |GROUP = Windows API | ||
| + | |MINUPDATE = 2008-03-05 | ||
| + | |ADVFILEPARAMS = no | ||
| + | |ADVREGPARAMS = no | ||
| + | |ADVBUILDPARAMS = no | ||
| + | |ADVSPECIALPARAMS = no | ||
| + | }}Identifies ''Windows Security Center'' entries. | ||
==Usage== | ==Usage== | ||
| − | WinSecCenter:<type>,<field>,<data> | + | WinSecCenter:<type(enum)>,<field(enum)>,<data(string)> |
===Examples=== | ===Examples=== | ||
Revision as of 14:21, 22 February 2008
| WinSecCenter | |
| Group | Windows API |
| Main Application | Version 1.3 or later |
| Required Update | 2008-03-05 |
| File Parameters | no |
| Registry Parameters | no |
| Build Parameters | no |
| Special Parameters | no |
Identifies Windows Security Center entries.
Usage
WinSecCenter:<type(enum)>,<field(enum)>,<data(string)>
Examples
WinSecCenter:"av","guid","{3207EF9A-E64B-40A0-B897-3F2B9D794816}"
Detects and removes an antivirus application that has the specified GUID.
Description
Anti virus entries are supported by WSC starting with XP, anti spyware entries starting with Vista.
- The first parameter defines the type of application to detect. The two types currently supported are
- av (anti virus application)
- as (anti sypware application)
- The second parameter specifies the field to look up, which only has only possible value, guid, as of now.
- The third parameter contains the data to detect, which since only GUIDs are supported right now, needs to be one such. This is a strict matching, no Algo-Prefix yet.
Scan Results
- Only a status report, the plugin structure currently doesn't allow a custom fixing type, so the entry will be removed immediately during the scan.
