Need to migrate Windows 10 installation to new SSD , it's a mess.

In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

The current settings on the computer are set to automatic restart after each BSOD.
With this setting it is easy to miss BSOD.

There were one or more BSOD on these dates displaying bugchecks:
6/13
6/16
6/18
7/3
7/4
7/5
7/7
7/13
7/14

There were many more BSOD displaying a failure of the crash dump.

@Teccmo,

I'm just curious...what is the hesitation in either:
1. Doing a clean install of Windows 10 to the new SSD, then copying the original C: partition to the SSD over the top of the C: drive that will be created with the new install or
2. Manually creating a boot partition on the new SSD, then copying the original C: partition to the new SSD and setting up the boot partition on the SSD to load it?

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\windows\system32> cd ..
PS C:\windows> cd ..
PS C:\> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\> dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.165

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\> chkdsk /scan
The type of the file system is NTFS.
Volume label is Original C.

Stage 1: Examining basic file system structure ...
699904 file records processed.
File verification completed.
10825 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
20317 reparse records processed.
875974 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
20317 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
88036 data files processed.
CHKDSK is verifying Usn Journal...
38820360 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

976264034 KB total disk space.
201907704 KB in 434723 files.
259016 KB in 88037 indexes.
0 KB in bad sectors.
1053026 KB in use by the system.
65536 KB occupied by the log file.
773044288 KB available on disk.

4096 bytes in each allocation unit.
244066008 total allocation units on disk.
193261072 allocation units available on disk.
PS C:\> get-disk

Number Friendly Name Serial Number HealthStatus OperationalStatus Total Size Partition
Style
------ ------------- ------------- ------------ ----------------- ---------- ----------
3 ST2000DX00... Z4Z80HBN Healthy Online 1.82 TB MBR
2 TOSHIBA-TR200 Y7OB60KHK46S Healthy Online 223.57 GB MBR
1 WDC WD10EZ... WCC3FDY9J7F8 Healthy Online 931.51 GB MBR
0 WDC WD5000... WD-WMAYUK151044 Healthy Online 465.76 GB MBR


PS C:\> get-physicaldisk

FriendlyName SerialNumber MediaType CanPool OperationalStatus HealthStatus Usage Size
------------ ------------ --------- ------- ----------------- ------------ ----- ----
WDC WD5000AAKX-221CA1 WD-WMAYUK151044 Unspecified False OK Healthy Auto-Select 465.76 GB
TOSHIBA-TR200 Y7OB60KHK46S SSD False OK Healthy Auto-Select 223.57 GB
WDC WD10EZEX-21M2NA0 WCC3FDY9J7F8 HDD False OK Healthy Auto-Select 931.51 GB
ST2000DX002-2DV164 Z4Z80HBN HDD False OK Healthy Auto-Select 1.82 TB


PS C:\> Get-Disk 0 | Get-StorageReliabilityCounter

DeviceId Temperature ReadErrorsUncorrected Wear PowerOnHours
-------- ----------- --------------------- ---- ------------
0 2 0 7132


PS C:\> Get-Disk 1 | Get-StorageReliabilityCounter

DeviceId Temperature ReadErrorsUncorrected Wear PowerOnHours
-------- ----------- --------------------- ---- ------------
1 0 0 20774


PS C:\> diskpart

Microsoft DiskPart version 10.0.17134.1

Copyright (C) Microsoft Corporation.
On computer: RYZEN5-PC

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 465 GB 1024 KB
Disk 1 Online 931 GB 1024 KB
Disk 2 Online 223 GB 223 GB
Disk 3 Online 1863 GB 0 B

DISKPART> list volume

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 F ATICD13-087 CDFS DVD-ROM 493 MB Healthy
Volume 1 E 500gb stora NTFS Partition 465 GB Healthy
Volume 2 C Original C NTFS Partition 931 GB Healthy Boot
Volume 3 D FireCuda 1s NTFS Partition 1863 GB Healthy System

