Some more feedback needed on Diskpart

sportsfan148 · 14 Aug 2018

Hi all, I've recently done a clean Windows 10 installation using a Media Creation Tool created flash drive. I always look afterwards in Disk Management or Diskpart to see if the partitions are set up correctly. My clean installation method is always the same I delete all partitions first and then let Windows set up the partitions it requires.
This is how my hard disk always looks in Diskpart when i Select Disk 0 and type Detail Disk.
Volume 1 Recovery NTFS Partition 450mb Healthy
Volume 2 C NTFS Partition 930GB Healthy Boot
Volume 3 FAT32 Partition 100MB Healthy System
If I select Volume 1 and type Detail Partition I get
Partition 1
Type
hidden
required
attrib
offset in bytes
* Volume 1 Recovery NTFS Partition 450Mb Healthy
Everything seems perfect so far

However, if I do it another way and instead firstly I type list partition and Select Partition 1, then Detail Partition I see this
Partition 1
Type
hidden
required
attrib
offset in bytes
* Volume 4 Recovery NTFS Partition 450Mb Healthy Hidden

Does anyone know why the Volume in Partition 1 changes from Volume 1 in the first method to being shown as a Hidden Volume 4 when I select the Partition first in the second method.
I wondered if other users are seeing the same on their systems if they have done a clean Windows setup allowing Windows to set up the partitions as required as I did. It may show differently if you have set up your own partitions...I don't know. I stumbled across this by accident and Im wondering if this is normal behaviour?

Steve C · 15 Aug 2018

I find MiniTool Partition Free gives a more informative view and you can explore the partition contents.

EdTittel · 16 Aug 2018

Turns out this is a well-known Windows behavior. You can stop it from occurring by first firing up diskmgmt.msc before launching a command prompt or PowerShell window. Or, like me, you can just learn to live with it, and remember to use the list <thing> (i.e. disk, volume, partition) before working on the <thing> inside DiskPart. Here's a Microsoft support document that addresses this behavior directly and explicitly: Volume numbers in the "Volume ###" column may change every time that you run the "List Volume" command in the Diskpart.exe utility in Windows
HTH,
--Ed--

MadPaxx · 16 Aug 2018

EdTittel said:

Turns out this is a well-known Windows behavior. You can stop it from occurring by first firing up diskmgmt.msc before launching a command prompt or PowerShell window. Or, like me, you can just learn to live with it, and remember to use the list <thing> (i.e. disk, volume, partition) before working on the <thing> inside DiskPart. Here's a Microsoft support document that addresses this behavior directly and explicitly: Volume numbers in the "Volume ###" column may change every time that you run the "List Volume" command in the Diskpart.exe utility in Windows
HTH,
--Ed--

Very Nice Info

Or you can always remember to rename each HDD something u would remember
Like //// Black HDD for Backups

Compumind · 17 Aug 2018

Hi.

Ed is correct.

However, you can download a free trial of EaseUS Partition Manager that will give you great information.

Here is the link -

EaseUS Partition Master - Best partition manager software for Windows PC and Server users.

Hope this helps a bit.