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.

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.

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.

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".

About the partition number as recovered by the api, it makes little sense to show the value 0 that it is returned ( as 0 ) , I mean. I do understand how the Api would return a 0, since the numbering is 1-based, maybe it would make more sense to "translate" the 0 to "N/A" or something like that.

If I get this right, this would happen only on non-first partition entries on Removable media, which would raise an interesting (side) question.

What happens on Windows 10 (latest-latest) that seemingly just changed the way Removable media is threated?

I made an e01 image with encase 8, image from whole 500gb HD. Now I need to restore it to other 500GB HD. How can I do it? The software dont show me any HD when I click disk unit, only when I click disk part. The HD is new, its not formatted. How can I choose this new HD and restore the e01 image to it?

thank you.

Edited: It was giving error on x64 version, with 32 its working normally.

I made an e01 image with encase 8, image from whole 500gb HD. Now I need to restore it to other 500GB HD. How can I do it? The software dont show me any HD when I click disk unit, only when I click disk part. The HD is new, its not formatted. How can I choose this new HD and restore the e01 image to it?

thank you.

Edited: It was giving error on x64 version, with 32 its working normally.

Glad you found on a solution the solution.

On x64, I believe you need to explicitly run as admin whereas on x32 CloneDisk will natively run as admin (provided you are an admin).