I'm currently using an ASUS laptop + SSD + Windows 10. I cloned my SSD to another SSD to run it on another similar ASUS laptop, so I don't have "downtime" while I take apart my current laptop for maintenance and thermal paste replacement, and then do a clean install of Windows and all programs. The problem is, Windows did not recognize the hardware change, so it didn't do the usual "getting devices ready" it usually does during the spinning dots, so it simply tries to boot a couple of times, crashes with BSOD, fails to repair, rinse and repeat. Is there anyway to force Windows 10 to detect/install new hardware on boot, during the spinning dots? NOTE: in case someone noticed, I placed the exact same question at the SuperUser pages. If someone posts a solution there, I'll copy the solution over here.
I didn't consider that because it would imply opening my current laptop, booting with the replacement SSD, running sysprep and then moving it to the other laptop. I thought there could be a tweak that could be applied offline that would force it to enter hardware detection mode.
It seems not as you have BSOD and other troubles, hardware difference is too important and can't be resolved as is for Windows. I always use a basic image of Windows uptodate with some progs and never get any problems by installing it on different machines. It is just an advice to avoid problems.
... and once again Windows does whatever it wants, whenever it wants. Step 1 - clone original SDD to an external USB SSD using Macrium Reflect Free Step 2 - insert SSD into the second laptop and boot Step 3 - boot, reboot, try to unsuccessfully repair Step 4 - rinse and repeat Step 3, until I get a "no bootable device". Yup, partitions were gone! Step 5 - repeat Step 1 (AGAIN!), no reboot in between, same programs running and Windows open as first time Step 6 - insert SSD into the second laptop and boot (AGAIN!) Step 7 - this time, Windows decided to show "getting devices ready" after the 1st failed boot attempt. Step 8 - wait 30 minutes for the (slow) Welcome screen, then install missing drivers Should I blame the cloning software? The 2nd SSD (Kingston)? Windows 10 v1709/b16299? Whatever. After I'm done cleaning the laptop, I'm downgrading to Windows 8.1 until I get a new laptop, or at least one built for Windows 10. I only use it for work, so I don't have any need for DirectX 12, Apps or whatever Windows 10 brings to the table anyway.
I only use cloning softwares from exactly same machine to exactly same machine in that case you can use a different HDD or SSD. What are both laptops version ?
They're different models (N61J with core i3 vs K50ID with core duo) but very similar in hardware, with same ports, altec SRS speakers, intel/NVidia switchable graphics (GT320 1GB vs GT325 1GB), and memory modules are the same type, but mine has 2x4GB and the other one 2x2GB. I once had problems with one of them (not sure what but solved since) and moved the RAM, SSD and HDD in DVD caddy to the other one, Windows simply did what was supposed to do: detected the new hardware on boot with the "getting devices ready" message, booted into the desktop and activated successfully since both laptops had already been upgraded to Windows 10. This time it simply decided not to... until it did. EDIT: laptop is on 22h/day, SSD 128GB power on time of 2016 days / 5.5 years and 29.17TB written, and STILL reports good condition. Samsung EVO rocks
Remember when cloning a HD both asus laptops must be identical in HW specs u mention similar so u mite have a conflict with HW drivers and is causing the crash, i would just do a manual clean install on the second machine.
Usually, when windows bluescreens after changing the hardware it's because it can't detect the boot device because of wrong SATA drivers or mode (INACESSIBLE_BOOT_DEVICE bluescreen) For example, if you installed windows on IDE mode, and your new system is in AHCI, you will have that problem. Solutions: - wait for windows recovery options to show up after it bluescreens and boot in safe mode. Most of the times it works and then you just need to reboot into normal mode. - try to change IDE to AHCI or RAID or whatever mode you had on the other laptop and try again.
