Solved Transferring hard drive between laptops, will re-install OS work?

[lolpsy]

Hello,

I am attempting to transfer the Hard drive from my old Asus laptop to my Sony, due to my failing hard drive.

The system boots properly for the most part aside from some minor driver issues, but the windows version is not considered genuine because of the hardware difference of course.

I was wondering if I would be able to:

Use the re-install function to re-fresh my windows but instead of using the Key activated on the Asus drive (which will receive the re-install), I want to use the key from my old Sony drive (which will match the hardware spec's).

would this be possible?

OR

should I just make system image/repair discs from the Sony drive and use them on the Asus drive?

Thanks in advance.

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 50
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-2QWT6-HCQXJ-9YQTR
Windows Product Key Hash: PVjSC5x6njvqunmbCY3lOD7rYDo=
Windows Product ID: 00359-OEM-8992687-00007
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7600.2.00010300.0.0.003
ID: {AFC60448-FBEF-4AE9-AEB5-53EF64AE7334}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7600.win7_gdr.100618-1621
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: B4D0AA8B-604-645_B4D0AA8B-604-645_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->
File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003]
File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003]

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{AFC60448-FBEF-4AE9-AEB5-53EF64AE7334}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-9YQTR</PKey><PID>00359-OEM-8992687-00007</PID><PIDType>2</PIDType><SID>S-1-5-21-877714752-2884639147-1695858663</SID><SYSTEM><Manufacturer>Sony Corporation</Manufacturer><Model>VGN-NW250D</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>R1120Y4</Version><SMBIOSVersion major="2" minor="4"/><Date>20090820000000.000000+000</Date></BIOS><HWID>62BA3607018400F8</HWID><UserLCID>1009</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Mountain Standard Time(GMT-07:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>Sony</OEMID><OEMTableID>VAIO</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7600.16385

Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00178-926-800007-02-1033-7600.0000-2092009
Installation ID: 095761429886733291225201448791399130460564142912300703
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: 9YQTR
License Status: Notification
Notification Reason: 0xC004F032.
Remaining Windows rearm count: 2
Trusted time: 22/04/2013 10:55:31 PM

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Not Registered - 0x80040154
Admin Service: Not Registered - 0x80040154
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: MAAAAAEAAQABAAEAAAACAAAAAwABAAEA6GHGFKgDMsGEqnxYcMzOR+Ks5in8CUbK

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information: 
  ACPI Table Name    OEMID Value    OEMTableID Value
  APIC            Sony        VAIO
  FACP            Sony        VAIO
  HPET            Sony        VAIO
  MCFG            Sony        VAIO
  SLIC            Sony        VAIO
  SSDT            Sony        VAIO
  SSDT            Sony        VAIO

 

[NoelDP]

You should be able simply to change the Key to the one on your Sony COA sticker and activate that.


You need to change the Product Key to the one on the COA sticker on the machine's case (or inside the battery compartment), using the Change Product Key link at the bottom of the System properties page.

You may need to activate by phone.

 

[lolpsy]

Thank you,

I was wondering if that would work, but I didn't want to Jeapordize the good key from my Sony.

My other issues are that all the hardware drivers and software that are in the ASUS drive for things ATK0100 (power and hotkey settings), are going to be of no use on the sony hardware, and the fact that the system has identified itself as an ASUS system in Computer info.

I suppose though, if I was able to use the key on the new hard drive regardless, that creating a system image and repair disc would allow me to shuffle all of the hardware drivers and system identity info for the Sony machine while getting rid of all the irrelevant ASUS software.

 

[Mark Phelps]

If you want to try it, Macrium Reflect (as does, I believe, EASUS and Paragon) makes a product that allows you to "migrate" an installation to different hardware. The way it works is as follows:
1) Restore the image made from the old hardware to the new hardware
2) Boot from the MR CD containing this option, and run this option
3) Point to the directory containing the drivers needed for the new hardware
4) Automatically removes all the old drivers, replacing them with the drivers needed for the new hardware
5) Remove the MR CD and reboot --NOW you're running with the new drivers.

I've successfully done this, so I know it works.

 

[theog]

How to clone your old drive to a new drive.
Solved How to Migrate OS to new Hard disk.

 

[lolpsy]

If you want to try it, Macrium Reflect (as does, I believe, EASUS and Paragon) makes a product that allows you to "migrate" an installation to different hardware. The way it works is as follows:
1) Restore the image made from the old hardware to the new hardware
2) Boot from the MR CD containing this option, and run this option
3) Point to the directory containing the drivers needed for the new hardware
4) Automatically removes all the old drivers, replacing them with the drivers needed for the new hardware
5) Remove the MR CD and reboot --NOW you're running with the new drivers.

I've successfully done this, so I know it works.

Thank you for the solution