Difference between revisions of "WinSecCenter"

From SpybotWiki
Jump to: navigation, search
(added info box)
m (added adv build param for >= 1.5.3)
 
Line 7: Line 7:
 
|ADVFILEPARAMS = no
 
|ADVFILEPARAMS = no
 
|ADVREGPARAMS = no
 
|ADVREGPARAMS = no
|ADVBUILDPARAMS = no
+
|ADVBUILDPARAMS = yes (fourth) ≥ 1.5.3
 
|ADVSPECIALPARAMS = no
 
|ADVSPECIALPARAMS = no
 
}}Identifies ''Windows Security Center'' entries.
 
}}Identifies ''Windows Security Center'' entries.
  
 
==Usage==
 
==Usage==
  WinSecCenter:<type(enum)>,<field(enum)>,<data(string)>
+
  WinSecCenter:<type(enum)>,<field(enum)>,<data(string)>[,advanced build parameters]
  
 
===Examples===
 
===Examples===

Latest revision as of 16:53, 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 yes (fourth) ≥ 1.5.3
Special Parameters no

Identifies Windows Security Center entries.

Usage

WinSecCenter:<type(enum)>,<field(enum)>,<data(string)>[,advanced build parameters]

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.

  1. The first parameter defines the type of application to detect. The two types currently supported are
    • av (anti virus application)
    • as (anti sypware application)
  2. The second parameter specifies the field to look up, which only has only possible value, guid, as of now.
  3. 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.

See also

Similar commands