Windows 10: Windows Hello or login screen - API for customer authentication device via TCP/IP request

My user story is to unlock the windows 10 / 11 login screen with an custom authentication device. The device is a development board connected via ethernet / LAN to the windows host PC. The device sends the request to unlock the login screen via ethernet TCP/IP.1. Windows PC is locked at login screen. 2. The user enters the room.3. The user moves in front of the PC.4. Our device detects and identifies the user in front of the Windows PC.5. The ethernet device sends the unlock request to our app or service on the Windows PC via ethernet.6. Our app or service receives the request and unlocks the

:)

 

Windows 10 only allowing WSD printing and not TCP/IP printing for any printer I attempt to install

Hi,



Thank you for posting your query in Microsoft Community.



I understand your concern and will assist you to resolve this issue.

I suggest you to follow the steps below and check if it helps.

• 
  Press Windows + X, select Control panel.
  
• 
  Select Devices and Printer.
  
• 
  Then click on "Add a printer" then choose printer wasn't listed then "Add a printer using a TCP/IP address or host name.
  

Hope this helps. If the issue remains unresolved, please get back to us and we would be happy to help.

 

a request for device descriptor request failed

my bios is and custom unlocked bios (latest version) (thanks to Bios Mods -The Best BIOS Update and Modification Source ) because of lenovo hardware whitlist maybe thats causing the problem???

 

a request for device descriptor request failed

Maybe it's time to step back from the current efforts, and start over. I suggest you read over this excellent tutorial and try all of its steps: [Solved] Unknown USB Device (Device Descriptor Request Failed) for Windows 10 - Driver Easy. The one that may provide you with some easy relief is the one where you uninstall the device whose descriptor is failing, reboot, and see what happens when device enumeration recurs during boot-up. If you're lucky, it will fix itself.
HTH,
--Ed--