API-MS-Win-Service-winsvc-L1-1-0

All functions in the API-MS-Win-Service-winsvc-L1-1-0 set are exports from ADVAPI32:

• ChangeServiceConfigA
• ChangeServiceConfig2A
• ControlService
• ControlServiceExA
• CreateServiceA
• I_QueryTagInformation
• I_ScBroadcastServiceControlMessage
• I_ScIsSecurityProcess
• I_ScPnPGetServiceName
• I_ScQueryServiceConfig
• I_ScRpcBindA
• I_ScRpcBindW
• I_ScSendPnPMessage
• I_ScSendTSMessage
• I_ScValidatePnPService
• NotifyServiceStatusChangeA
• OpenSCManagerA
• OpenServiceA
• QueryServiceConfigA
• QueryServiceConfig2A
• QueryServiceStatus
• RegisterServiceCtrlHandlerA
• RegisterServiceCtrlHandlerW
• RegisterServiceCtrlHandlerExA
• StartServiceA
• StartServiceCtrlDispatcherA

For most of these functions, the implementations in ADVAPI32 version 6.1 and higher are just stubs which transfer the handling to wherever the schema redirects the API Set. The exceptions are:

• I_QueryTagInformation
• I_ScBroadcastServiceControlMessage
• I_ScIsSecurityProcess
• I_ScPnPGetServiceName
• I_ScQueryServiceConfig
• I_ScRpcBindA
• I_ScRpcBindW
• I_ScSendPnPMessage
• I_ScSendTSMessage
• I_ScValidatePnPService

which have no code in ADVAPI32 but are instead exported as forwards to the API Set.

New Locations

Non-trivial implementations of all functions in this API Set are exported from SECHOST version 6.1 and higher.

Schema Redirection

The Windows 7 schema redirects this API Set to SECHOST. Thus:

• high-level executables, which do not use the API Set, continue to import these functions from ADVAPI32;
• low-level executables have their imports from the API Set redirected to SECHOST;
• as a particular case of the preceding, the stub implementations in and forwards from ADVAPI32 import from underlying implementations in SECHOST.