Boot code 0x490 after moving hard drive to a new laptop

My laptop died Friday morning and I took the hard drive out and installed it into a backup laptop. Dead laptop = asus 555l and new laptop = dell lattitude e5510. Was able to boot into safe mode enough times to get all the drivers updated but then the dell got into a repair loop at the startup repair utility bailing with a 0x490 error code every time the unit booted. Was able to get back to a cmd prompt where I ran bootrec with the /fixmbr and /fixboot options then rebuilt the boot table with bcdedit. Still no luck. Here are my boot settings from the bcdedit dump. Any help would be appreciated. Thanks.


Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {959c9d43-5cae-11e5-b845-b567baaa0d7d}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {959c9d45-5cae-11e5-b845-b567baaa0d7d}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {959c9d43-5cae-11e5-b845-b567baaa0d7d}
nx OptIn

Windows Boot Loader
-------------------
identifier {959c9d45-5cae-11e5-b845-b567baaa0d7d}
device ramdisk=[C:]\Recovery\959c9d45-5cae-11e5-b845-b567baaa0d7d\Winre.wim,{959c9d46-5cae-11e5-b845-b567baaa0d7d}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\959c9d45-5cae-11e5-b845-b567baaa0d7d\Winre.wim,{959c9d46-5cae-11e5-b845-b567baaa0d7d}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {959c9d43-5cae-11e5-b845-b567baaa0d7d}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume1
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {959c9d46-5cae-11e5-b845-b567baaa0d7d}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\959c9d45-5cae-11e5-b845-b567baaa0d7d\boot.sdi

It is an oem version that I purchased. The asus computer had win10 and I wiped it with the oem win 7. I did use it to install a ssd drive on the dell to backup the hard drive the other night and it didn't complain then but I haven't used it and then I swapped the ssd for the old laptop drive.

For my issue though, I just ran bootsect /nt60 SYS /force /mbr on the system I've having a problem with with no success. Is there anything that looks incorrect in the file I posted above? Thanks.

The dell originally had win7 on it but the hard drive was removed so it makes no difference. I had run the Asus with the oem win7 on it for a year with no issues until the system board died so I do not believe overwriting 10 with 7 was an issue. Now serialization to the system board certainly might be. Once upon a time a user could take a copy of windows or any other software and run it on one machine at a time and it was deemed acceptable and I still observe that practice whether redmond likes it or not. I'm not going to pay to run a piece of software until the hardware that it runs on dies. That is a ridiculous concept and Microsoft can go shove it if that is indeed what they are asking their customers to do..

Dell - originally win7 but had hard drive removed. Installed new ssd with the oem copy of windows to make some backups, then removed the ssd drive.

Asus - originally win10. Reinstalled win7 over it one year ago and ran fine for that year. Took hard drive and reinstalled into the dell, updated drivers in safe mode to a functional state, but now having the boot issue.

The data that I have posted is from the dell machine with the newly installed drive from the dead asus. Thanks.

Clearly I purchased the wrong one then. Not that it matters. I only have one application that requires windows and I'm pretty close to getting that working under virtualbox on a real operating system so I can say good bye to Microsoft once and for all.

For this particular issue though, I ended up just reinstalling my apps on the ssd drive as it was the shortest path to getting back up and running. It should not take hours to perform a trivial task such as installing a boot sector/mbr or figure out why it does not work. One of the many reasons why I am abandoning MS.

Good luck Microsoft users. You always need it.