Moved SSD from one laptop to another laptop Startup Repair did not fix

[BruceWayne]

Hello all
Windows 7 Pro 64bit Retail version was installed on a Dell M4300 on a Samsung SSD and worked flawless. I sold the Dell and kept the SSD. I had iTunes on the SSD and synced to my iPhone with music and pictures.

I tried to boot the Win 7 Pro SSD build on a Lenovo T430 and it won't boot. I tried the Win 7 DVD to repair it with no luck yet. The Diagnosis and repair details: are very long and I can't copy and paste it. So this is just a few lines.
Boot status indicates that the OS booted successfully.
------
------
Session details
System Disk = \Device\Harddisk0
Windows directory = C\Windows
AutoChk Run = 0
Number of root causes = 1
------------
A patch is preventing the system from starting.

Repair action: System files integrity check and repair
Result: Failed. Error code = 0x490
-----------------

I typed diskpart, then list disk, and Disk 0 and Disk 1 are displayed. Disk 1 is 22 GB and msata. Neither have an asterisk ( * ) to the left of "Disk x"

Any suggestions?

I don't want to resync my phone and all that associated stuff that is why I really really really want this SSD to boot.

TIA peoples!

 

[Thedoctor44]

If you get any BSODs can you please upload the files by following the www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

It looks like the SSD is damaged. Can you test it on another PC?

 

[Cybie257]

I know this is an old topic, but I'm hoping that others that search for this same thing, they can see that there is more to this problem. It's a Windows Copy protection reason. Microsoft wants FULL CONTROL of your system and your MONEY.

There is a BSOD failure when moving a hard drive to another computer solely for the fact that MS thinks that you should buy a new copy of Windows, or start from scratch (Not caring that you spent days/weeks/months/years customizing your system) in order to run their inferior software.

What is happening is that fact that Windows 'CHECKS' for hardware changes. In stead of allowing it to load, or loading basic drivers to load to get you running, MS Sends a BSOD in order to keep you from booting your legitimately (over)paid for software into another computer, accusing you of "Stealing" their OS. They don't seem to figure it out enough that sometimes hardware fails and you have to buy new. So, they have failed in providing a transfer method in retaining all your past hard work.

Linux, on other hand, can be created on a VM (using a dedicated drive), then loaded on the bare metal machine without issues. You can also install Linux on a USB stick, then load it into ANY computer that allows you to boot from USB.

This isn't a Linux/Windows bashing. This is a clear statement that Windows should be designed in order to allow for the exact same thing. Switching hardware/computers in the event your old computer dies.

There IS a workaround on this, it's just a lot fo work and hard to find. All you find are these posts that others ask you to upload the 'logs' so THEY can figure it out. They will NOT figure it out. it is a system check, too much hardware change failure that MS purposely injected into the OS. You might also get this exact issue if you change out more the 3 pieces of hardware within a certain time period. It's all about a game of suspicion that you are copying illegally.

FACT : MS Knows and has stated in the past "Without the pirating of Windows 95, we would not be this successful".. Not exact words, but close. So, they rally need to quit making life a pain in the ass for users, whether they are legit or pirated copies. Disclaimer : This statement in mo means implies that I encourage copying software.