DISKPART> list volume

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 F ATICD13-087 CDFS DVD-ROM 493 MB Healthy
Volume 1 E 500gb stora NTFS Partition 465 GB Healthy
Volume 2 C Original C NTFS Partition 931 GB Healthy Boot
Volume 3 D FireCuda 1s NTFS Partition 1863 GB Healthy System

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> detail disk

WDC WD5000AAKX-221CA1
Disk ID: 583CA8D9
Type : SATA
Status : Online
Path : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0103)#PCI(0001)#ATA(C00T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 1 E 500gb stora NTFS Partition 465 GB Healthy

DISKPART> select disk 1

Disk 1 is now the selected disk.

DISKPART> detail disk

WDC WD10EZEX-21M2NA0
Disk ID: C669617B
Type : SATA
Status : Online
Path : 1
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0103)#PCI(0001)#ATA(C01T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : Yes
Pagefile Disk : Yes
Hibernation File Disk : No
Crashdump Disk : Yes
Clustered Disk : No

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 2 C Original C NTFS Partition 931 GB Healthy Boot

DISKPART> select disk 2

Disk 2 is now the selected disk.

DISKPART> detail disk

TOSHIBA-TR200
Disk ID: 855EE9D0
Type : SATA
Status : Online
Path : 4
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0103)#PCI(0001)#ATA(C04T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No

There are no volumes.

DISKPART> select disk 3

Disk 3 is now the selected disk.

DISKPART> detail disk

ST2000DX002-2DV164
Disk ID: A541C08D
Type : SATA
Status : Online
Path : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0103)#PCI(0002)#PCI(0600)#PCI(0000)#ATA(C00T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 3 D FireCuda 1s NTFS Partition 1863 GB Healthy System

DISKPART>

NavyLCDR said:

@Teccmo,

I'm just curious...what is the hesitation in either:
1. Doing a clean install of Windows 10 to the new SSD, then copying the original C: partition to the SSD over the top of the C: drive that will be created with the new install or
2. Manually creating a boot partition on the new SSD, then copying the original C: partition to the new SSD and setting up the boot partition on the SSD to load it?

Well, nothing really, other than the fact that I've been busy all day, and I just sat down and did what some of the other posts told me to in the last hour or so. That and thinking a clean install of windows 10 and a c: partition copy won't be utilizing the little bit of space on the ssd, it's only 240gb.

2. This sounds like a better option, just haven't done it before.

NavyLCDR said:

@Teccmo,

I'm just curious...what is the hesitation in either:
1. Doing a clean install of Windows 10 to the new SSD, then copying the original C: partition to the SSD over the top of the C: drive that will be created with the new install or
2. Manually creating a boot partition on the new SSD, then copying the original C: partition to the new SSD and setting up the boot partition on the SSD to load it?

This is very easy to do with Macrium Reflect Free and reliable How to Clone Windows from a Hard Disk to an M.2 SSD (and Keep It Bootable) - YouTube this Video shows you how to use MR what you want to do is create an Image of your C: Partition, then remove all drives except the SSD your want windows installed on, Do a clean install, then use MR to restore your c: image to the C: on your new SSD it will delete the current data in restore your data. During the restore you can adjust the C: partition to fit your data that why I linked the video it shows you how to adjust the C: partition. Of course, before you do any of this your C: Partition has to be less than the total data of the SSD.
You can't lose your data because its still in the Image you created on an external disk after you restore it the image will still be safe there until you overwrite it or delete it. The Clean install is only to set up your SSD UEFI with the correct partitions to boot your C:

After following some of the threads in here, I have the SSD successfully booting and cloned as the C: drive, with the former 1tb C: drive disconnected for now. I used Macrium Reflect after following some of the diskpart and shell commands in earlier threads, and it worked like a charm. I had to choose from a set of windows 10 installations, and then there was the microsoft windows boot repair thing that ran for a minute and rebooted, and everything seems to be running fine so far. It's definitely a lot faster, I can see a major difference. Thanks to anyone that contributed in this post. Gave me a real smile haha.