Old HDD Shows Offline After Cloning Signature Collision Fix
The clone works, the new SSD boots beautifully — but when you reconnect the old HDD for extra storage, Windows shows it as Offline and will not touch it. Nothing is broken. Windows has found two disks with the same signature.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 10 minute fix
🎥 Watch the full video — HDD change and complete disk clone, step by step
This surprises everyone the first time: a cloned disk and its original cannot be online together until one of them gets a new disk signature. The fix takes two minutes, in the GUI or with diskpart, and it does not touch a single file.
Command Prompt — diskpart
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 476 GB 0 B *
Disk 1 Offline 931 GB 0 B *
DISKPART> select disk 1
Disk 1 is now the selected disk.
DISKPART> uniqueid disk
Disk ID: 8F3A21C7
Disk Management shows the same story in words — The disk is offline because it has a signature collision with another disk that is online.
1
Why Windows Refuses to Bring the Old Disk Online
Every disk carries an ID — the disk signature. Cloning copies it exactly, so after a clone your PC contains two disks claiming the same identity. Windows protects you from that confusion by forcing the second disk offline. It is not faulty, not unformatted and not empty — open Disk Management and you will see the disk listed as Offline, with the signature collision message when you hover or right-click it. Your data is untouched; Windows is simply refusing to use two disks with one name.
2
The Easy Fix — Let Disk Management Assign a New Signature
First, be sure the PC is booting happily from the new drive alone. Do not do this step until the clone has proven itself.
Reconnect the old disk and open diskmgmt.msc.
Find the disk marked Offline, right-click on its name area on the left, and choose Online.
Windows detects the collision and automatically writes a new random signature to the old disk, then brings it online with drive letters. Done — it now works as a normal extra drive.
3
The diskpart Fix — Set the Signature Yourself
If the GUI route is unavailable — a server, or a disk you are preparing from a recovery environment — diskpart does the same job. Open an administrator Command Prompt and work through these commands, checking the disk number twice before selecting anything:
diskpart
list disk — identify the OFFLINE disk by its size.
select disk 1 — replace 1 with the offline disk number from your list.
uniqueid disk — shows the current signature, as in the panel above.
For an MBR disk, set a new 8-digit hexadecimal ID: uniqueid disk id=9B21F04D — use your own random value, different from the other disk.
For a GPT disk the ID is a full GUID: uniqueid disk id={3F8A1C44-2B7E-4D91-9E02-6A5C81D47F20} — generate a fresh GUID rather than reusing one.
online disk then exit. The disk appears in Explorer like any other drive.
4
Now Decide What the Old Disk Is For
Keep it as a data drive as-is — your old Windows and files stay available as plain folders. That is genuinely useful for a few weeks while you settle in.
Or format its old Windows partition and use the whole disk as clean storage. Do this only after the verification period, and double-check you are formatting the OLD disk — the sizes in Disk Management tell you which is which.
If the old disk was failing, do not keep using it for anything you care about. A failing disk promoted to "backup drive" is a trap, not a backup.
🔴 Honest note: changing the signature does not delete or alter any file on the disk — it only renames the disk itself in Windows eyes. But never change the signature of the disk you are currently booted from, and never rush this step before the clone has booted alone successfully.
🎥 Watch the Complete Video Guide
The full process on a real PC — changing the HDD and cloning the complete disk, step by step.
Did the signature collision damage anything on the old disk?
No. The disk is complete and untouched — Windows simply refuses to mount two disks that claim the same identity. The moment the old disk gets a new signature, every file appears exactly as before.
Why did Windows not complain during the clone itself?
Cloning tools work below Windows, writing the copy directly. The collision is only detected when Windows itself tries to bring both finished disks online in the same running system — which is precisely the moment you reconnect the old drive after the job.
Can I avoid the collision completely?
Only by never using the two disks together, or by wiping the old disk in another machine first. There is no cloning mode that changes the signature during the copy — and you would not want one, because the clone must be an exact bootable copy. Assigning the new signature afterwards is the designed workflow.
This guide is based on the Technical Anshu video on cloning a full disk to a new drive • Stuck on a step — ask in the video comments and the community will help 🙏