Credential Provider Usage Scenario: CPUS_UNLOCK_WORKSTATION Removed from Windows 10

Question

I am developing my own credential provider and should know it at runtime if the script is a login or session unlock. To do this, I check the CREDENTIAL_PROVIDER_USAGE_SCENARIO returned by the SetUsageScenario interface ICredentialProvider.

In Windows 10, regardless of whether I’m in the login or when the session is locked, I always use the CPUS_LOGON script, and in the previous version of Windows, CPUS_UNLOCK_WORKSTATION returned when the session was blocked and CPUS_LOGON when logging in.

So, it seems that the changes came with Windows 10, which are not reported on MSDN.

Is there any other way to determine if a usage scenario is a locked session?

Answer 1

I am currently studying the same problem and can work until Microsoft can update the documentation.

Although I still get CPUS_LOGON, we are still in the same session as the blocked user. Using the WTSQuerySessionInformationW function , you can verify that the user is currently logged in to the current session. From there, you can continue as if you were using the CPUS_UNLOCK_WORKSTATION usage script.

UPDATE (1/18/2016): , Microsoft . . CREDENTIAL_PROVIDER_USAGE_SCENARIO:

Windows 10, CPUS_LOGON CPUS_UNLOCK_WORKSTATION . , . . - CPUS_LOGON . , CPUS_LOGON . - , CPUS_UNLOCK_WORKSTATION. , , . Windows , . CPUS_UNLOCK_WORKSTATION . , .

• .
• .
• , , .

, , API-, WTSQuerySessionInformation,

Answer 2

SENS ( ). Microsoft.

https://msdn.microsoft.com/en-us/library/windows/desktop/cc185680(v=vs.85).aspx

/ / . COM+. , , , , .

Answer 3

, CPUS_UNLOCK_WORKSTATION . CPUS_LOGON. Windows API , CPUS_UNLOCK_WORKSTATION, CPUS_LOGON. , , , , .