Swapping mobo and cpu. Will Windows / Microsoft like it or complain?

[ZaphodB]

Hi,

Currently an issue with a 15 year-old Dell Vostro 200 Destop (the subject of this thread)

It has

• Foxconn G33M02 Mobo
• E4400 Core 2 Duo 2GHz CPU
• 4Gb DDR2 RAM
• 450W Corsair PSU

I've tried everything I can think of to fix the issue I have (refer to above thread if interested in the background) and have now purchased another (working) G33M02 mainboard which has

• E6600 Core 2 3.06GHz CPU
• 3Gb DDR2 RAM
• Same 45w Corsair PSU (obviously)

My question is this.

Is this going to be a simple swap-out (or may there be driver issues)? As the board is already working with the 3Gb RAM, that shouldn't be an issue.

Will Windows suddenly decide that it is in a new pc and tell me that it isn't a valid installation (and if it is, how do I tell M$ that the mainboard and CPU have been replaced?)

Do I simply umplug (taking careful note of what goes where and which way round) the cables, remove the old board, pop the new one in, re-cable and it should boot fine? I'm guessing that it won't be that simple!

Any hints / tips / tricks / observations welcome.

If this works and sorts out the original (static drain) issue, I'll pop Win 7 on a small SSD to act as the system disk and use the existing physical disk as the data storage.

Thoughts?

Zaph

 

[torchwood]

Hi

BIG can of worms here!!!!! purely from an activation point of view
bear with me, so many different options, definately gunna need to know a few things

Unfortunately MS will designate it as a NEW machine.....
major component change

However if the new MB was an "original" Dell board you MIGHT get lucky
(is the BIOS on the new board up to date????)

from what i can find, that comp came with Vista
please confirm and if so how did you move upto W7 OLD BOARD
(the "new" motherboard could still be holding Vista/W7 or even W10 activation details)

i did look at the other thread definately a hardware problem

TO answer your question it WILL require the installation of the NEW motherboard
then i will need to see the results of this tool

https://www.sevenforums.com/attachm...vation-issue-posting-instructions-mgadiag.exe

IF you run the W10 upgrade on your >current< setup you will be able to get a free >>W10<< licence
note MS are currently rather lax in regard to this licence and even changing the MB/CPU has been known to be acceptable (go figure!!!)

 

[Alejandro85]

Will Windows suddenly decide that it is in a new pc and tell me that it isn't a valid installation (and if it is, how do I tell M$ that the mainboard and CPU have been replaced?)

For every practical effect this IS a new computer. You've replaced the motherboard and CPU, the central components while retaining the data and other minor parts, it's not much different from extracting the hard disk from one computer and putting into another.

My only suggestion in those cases is: don't try the same Windows install there. Just do a clean install and avoid the inevitable driver and compatibility problems.

 

[torchwood]

NOT neccessary true, read my comments #3 and #4
and whether a COA is available to use, in this case the cpu is not designated as new

 

[ZaphodB]

Thanks folks

Okay to try to answer the questions.

The original mobo is as supplied by Dell. PC, as you say, came with Vista.

The W7 installation was a fresh, new one (I have the CoA) and was put onto a freshly-wiped HDD.

The BIOS on the new board is (accoring to the pix) 1.0.16 which, as far as I can tell, is the latest BIOS for that machine and dates from 2008.
torchwood Are you saying to run MGADiag after installing the new mainboard??

Basic thing here is that the pc needs to boot into Windows (are you assuming it will) in order to run the exe file - or to run it before?

Zaph

 

[torchwood]

Hi

It does appear that the new motherboard, based on Bios date, was also Vista era
I dont think this is going to cause any problem setup and driver wise

