Windows 10: Display the keyboard when using a third-party credential provider on Windows instead of the...

Good afternoon. We are currently using third-party software for two-factor authentication. The essence of this software is that the standard Windows credential provider is replaced with a third-party credential provider for MFA and we display a different login window instead of the standard Windows welcome. The problem is that When using a third-party credential provider on our Windows PCs with touch screens, the touch/virtual keyboard stops popping up.According to the developer of the third-party credential provider, the Windows keyboard display is not enabled because... This is a limitation

:)

 

Windows Network Credentials

Hi Keith,

We suggest that you disable Credential Manager before mapping your Drives. Please follow these steps to disable Credential Manager:

• In the search box type “Services”
• Right click on “Services” and select “Run as Administrator”
• In the Services Window, look for Credential Manager Service and click “Stop”.
• Restart the computer and go back the Credential Manager Service and set it to “Automatic”.
• Restart the computer again.

Please keep us updated if you were able to map your drives.

 

Network Credentials

Hi Sammy,

To assist you better regarding your concern with network credentials, have you checked the Windows credentials for any information about the username and password for the network credentials? If not yet, follow the steps below to access Windows Credentials
manager.

• Press the Windows icon on the desktop.
• Type in Windows Credentials.

We would appreciate as well if you could provide us a screenshot.

Let us know how it goes.

 

Scheduled tasks run with elevated privileges can't access stored Windows credentials

It seems that after Creators update scheduled tasks run with elevated privileges ('run with highest privileges' option) can't access stored Windows credentials. Is that a bug or an intentional change and is there a recommended workaround?

Here's one way to reproduce the behaviour:

• Start Credential Manger and add some Windows share credentials.
• In a console window type 'cmdkey /list', which should list the added credentials
• Create a task in a task manager:
  • Trigger: on user logon
  • Action: run cmd.exe
  • Tick the 'run with highest privileges' option
• Reboot the machine and log in
• In the console window (let's call it 'console 1') opened from the scheduled task type 'cmdkey /list'. This most likely won't display the credentials added in step 1 and properly listed in step 2. ->
  This looks like a bug
• Now, without closing 'console 1' open another console window as an administrator (let's call it 'console 2') and type 'cmdkey /list'. This will properly list credentials added in step 1.
• Switch to 'console 1' and type 'cmdkey /list' again. This time the credentials are listed properly, unlike in step 5. It looks like an access to Windows credentials was somehow 'unlocked' by step 6.