2,795 questions
Problems with using the SetupDiGetClassDevs interface On Windows Server 2016
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(32, 5%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
鸿 徐
0
Reputation points
Background of the problem:
- We use the SetupDiGetClassDevs (&Guid_DEVINTERFACE-STOAGEPORT, NULL, NULL, DIGCF-PRESENT | DIGCF-DEVICEINTERFACE) interface to enumerate the interfaces of storage class devices.
- Then, based on the handle, we further obtain the device path to select our own raid card (currently, there are three devices that can be listed, including two Sata AHCI controllers and our raid card).
Now we run the script pressure test and find that the SetupDiGetClassDevs interface returns an error (the probability is small, and the next call will be successful in a few seconds). The error code is 6 (The Handle is invalid). Please ask:
- When will this interface report this error code?
- I understand that even if the RAID card is not connected, this interface should still list the two Sata AHCI controllers of the system and not report invalid handles?
Windows development | Windows API - Win32
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 34%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXY%3C/text%3E%3C/svg%3E)
Xiaopo Yang - MSFT 12,731 Reputation points Microsoft External Staff2023-12-15T07:54:38.4066667+00:00 Can you reproduce it on Windows11 constantly? Could you please provide a minimal sample?
The error code is 6 (The Handle is invalid).
What handle does
SetupDiGetClassDevsreport? Is It the internal handleSetupDiGetClassDevsrequests? -
鸿 徐 0 Reputation points
2023-12-15T09:50:18.3+00:00 DEFINE_GDUID(GUID_DEVINTERFACE_STORAGEPORT, 0x2accfe60,0xc130,0x11d2, 0xb0,0x82,0x00,0xa0,0xc9,0x1e,0xfb,0x8b); SP_DEVICE_INTERFACE_DATA ifdata; SP_DEVINFO_DATA devInfo; handle = SetupDiGetClassDevs (lpGuid, NULL, NULL, DIGCF_PRESENT | DIGCF_DEVICEINTERFACE) if(handle == INVALID_HANDLE_VALUE) { ... } PSP_DEVICE_INTERCADE_DETAIL_DATA pDetail = malloc(...) pDetail->cbsize = sizeof(SP_DEVICE_INTERCADE_DETAIL_DATA) bResult = true; while (bResult) { ifdata.cbsize=sizeof(ifdata) bResult = SetupDiEnumDeviceInterface(handle, NULL,lpGuid, count, &ifdata); if(bResult) { devInfo.cbsize = sizeof(devInfo); bResult = SetupDiGetInterfaceDeviceDetail(handle, &ifdata, pDetail, size, NULL, &devInfo); if(bResult){ bResult = SetupGetDeviceResiterPropery(&devInfo, SPDRP_ADDRESS, null, &addr, sizeof(addr), NULL); ... ... } } } if(hanle != INVALID_HANDLE_VALUE) { SetupDiDestoryDeviceInfoList(hanle); } The result returned by SetupDiGetClassDevs is INVALID_HANDLE_VALUE. Normally, it runs normally, and the probability of this problem occurring is very low, but it will recover after a few seconds -
Deleted
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
-
鸿 徐 0 Reputation points
2023-12-15T09:58:12.1766667+00:00 DEFINE_GDUID(GUID_DEVINTERFACE_STORAGEPORT, 0x2accfe60,0xc130,0x11d2, 0xb0,0x82,0x00,0xa0,0xc9,0x1e,0xfb,0x8b); SP_DEVICE_INTERFACE_DATA ifdata; SP_DEVINFO_DATA devInfo; handle = SetupDiGetClassDevs (lpGuid, NULL, NULL, DIGCF_PRESENT | DIGCF_DEVICEINTERFACE) if(handle == INVALID_HANDLE_VALUE) { ... } PSP_DEVICE_INTERCADE_DETAIL_DATA pDetail = malloc(...) pDetail->cbsize = sizeof(SP_DEVICE_INTERCADE_DETAIL_DATA) bResult = true; while (bResult) { ifdata.cbsize=sizeof(ifdata) bResult = SetupDiEnumDeviceInterface(handle, NULL,lpGuid, count, &ifdata); if(bResult) { devInfo.cbsize = sizeof(devInfo); bResult = SetupDiGetInterfaceDeviceDetail(handle, &ifdata, pDetail, size, NULL, &devInfo); if(bResult){ bResult = SetupGetDeviceResiterPropery(&devInfo, SPDRP_ADDRESS, null, &addr, sizeof(addr), NULL); ... ... } } } if(hanle != INVALID_HANDLE_VALUE) { SetupDiDestoryDeviceInfoList(hanle); } The result returned by SetupDiGetClassDevs is INVALID_HANDLE_VALUE. Normally, it runs normally, and the probability of this problem occurring is very low, but it will recover after a few seconds -
Xiaopo Yang - MSFT 12,731 Reputation points Microsoft External Staff
2023-12-18T03:22:59.6233333+00:00 It could depend on the state of device if that is ready to be queried.
If this has a big impact on you, you can send feedback to Microsoft with the Feedback Hub app about the situation.
-
鸿 徐 0 Reputation points
2023-12-19T02:24:48.4433333+00:00 Under normal circumstances, when I use SetupDiGetClassDevs (lpGuid, NULL, NULL, DIGCF_PRESENT | DIGCF_DEVICEINTERFACE) or SetupDiGetClassDevs (NULL, NULL, NULL, DIGCF_ALLCLASSES), I won't report an error. So, I wonder if the SetupDiGetClassDevs interface will return an error (GetLastError=6) when the Windows system is in what state?
-
Xiaopo Yang - MSFT 12,731 Reputation points Microsoft External Staff
2023-12-19T07:07:36.93+00:00 I try answering. When the device is held by other processes or not ready.
For accuracy, you can send feedback to Microsoft with the Feedback Hub app about the situation.
-
Xiaopo Yang - MSFT 12,731 Reputation points Microsoft External Staff
2023-12-27T03:05:04.86+00:00 @鸿 徐, Can the question be marked as completion? Or have you sent feedback to Microsoft? It's better to show the feedback link.
Sign in to comment
Sign in to answer