A GPT/MBR disk
cannot “flip” just by moving it between the Dell and the Lenovo. The partition table is stored on the Samsung itself. So if one PC shows GPT and the other shows MBR,
one of these is happening:
1)
You’re not looking at the same physical disk (easy to do if multiple disks are attached and Windows renumbers them),
or
2) The disk is actually
MBR with an Extended partition + many Logical drives (this allows lots of drive letters like J–Q even though the disk is still MBR),
or
3) One of the PCs is showing a
stale/cached view until you refresh/rescan.
There is
no SSD vs HDD rule that makes partition style behave differently. SSD vs HDD doesn’t matter here.
What “guarantee” can dismiss the nightmare?
This one:
If both PCs show Partition style: GUID Partition Table (GPT) in Disk Management → right‑click the disk label (“Disk X”) → Properties → Volumes, then the disk is GPT, full stop.
And if either PC shows
MBR there, then it’s MBR, full stop.
Everything else (drive letters, Dynamic prompts) is secondary.
Do this exact 30‑second check on BOTH PCs (and report just the one line)
On each machine, with the Samsung plugged in:
- Win+X → Disk Management
- Find the Samsung by size (~1863 GB)
- Right‑click the left box that says Disk X → Properties → Volumes
- Tell me what it says for Partition style:
- “GUID Partition Table (GPT)” or
- “Master Boot Record (MBR)”
That’s the only thing that matters right now.
If you want an even clearer confirmation (copy/paste)
In
PowerShell (Admin) on each PC:
Get-Disk | Format-Table Number,FriendlyName,Size,PartitionStyle,IsRemovable -Auto
Paste the one line that corresponds to the Samsung (by size/name).
About my earlier “lesson learned” comment
You’re right to push back: you
did initialize on the Lenovo first. My point (poorly phrased) was simply:
initialize to GPT once, then verify
by that “Partition style” line on any other PC before doing lots of work.
Reply with:
- Dell “Partition style = ____”
- Lenovo “Partition style = ____”
…and I’ll tell you exactly what’s going on (most likely: it’s actually MBR+extended/logical, or you’re checking the wrong Disk # on one machine).