M.2 SSD to USB adapter eliminated, does not appear in Device dropdown

[taylorstools]

Checklist

• I have been made aware that if my problem can be summarized as "I've created or tried to create a media using Rufus, and ...", and I am not including a log, this issue will be summarily closed.
• I looked at https://github.com/pbatard/rufus/wiki/FAQ to see if my question has already been answered.
• I performed a search in the issue tracker for similar issues using keywords relevant to my problem, such as the error message I got from the log.
• I clicked the 'Log' button (🗒️) or pressed Ctrl-L in Rufus, or used DebugView, and copy/pasted the log into the section that says <FULL LOG> below.
• The log I am copying is the FULL log, starting with the line Rufus version: x.y.z - I have NOT removed any part of it.

Additionally (if applicable):

• I ran a bad blocks check, by clicking Show advanced format options then Check device for bad blocks, and confirmed that my USB is not defective.
• I also tried one or more of the following:
  • Using a different USB drive.
  • Plugging the USB into a different port.
  • Running Rufus on a different computer.
• If using an image, I clicked on the (✓) button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.

Issue description

When trying to use Rufus with this specific M.2 SSD to USB adapter, it is eliminated and does not appear in the Device dropdown. This occurs even if "List USB Hard Drives" is checked.

I replicated this issue with Rufus 4.11 on 2 different PCs, with 2 different SSDs connected to the adapter. The SSDs appear fine in Disk Management and Windows Explorer when connected to the adapter, and can have files copied to them without any issue.

USB debug log below.

Log

Rufus x64 v4.11.2285
Windows version: Windows 11 Pro x64 (Build 26200.7462)
Syslinux versions: 4.07/2013-07-25, 6.04/pre1
Grub versions: 0.4.6a, 2.12
System locale ID: 0x0409 (en-US)
Will use default UI locale 0x0409
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'en-US'
Processing Hub 1:
Processing Hub 2:
  Hub[1] = '\\?\usb#root_hub30#4&f1f70b6&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}'
  Found ID[078]: USB\VID_06CB&PID_0106\2999D08AC7B2
  Found ID[026]: USB\VID_30C9&PID_00E6\200901010001
  Found ID[236]: USB\VID_8087&PID_0037\5&16028319&0&10
Processing 'SCSI' device:
  Hardware ID: ''
Found non-USB non-removable device 'SK hynix PC801 HFS512GEJ9X101N' => Eliminated
0 devices found
Found 5 additional UEFI revocation filters from remote SBAT
Found 4 active Secure Boot certificate entries from remote
Found 1 revoked Secure Boot certificate entries from remote
Processing Hub 1:
Processing Hub 2:
  Hub[1] = '\\?\usb#root_hub30#4&f1f70b6&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}'
  Found ID[078]: USB\VID_06CB&PID_0106\2999D08AC7B2
  Found ID[026]: USB\VID_30C9&PID_00E6\200901010001
  Found ID[236]: USB\VID_8087&PID_0037\5&16028319&0&10
Processing 'SCSI' device:
  Hardware ID: ''
Found non-USB non-removable device 'SK hynix PC801 HFS512GEJ9X101N' => Eliminated
0 devices found

[pbatard]

Thanks for the report.

I'm pretty sure that this issue has to do with some newer SSDs producing very long hardware IDs, and our static buffer to retrieve them all being to small (hence your log report of Hardware ID: '', because Windows should always be able to retrieve the Hardware ID of disk devices, which we then use to properly enumerate UAS drives, like your adapter).

I should be able to fix this for the next release.

[pbatard]

Can you please try the rufus_x64.exe from the VS2022 artifact you will find in the latest buid at https://github.com/pbatard/rufus/actions/runs/20894603176 and confirm that it works better?

[taylorstools]

Thanks for looking into this.

I just tried the alpha build and it is still having the same issue. But now, the log shows the new device. The "General Generic SATA UAS Device" is the M.2 to USB adapter, the SK Hynix drive later in the log is the internal SSD in my computer that Windows is installed to (so it would make sense for that to be eliminated).

Log

Rufus x64 v4.12.2303 (Alpha)
Windows version: Windows 11 Pro x64 (Build 26200.7462)
Syslinux versions: 4.07/2013-07-25, 6.04/pre1
Grub versions: 0.4.6a, 2.12
System locale ID: 0x0409 (en-US)
Will use default UI locale 0x0409
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'en-US'
Processing Hub 1:
Processing Hub 2:
  Hub[1] = '\\?\usb#root_hub30#4&f1f70b6&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}'
  Found ID[078]: USB\VID_06CB&PID_0106\2999D08AC7B2
  Found ID[026]: USB\VID_30C9&PID_00E6\200901010001
  Found ID[236]: USB\VID_8087&PID_0037\5&16028319&0&10
  Found ID[011]: USB\VID_0000&PID_0000\MSFT300123456789ABCDEF
Processing IDs belonging to 'UASPSTOR':
  USB\VID_0000&PID_0000\MSFT300123456789ABCDEF
Processing 'SCSI' device:
  Hardware ID: 'SCSI\DiskGeneral_Generic_SATA____1003'
  Matched with ID[011]: USB\VID_0000&PID_0000\MSFT300123456789ABCDEF
  Matched with Hub[1]: '\\?\usb#root_hub30#4&f1f70b6&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}'
Found non-USB non-removable device 'General Generic SATA UAS Device' => Eliminated
Processing 'SCSI' device:
  Hardware ID: 'SCSI\DiskNVMe______________SK_hynix_PC801_HFS512GEJ9X101N____HPS1'
