Jump to content

Moving Windows 10 from one mobo/CPU to another

HunterAP
Go to solution Solved by HunterAP,

So I wanted to report on my experience with my situation:
The system in question was originally using a Z170 mobo and an i7-6700K. Windows 10 Pro was installed on that system directly, and the key was used on it when it was built. The new system is an X470 mobo with an R7 2700X. Initially, there were some driver issues (such as my GTX 1080 having lots of drivers crashes, which were fixed after using DDU in Safe Mode and then installing the newest drivers manually). Other things that needed to be fixed were the removal of old drivers from the previous board (Intel HAXM, any mention of the 6700K in Device Manager -> Processors, etc), and running an "SFC /scannow" in an admin console to make sure Windows was working properly. Any other issue I've had was due to CPU and memory overclocking, and it seems that I now have 0 issues to speak of.

 

"Re-activation" was super easy: I signed into my MS account as normal on boot, then Windows prompted me to confirm that I did indeed move my drive to a new system, and that was it.

 

Thank you all for the answers that helped me decide not to do a complete clean reinstall of Win 10, it saved me hours of problems and all I really needed to do was some manual cleaning post-switch.

I'm upgrading my PC by replacing the mobo and CPU on a Windows 10 Pro machine with newer parts, but I'm concerned about how Window 10 Pro gets transferred over to a new mobo. The SSD that W10 Pro is installed onto is going into the new system, and from I've seen it supposedly doesn't matter as long as it wasn't an OEM key. Is this true?

 

For another W10 system, I am reusing the machine but changing the OS drive from an HDD to an SSD without using a migration tool by doing a completely fresh install of W10. This 2nd machine is a prebuilt that came with Windows 7 but was upgraded to Windows 10. Is there anything I have to do for this machine to reuse the current key?

Link to comment
Share on other sites

Link to post
Share on other sites

When I moved my system over I just powered it up and Windows detected the hardware change, had me sign into my Microsoft account, and churned for a bit while it setup the new stuff and then I was good to go.

Current Network Layout:

Current Build Log/PC:

Prior Build Log/PC:

Link to comment
Share on other sites

Link to post
Share on other sites

I believe if it isn't an OEM key it should be fine.

Though, I got my OEM key to run on another computer. It refused to boot correctly at first, but I entered safe mode, and the booted normally.

It runs fine to this day.

I think Windows 7 upgrade to 10's are only meant to work on the same machine, and have heard of issues trying to move it, especially because the key is weird. Though you could still get it to work.

Long story short, results may vary..

Try it and see what happens, assuming you have the parts already.

 

Desktop:

CPU: Ryzen 5 1600 @3.75* RAM: 2 by 8gb G.Skill Flare X 2400 @2666* GPU Strix GTX 1070 @1880-ish

Storage: Samsung 860 Evo 500gb; 2x 2tb Seagate Barracuda Drives; 1tb hdd (It died after 4 years :();

 

Laptop: (HP Stream 11-y010nr "Spent all my money on my Desktop" Edition)

CPU: Intel Celeron N3060 @160 BILLION hertz RAM: 400 BILLION bytes Samsung DDR3L @160 BILLION hertz 

GPUIntel HIGH DEFINITION Graphics @32 BILLION hertz

Storage: 32 TRILLION bytes of SOLID STATE emmc C drive with 64 TRILLION bytes of SOLID STATE microSD card D drive.

 

*Overclocked around 25% of the time... questionably stable.

Link to comment
Share on other sites

Link to post
Share on other sites

14 hours ago, Linker said:

I believe if it isn't an OEM key it should be fine.

Though, I got my OEM key to run on another computer. It refused to boot correctly at first, but I entered safe mode, and the booted normally.

It runs fine to this day.

I think Windows 7 upgrade to 10's are only meant to work on the same machine, and have heard of issues trying to move it, especially because the key is weird. Though you could still get it to work.

Long story short, results may vary..

Try it and see what happens, assuming you have the parts already.

 

Its not about how upgrade was made. It IS about what key it is. Because keys activate in different ways. With Win10 if key is connected to MS account -> no issues. If its retail -> no issues. If its Win7(8(.1 retail -> no issues. If its non-branded Win7 OEM -> should be no issues, though I haven't changed mobo after moving to Win10. If its branded WIn7 OEM or Win8/.1 OEM -> issues.

^^^^ That's my post ^^^^
<-- This is me --- That's your scrollbar -->
vvvv Who's there? vvvv

Link to comment
Share on other sites

Link to post
Share on other sites

So I wanted to report on my experience with my situation:
The system in question was originally using a Z170 mobo and an i7-6700K. Windows 10 Pro was installed on that system directly, and the key was used on it when it was built. The new system is an X470 mobo with an R7 2700X. Initially, there were some driver issues (such as my GTX 1080 having lots of drivers crashes, which were fixed after using DDU in Safe Mode and then installing the newest drivers manually). Other things that needed to be fixed were the removal of old drivers from the previous board (Intel HAXM, any mention of the 6700K in Device Manager -> Processors, etc), and running an "SFC /scannow" in an admin console to make sure Windows was working properly. Any other issue I've had was due to CPU and memory overclocking, and it seems that I now have 0 issues to speak of.

 

"Re-activation" was super easy: I signed into my MS account as normal on boot, then Windows prompted me to confirm that I did indeed move my drive to a new system, and that was it.

 

Thank you all for the answers that helped me decide not to do a complete clean reinstall of Win 10, it saved me hours of problems and all I really needed to do was some manual cleaning post-switch.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×