Rufus v4.13 still does not filter out Bitdefender Virtual Disks correctly

[R-Adrian]

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 also tried one or more of the following:
  • Running Rufus on a different computer (that also has Bitdefender installed) - same behaviour happens there too.

Issue description

in Rufus v4.12 the Bitdefender virtual disks were supposed to be filtered out, but they still show up in Rufus v4.13

Log

Rufus x64 v4.13.2316 (Portable)
Windows version: Windows 11 Pro x64 (Build 26200.8246)
Syslinux versions: 4.07/2013-07-25, 6.04/pre1
Grub versions: 0.4.6a, 2.14
System locale ID: 0x0409 (en-US)
Will use default UI locale 0x0409
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'en-US'
Notice: The ISO download feature has been deactivated because 'Check for updates' is disabled in your settings.
Found VHD device 'Microsoft Virtual Disk'
Could not get Disk Extents: [0x00000001] Incorrect function.
Could not get Disk Extents: [0x00000001] Incorrect function.
Found USB 3.0 device 'Kingston DataTraveler 3.0 USB Device' (0951:1666)
2 devices found
Could not get Disk Extents: [0x00000001] Incorrect function.
Disk type: FIXED, Disk size: 32 MB, Sector size: 512 bytes
Cylinders: 4, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 1
Disk GUID: {3A182634-ECAF-4D9C-9CE0-9E61EC7A093A}
Max parts: 128, Start Offset: 17408, Usable = 33520128 bytes
Partition 1:
  Type: Microsoft Basic Data Partition
  Name: 'Bitdefender Partition'
  Detected File System: NTFS
  ID: {BA5FBC33-B5DD-4468-B9FB-349269EF43B8}
  Size: 31.9 MB (33488896 bytes)
  Start Sector: 64, Attributes: 0x8000000000000001
2 devices found
Could not get Disk Extents: [0x00000001] Incorrect function.
Disk type: Removable, Disk size: 14.6 GB, Sector size: 512 bytes
Cylinders: 1912, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0xA9F2916D
Drive has a Windows 7 Master Boot Record
Partition 1:
  Type: FAT32 LBA (0x0c)
  Detected File System: FAT32
  Size: 14.6 GB (15727591424 bytes)
  Start Sector: 2048, Boot: Yes
2 devices found
Could not get Disk Extents: [0x00000001] Incorrect function.
Disk type: FIXED, Disk size: 32 MB, Sector size: 512 bytes
Cylinders: 4, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 1
Disk GUID: {3A182634-ECAF-4D9C-9CE0-9E61EC7A093A}
Max parts: 128, Start Offset: 17408, Usable = 33520128 bytes
Partition 1:
  Type: Microsoft Basic Data Partition
  Name: 'Bitdefender Partition'
  Detected File System: NTFS
  ID: {BA5FBC33-B5DD-4468-B9FB-349269EF43B8}
  Size: 31.9 MB (33488896 bytes)
  Start Sector: 64, Attributes: 0x8000000000000001

[R-Adrian]

quote from rufus/src/dev.c:

// Bitdefender now uses a special 32 MB VHD
				if (props.is_VHD && safe_strcmp(label, bitdefender_label) == 0 && GetDriveSize(drive_index) <= 32 * MB) {
					uprintf("Device eliminated because it is a Bitdefender VHD");
					safe_free(devint_detail_data);
					break;
				}

seems Bitdefender has increased the VHD to 33 MB (as reported by Rufus v4.13) ... are they doing it on purpose to confuse Rufus? or are they using Rufus internally and need it to access the VHD?

[pbatard]

Nah, your screenshot shows a size of 33520128 bytes which is the exact size we tested with, and which is 31.96 MB.

The one difference I see is that your disk is labelled Bitdefender Virtual Disk in the dropdown, whereas the one we tested is labelled Bitdefender Partition, so it looks like they didn't change the size, but they changed how they labelled the partition... This is annoying, because I can't go hunt every time the Bitdefender folks decide that their label would look better one way or another, and a blanket search for Bitdefender might be a bit too heavy handed, though it's probably what I'm going to have to do.

Is there any chance you could locate the VHD used by bitdefender and share it with us.

If anything, you should be able to dump the drive to VHD or VHDX using Rufus, by clicking the yellow save icon you see next to the drive. Then you should be able to zip that file and add it as an attachment here, or you can e-mail it directly to me at pete@akeo.ie.

[R-Adrian]

i dumped the vhd with Rufus and opened it in 7-zip
here is what it contains (with Flat view mode, to show the entire subfolders inline)

[pbatard]

Please send me the VHD you dumped. You can zip it and then send in one of the two ways I highlighted above. I need to work with the actual VHD rather than screenshots that force me to guess lots of stuff. Thank you.

[R-Adrian]

ok... i sent the VHD via email there, in a 7zip archive.

[pbatard]

Thanks I got it and I can replicate the issue. Will look into how I want to address this in Rufus.

[pbatard]

I believe the filtering should work now. Feel free to test with the rufus_x64.exe from the VS2022 Artifact from https://github.com/pbatard/rufus/actions/runs/24607672623.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.