Actually, this is a "normal" behavior : windows only "consider" the first primary partition on a removable disk.
All other partitions are non existing (for windows) and therefore numbered with 0.
As opposed to a fixed drive, where all partitions would be numbered.
Sure, and as said it is "minor", but if you go Advanced->MBR, the # is about "Partition entry" or "Partition slot", that is what I would find confusing if I didn't already know about the matter.
Maybe - similarly to the PBR editor, you could have "valid" (as seen by windows) partitions with white background and "not valid" (as seen by windows) partitions background gray. , but IMHO the number should be referred to the "entry" or "slot".
Actually, "Convert RAW to VMDK/VHD" would need to be reworded : it does not really convert but actually creates a header.
Disk conversion is mostly meant as converting files (vmdk, vhd, ewf, vdi, etc) to RAW.
No, allow me to diasgree, the scope is always that of making things as simple and as less confusing as possible.
A conversion means to "transform" something in something else.
If you transform a whole disk RAW image into a "fixed" VHD
by means of a header appending a footer you are converting.
If you transform a "fixed" VHD into a RAW image by means of stripping a
header footer you are converting.
If you transform a whole disk RAW image into a "fixed" VMDK by means of a header (do you actually do that conversion? Or are you adding a VMDK descriptor file? Haven't tried. ) you are making a conversion, etc.
In other words, I would find easier to have a choice "Image format conversion" where you can chose as source and destination suitable "couples" of formats, without the "special cases" for RAW to VHD and RAW to VMDK.