How to replace faulty disk/motherboard and use Windows 10 again?

smalltech

Distinguished
Apr 10, 2009
574
3
18,995
My windows is install in Samsung SSD disk. Windows 10 installed in SSD disk.

I store data and files in another WD internal hard disk.

For example if now SSD drive faulty or motherboard faulty, I will just buy new SSD (any model) or new motherboard (any model) then reinstall Windows 10.

May I know is there any file in the old SSD C: I need to backup/transfer to new SSD, so that new SSD or new motherboard will work smoothly?

Is there important file to backup in the old C: ?

Add question: I assume C:\Users\Username is the most important folder as it may contain important data?
What user files do you copy usually?
I assume C :\Users\Username\Desktop is more important only, since sometimes I put some file on desktop.

Thanks
 
Solution
The Windows 10 license is stored on the motherboards in a section of the UEFI and also on the Microsoft License server under your Microsoft Account. So removing and installing Windows 10 onto a new drive is not an issue.

For a motherboard switch this is a bit more problematic as any license that is linked to the hardware will see a motherboard switch as a new computer. In this case you can try to get the Windows license server to fix the license onto your new motherboard, but you may need to call Microsoft in this case and describe to them what happened to get them to fix it on their side. The same would need to be done with any other software that you have that has a license linked to the hardware.

caqde

Distinguished
The Windows 10 license is stored on the motherboards in a section of the UEFI and also on the Microsoft License server under your Microsoft Account. So removing and installing Windows 10 onto a new drive is not an issue.

For a motherboard switch this is a bit more problematic as any license that is linked to the hardware will see a motherboard switch as a new computer. In this case you can try to get the Windows license server to fix the license onto your new motherboard, but you may need to call Microsoft in this case and describe to them what happened to get them to fix it on their side. The same would need to be done with any other software that you have that has a license linked to the hardware.
 
Solution