There are a lot of questions like this, but given the specific circumstances I am adding this one as a new question as there are some specific issues that need to be tackled.
The steps that got me to this point:
- I had a PC with a SATA SSD, this SSD started having issues
- I put in an m.2 SSD and installed Windows 10 on it, but the boot loader/record was not moved, the old SSD was kept inside the system
- My SATA SSD kicked the bucket completely, which made my system inaccessible.
- I swapped in a different SSD and did an error check on the m.2,
which was fine. Windows' recovery terminal would not let me create a
fresh boot record on the m.2, and while it still recognized that
install it would not let me boot into it, just the fresh/blank
install on the new SATA SSD.
As a result, I ordered a new m.2 SSD and an m.2 to SATA enclosure (so I can pull the data off the old m.2, as my motherboard only has one m.2 slot).
I would like to move my Windows install from the old m.2 to the new m.2. The new SSD is larger (1TB) than the old one (128GB), but I cannot boot up the old system, only access its files. I also specifically want to cut out any other drives, but there is no boot record on the m.2, so that needs to be created on the new SSD during this process.
I am okay with 1:1 cloning the drive, as long as I can still create the boot record and resize the partition to the full SSD size. Just fixing the old m.2 SSD is not an option, as it is also degraded (cache on it is broken).
Somehow I need to clone the files from the old to the new SSD and create a boot record on the new SSD, without having the old system accessible.
Is there a process or piece of software that can help me do this, from a live environment running on a USB drive?
Best Answer
When it comes to Windows, 3rd party cloning tools are not an efficient way to image a partition.
Create a
WimScript.ini
config file to specify exclusions or exceptions.DISM
included within them.Configure Partitions
diskpart /s CreatePartitions.txt
):diskpart
>lis dis
>sel dis #
>clean
convert gpt
cre par pri offset=1024 size=665 id=27
cre par pri offset=1024 size=665 id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
format quick fs=ntfs label=WinRE
WinRE.wim
is ~300MB in size)gpt attributes=0x8000000000000001
cre par pri size=100
format quick fs=ntfs label=Boot
active
cre par efi size=100
format quick fs=fat32 label=EFI
cre par msr size=16
cre par pri
UEFI:
cre par pri id=ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
format quick fs=ntfs label=System
cre par pri size=204800
UEFI:
cre par pri size=204800 id=ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
C:\
(recommended)(i.e
%UserProfile%\Documents
,%UserProfile%\Downloads
, etc.)200*1024=204800
)format quick fs=ntfs label=System
DiskPart
via:exit
UEFI:
DiskPart
to ensure it's clean of any installer files.Imaging
WinPE only has 32MB of scratch [temp] space by default, so
/ScratchDir
is required/Compress:Max
to/Compress:Fast
if not saving captured image to an SSDNOTE:
/CheckIntegrity
&/Verify
/Compress:Recovery
is the only compression algorithm available.Example:
/Get-WIMinfo