Found non-USB non-removable device 'SK hynix PC801 HFS512GEJ9X101N' => Eliminated
0 devices found
Found 5 additional UEFI revocation filters from remote SBAT
Found 4 active Secure Boot certificate entries from remote
Found 1 revoked Secure Boot certificate entries from remote
Processing Hub 1:
Processing Hub 2:
  Hub[1] = '\\?\usb#root_hub30#4&f1f70b6&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}'
  Found ID[078]: USB\VID_06CB&PID_0106\2999D08AC7B2
  Found ID[026]: USB\VID_30C9&PID_00E6\200901010001
  Found ID[236]: USB\VID_8087&PID_0037\5&16028319&0&10
  Found ID[011]: USB\VID_0000&PID_0000\MSFT300123456789ABCDEF
Processing IDs belonging to 'UASPSTOR':
  USB\VID_0000&PID_0000\MSFT300123456789ABCDEF
Processing 'SCSI' device:
  Hardware ID: 'SCSI\DiskGeneral_Generic_SATA____1003'
  Matched with ID[011]: USB\VID_0000&PID_0000\MSFT300123456789ABCDEF
  Matched with Hub[1]: '\\?\usb#root_hub30#4&f1f70b6&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}'
Found non-USB non-removable device 'General Generic SATA UAS Device' => Eliminated
Processing 'SCSI' device:
  Hardware ID: 'SCSI\DiskNVMe______________SK_hynix_PC801_HFS512GEJ9X101N____HPS1'
Found non-USB non-removable device 'SK hynix PC801 HFS512GEJ9X101N' => Eliminated
0 devices found

[pbatard]

Thanks for the feedback. Let me look into it, as Rufus seems to have matched it with the relevant USB hub. My guess is that, because it has SATA in its name, we might still be declaring it as a SATA device.

[taylorstools]

Thanks again. My logs have been trying to use SATA M.2 SSDs with this adapter. The adapter supports NVMe drives too, so I decided to connect one of those and see if anything is different/get you more info.

It seems like, depending on if a SATA or NVMe drive is connected, it can show up as either "General Generic SATA UAS Device" or "General Generic PCIE UAS Device". But no matter what, both get eliminated.

Rufus x64 v4.12.2303 (Alpha)
Windows version: Windows 11 Pro x64 (Build 26200.7462)
Syslinux versions: 4.07/2013-07-25, 6.04/pre1
Grub versions: 0.4.6a, 2.12
System locale ID: 0x0409 (en-US)
Will use default UI locale 0x0409
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'en-US'
Processing Hub 1:
Processing Hub 2:
  Hub[1] = '\\?\usb#root_hub30#4&f1f70b6&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}'
  Found ID[078]: USB\VID_06CB&PID_0106\2999D08AC7B2
  Found ID[026]: USB\VID_30C9&PID_00E6\200901010001
  Found ID[236]: USB\VID_8087&PID_0037\5&16028319&0&10
  Found ID[011]: USB\VID_0000&PID_0000\MSFT300123456789ABCDEF
Processing IDs belonging to 'UASPSTOR':
  USB\VID_0000&PID_0000\MSFT300123456789ABCDEF
Processing 'SCSI' device:
  Hardware ID: 'SCSI\DiskGeneral_Generic_PCIE____1003'
  Matched with ID[011]: USB\VID_0000&PID_0000\MSFT300123456789ABCDEF
  Matched with Hub[1]: '\\?\usb#root_hub30#4&f1f70b6&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}'
Found non-USB non-removable device 'General Generic PCIE UAS Device' => Eliminated
Processing 'SCSI' device:
  Hardware ID: 'SCSI\DiskNVMe______________SK_hynix_PC801_HFS512GEJ9X101N____HPS1'
Found non-USB non-removable device 'SK hynix PC801 HFS512GEJ9X101N' => Eliminated
0 devices found
Found 5 additional UEFI revocation filters from remote SBAT
Found 4 active Secure Boot certificate entries from remote
Found 1 revoked Secure Boot certificate entries from remote
0 devices found

[pbatard]

Hold on, something is screwy with your device, as it reports a VID:PID of 0000:0000, which is not allowed:

(...)
Found ID[011]: USB\VID_0000&PID_0000\MSFT300123456789ABCDEF
(...)
Matched with ID[011]: USB\VID_0000&PID_0000\MSFT300123456789ABCDEF

Considering that the strings we report come directly from Windows (we don't construct the VID:PID ourselves), it would look to me like the ELUTENG folks forgot to set a proper VID:PID for their device, which of course will break applications.

I would advise you to look at your disk in Device Manager, and then set View → Device by connection and look at the parent device, and then at at its properties page for Details → Hardware IDs. See the following screenshot for help (for a proper UAS/SSD adapter that does not use VID:PID 0000:0000):

There you should be able to confirm that, Windows Device Manager (so it's not just Rufus) also reports USB\VID_0000&PID_0000 which, again, is not allowed for a consumer device.

Then you can contact your seller or the manufacturer's support and report that issue, so they can fix it, as they should not EVER use a VID:PID of 0000:0000.

Once you confirm that Device Manager also reports 0000:0000, I will have to close this issue, as I am not planning to support nonstandard USB devices in Rufus.

[taylorstools]

Yep, that appears to be the issue:

Feel free to close this out, I'll try to get in contact with the OEM.

[pbatard]

Thanks. I will close this issue.