I DO need to know how that COA key is labelled , the Mga tool will give me the answers, but if you tell me now can all the better
(DONT post the key just the description

The tool will need to be run on the new motherboard

 

[ZaphodB]

Hi

It does appear that the new motherboard, based on Bios date, was also Vista era
I dont think this is going to cause any problem setup and driver wise

I DO need to know how that COA key is labelled , the Mga tool will give me the answers, but if you tell me now can all the better
(DONT post the key just the description

The tool will need to be run on the new motherboard

Not sure I understand what you mean here.

I've run the MGA and get several tabs with info. The most likely seems the Windows tab.

I have:

• Product Key
• Product Key Hash
• Product ID
• Product ID Type
• Windows OS Version
• ID
• Administrator
• TestCab
• LegitcheckControl
• Signed by
• Product Name
• Architecture & Build.

and a Licensing tab with lots of info.
On this tab under 'Description' it says Windows(R) 7, OEM_COA_SLP channel.

Is this what you were after?

Zaph

 

[torchwood]

copy/paste it please then i can see whates going on

 

[Megahertz07]

Run the MGADiag. On the first screen (Windows tab) hit the "Copy" button.
Paste it here.

 

[ZaphodB]

Here you go:



A thought.

Just wondering if I could use Macrium Reflect to clone the existing (and validated) Win 7 OS and installed programs onto a new HDD (if, of course, the existing HDD/OS actually works with the new mobo/cpu combo).

I guess first we have to see if the new mobo/cpu will play nicely with the existing OS installation!

Zaph

 

[torchwood]

Hi

I really need to see ALL of the report ---- DO NOT REDACT anything this time

from the little i can see the product key in use is from a W7 OEM computer,
not an upgrade/retail or system builder key

 

[Megahertz07]

Hi

I really need to see ALL of the report ---- DO NOT REDACT anything this time

from the little i can see the product key in use is from a W7 OEM computer,
not an upgrade/retail or system builder key

Run the MGADiag. On the first screen (Windows tab) hit the "Copy" button.
Paste it here.

On the first screen (Windows tab) hit the "Copy" button.
Paste it here

 

[torchwood]

Its not the 1st time he's NOT posted the complete report.....

 

[ZaphodB]

Its not the 1st time he's NOT posted the complete report....

I'm puzzled.

In this post (#6 this thread) you said:

Hi

It does appear that the new motherboard, based on Bios date, was also Vista era
I dont think this is going to cause any problem setup and driver wise

I DO need to know how that COA key is labelled , the Mga tool will give me the answers, but if you tell me now can all the better
(DONT post the key just the description

The tool will need to be run on the new motherboard

So I post what you asked (I redacted the key and key hash) yet you seem annoyed.

FWIW, here is the full screen (!)




Zaph

 

[torchwood]

i meant to whole product key........

and NO you havn't posted the complete output from the tool...... i need all of it to give you the correct information so you can go forward

 

[ZaphodB]

i meant to whole product key........

and NO you havn't posted the complete output from the tool...... i need all of it to give you the correct information so you can go forward

Ahh... sorry

I thought you just wanted the first screen.

MGA Tool says


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


Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-MQH9P-TWP6V-7TF9K
Windows Product Key Hash: 2YscZqXxDxQcDaZuEC2bkd2hdkk=
Windows Product ID: 00359-OEM-9828645-72715
Windows Product ID Type: 8
Windows License Type: COA SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {44FB2856-D8F0-4BAC-A7BD-F7FC30B5188E}(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: 7601.win7sp1_ldr_escrow.190220-1800
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: 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\Google\Chrome\Application\chrome.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>{44FB2856-D8F0-4BAC-A7BD-F7FC30B5188E}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-7TF9K</PKey><PID>00359-OEM-9828645-72715</PID><PIDType>8</PIDType><SID>S-1-5-21-3659428073-1941274565-2760938267</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Vostro 200</Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>1.0.3</Version><SMBIOSVersion major="2" minor="5"/><Date>20070712000000.000000+000</Date></BIOS><HWID>04203C07018400FA</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL </OEMID><OEMTableID>FX09 </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.7601.17514


Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_COA_SLP channel
Activation ID: 5e017a8a-f3f9-4167-b1bd-ba3e236a4d8f
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00196-286-472715-02-2057-7600.0000-2672021
Installation ID: 007445550986803180727405206825327401858250052603008931
Processor Certificate URL: Runtime Error
Machine Certificate URL: Runtime Error
Use License URL: Runtime Error
Product Key Certificate URL: Runtime Error
Partial Product Key: 7TF9K
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 24/03/2022 17:12:31


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: MgAAAAEABAABAAEAAAABAAAAAgABAAEA6GHgW5gkZP7mcoj9YCGs2+YPri4MsAxtKoU=


OEM Activation 1.0 Data-->
N/A


OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x0
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC DELL FX09
FACP DELL FX09
HPET DELL FX09
MCFG DELL FX09
SLIC DELL FX09
DMY2 DELL FX09
SSDT PmRef CpuPm


Zaph

(thanks for your patience btw)

 

[torchwood]

Hi

As i thought,,, the key in use has been "lifted" from another W7 machine.
Although its licenced its not fully activated, it needs tobe registered on the MS servers
this is shown by a number of exceptions
File Mismatches
Runtime errors
Admin service not registered

the system was last (re)installed from about September last year, does it have kb3138612 installed??
if not please install it and then run SLUI4 from a command prompt

REBOOT x2 and then rerun the tool again---- status may change, post new log

The install media used is non standard, im not saying it contains any modifications, but appears to be a business SysPrep version...... It had 5 re-arm options and i see that you have actually had to use 1 allready
(guessing another is due anytime.. based on the install date and rearm timeframe)

This 2007 Vista board does not have the correct SLIC table entries. to be expected, or Upgrade key indicator

Based on the above i believe MS will turn your system Non-genuine in about 4/5 months
UNLESS the KB and SLUI activation work.... no guarentee even then

 

[ZaphodB]

Hi again Torchwood.

Many thanks for your patience & replies.

A few questions if I may.

1) KB3138612 relates to the Windows Update Client. Why do I need to run this seeing as Win 7 doesn't get any more updates from Microsoft. Can you please explain?

I don't know if I have this installed, I'll have to examin the Windows Update Cache on the pc.

2) What does the SLUI4 command do? As far as I can tell it is linked to Windows Activation.

3) What is re-arm? I'm guessing the first use was the orginal installation?

What happens if the re-arm hits zero?

4) When this s/ware was installed last year I had to ring the Activation Line and I got a sequence of numbers back to input into the pc.

The SLUI4 command tries to activate the windows installation automatically?

Cheers

Zaph

 

[torchwood]

Hi

All 4 of your questions DO relate to Activation.....

1)
the old way to correct those errors was to install KB971033.. but MS has pulled it from the catalogue
(you can ignore all the posts saying it caused more problems than it worth.. mostly rubbish apart from KMS.. not yours)
the KB i asked you to install updates the User Agent.. and sometimes corrects it
2)
SLUI4 takes you to the MS servers and tries to Register it directly
3)
slmgr /rearm is a means to extend the grace period of an install if either a correct key is not present or deemed un-acceptable by MS for whatever reason
ONCE rearm hits 0 then you have 30 days left before the OS turns Non-genuine
initial installation of the OS does NOT reduce it by 1... Thats why i made the comment in previous post
(it was originally included for developers to test thier programs on)
4)
the key, Unique ID as they call it, provided by MS should be the 1 in use and NOT the key on the COA label you have
WHICH IS on your system COA or MS
The UID should have performed BOTH requirements immediately - how many characters in yours note i have one

 

[ZaphodB]

Hi

4)
the key, Unique ID as they call it, provided by MS should be the 1 in use and NOT the key on the COA label you have
WHICH IS on your system COA or MS
The UID should have performed BOTH requirements immediately - * how many characters in yours note i have one *

Hi again,

I'm sorry but I don't understand what you are asking me here (highlighted) and have no idea what you mean (bit in red). [for some reason bold highlighting isn't showing!)

Can you explain please?

Cheers

Zaph