Before the program in WinXP, Windows 7, doing can be normal use, but can't be used on WIN10;
Device is a USB HID protocol card reader;
Use Createfile get the device handle, found on the Win10 calling Createfile handle does not return,
Consult ace teach me in Win10 how to use the CreateFile, or how to call on Win10 for HID device,

CodePudding user response:

The enumeration in the device manager to have no?

CodePudding user response:

Using GetLastError see errors,

CodePudding user response:

Reply 1: already enumerated, the device manager, program enumeration is correct;
Reply 2: GetLastError also have no reaction, the return value is zero;

CodePudding user response:

Meet the same problem, big head

CodePudding user response:

I met the situation is less than win10 recognition equipment!

CodePudding user response:

reference 5 floor xqhrs232 reply:

I met is not win10 recognition of equipment.

Using the driver genius software upgrades can drive,

CodePudding user response:

refer to 6th floor zhao4zhong1 response:

Quote: refer to the fifth floor xqhrs232 reply:

I met the situation is less than win10 recognition equipment!

Used to drive the elves of software upgrades can drive,

Not drive problem, it's my problem of the board, other board is no problem for hid under win10 recognition,

CodePudding user response:

CreateFile failed to open the file, see GetLastError () is what? Some devices may not be able to open the file way set GENERIC_READ/GENERIC_WRITE at the same time, such as mouse and keyboard, etc

CodePudding user response:

Meet the same problem,
CreateFile return 1,
The strange thing is, in some Win10 x64 computers can use, some simply can't use,
After using FILE_SHARE_READ | FILE_SHARE_WRITE set, can open the device, but events are no response,
Depressed in the...

CodePudding user response:

Close the UAC, firewall, anti-virus software,...
As an administrator to run
.

CodePudding user response:

The registry path may be wrong

CodePudding user response:

In the device manager, see if there are any equipment driver signature problem? Win10 close the driver signature