Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Assuming the motherboard and BIOS will support it, can I change from a dual core processor to a quad core without Windows 7 giving me any grief?

share|improve this question

3 Answers 3

up vote 12 down vote accepted

Yes you can. As you say "Assuming the motherboard and bios are all ready to go" if this condition is OK, I mean, if your processor uses the same socket and a compatible chipset you could not only upgrade from a dual core to quad core but the other way as well, downgrading from quad core to a dual core processor.

share|improve this answer

For a cpu change there should be no problem, since there aren't any drivers involved (which Windows 7 would get from the internet anyway). Maybe it will ask you to re-activate... but that depends on what has changed, not only now but in the past since your last activation.

share|improve this answer

Both dual core and quad core systems would very likely use the same SMP kernel, and be unlikely to give you trouble due to that. If you wish to play it safe, you may want to run sysprep /generalize to make it a generic, non specialized system before you do the processor swap.

Other issues such as activation may still need to be taken care of, but this should allow the system to be bootable without driver incompatibilities.

share|improve this answer
6  
+1 Good point "sysprep /generalyze" –  Diogo Jun 1 '12 at 14:42
    
i like this answer –  RawR Crew Jun 1 '12 at 15:35
    
sysprep is always a good idea, can save a lot of grief. –  WindowsEscapist Jun 1 '12 at 19:09
1  
Are you sure you want to run sysprep for a CPU change? This sounds like a horrible idea based on the documentation. I was under the assumption that having your SID reset is usually not desirable. –  Oliver Salzburg Jun 2 '12 at 0:31
3  
@OliverSalzburg Actually it turns out that machine SIDs are never exposed to the outside world on client computers; it's apparently totally okay to never change them. You still need unique machine SIDs on your domain controllers because that gets promoted to the domain SID, and the client's domain SID needs to be unique (e.g by having the clone re-join the domain), but the client's machine SID isn't ever exposed to the network. That's why SysInternals retired NewSID. –  Tacroy Jun 8 '12 at 22:59

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.