Transferring existing Win10 installation

From: philo

On 07/18/2018 09:17 PM, Paul wrote:
tumppiw wrote:
I wonder what would happen / Can I "clone" my exiting Win10SpringCU
(winver=17134.165) from my existing system?? (Windows is a free
upgrade from Win7HP)

Current system:
ASUS F1A75-M pro m/b (BIOS 2203) , AMD Llano A6-3650 boxed, 4*4096MB
(16GB) KHX1600C9D3/4GX,
Asus Radeon HD7790 DirectCU II OC 1GB,
Kingston SSDNow V300 120GB (as C,

to my new system:
Intel Core i5-8600K,MSI B360 GAMING PLUS, G.Skill RipjawsV DDR4 3200
MHz 16 Gt (2 x 8 GB), MSI GEFORCE GTX 1050 TI 4GT LP, Kingston A1000
240 Gt (nVMe SSD)


Transfer or new/clean install (I have a Win10HomeCreatorsUpdate
USB-media)???

And I know everybody says: CLEAN INSTALL , but that would be a PITA
(as I've had/used/upgraded it since Win10 came out) and I don't have
all my softwares install media anymore...


I will be changing PSU, case, transferring MY HDDs (Samsung
HD154UI,Seagate ST300DM001,Verbatim(Toshiba)DT01ACA300

Rest of new system is:
Corsair CS650M, BitFenix Shinobi Window (haven't decided if I will
transfer opticalDiscDrive)

Sysprep


https://docs.microsoft.com/en-us/win...top/sysprep--g
eneralize--a-windows-installation


Â*Â* "To deploy a Windows image to different PCs, you have to first
Â*Â*Â* generalize the image to remove computer-specific information
Â*Â*Â* such as installed drivers and the computer security identifier (SID).

Â*Â*Â* You can either use Sysprep by itself or Sysprep with an unattend
Â*Â*Â* answer file to generalize your image and make it ready for
deployment."

The following was a Windows To Go example (no Sysprep, runs on same
machine).
The directory H: in this example, is a Macrium clone of C: with the
DiskID changed when the associated VHD is "attached" in Disk
Management.





With XP or Win7 that may be needed but I have never had a problem
transferring a Win10 HD to other hardware.



--- Internet Rex 2.31
* Origin: The gateway at Omicron Theta/2 (1:261/20.119)