History:
- I've just upgraded myself to a new custom build and want to give my kids my old custom build
- Old custom build worked just fine prior to my upgrade
- My kids have a year old Gateway store bought, and I wanted to just swap their hard drive over to the custom build (better CPU, GPU, MB, RAM..etc). This drive currently runs Win 10.
The drive from the Gateway machine will not boot to Win 10 in the custom build, but still boots just fine when I swap it back to the Gateway. The drive is detected in BIOS in the custom build, and I've tried swapping from IDE to AHCI and back just to rule that out.
When I boot the custom with their drive it gets through the BIOS info and memory count, but then just sits with the flashing cursor and never loads Win 10.
I have another drive with a corrupt copy of Win, and when I put that drive into the custom it gets passed BIOS and does try to load that bad copy of Win.
I really wanted to just bring their drive over as is so they still have access to all of their programs and files without having to format and reinstall.
Any thoughts on what may be going on? Certainly the Gateway has a different chipset and MB, but I thought that would not cause any issues and I could just update drivers once Win loaded. I was able to do this when swapping my old drive from the old custom build to the new without issues.
Thanks!
- I've just upgraded myself to a new custom build and want to give my kids my old custom build
- Old custom build worked just fine prior to my upgrade
- My kids have a year old Gateway store bought, and I wanted to just swap their hard drive over to the custom build (better CPU, GPU, MB, RAM..etc). This drive currently runs Win 10.
The drive from the Gateway machine will not boot to Win 10 in the custom build, but still boots just fine when I swap it back to the Gateway. The drive is detected in BIOS in the custom build, and I've tried swapping from IDE to AHCI and back just to rule that out.
When I boot the custom with their drive it gets through the BIOS info and memory count, but then just sits with the flashing cursor and never loads Win 10.
I have another drive with a corrupt copy of Win, and when I put that drive into the custom it gets passed BIOS and does try to load that bad copy of Win.
I really wanted to just bring their drive over as is so they still have access to all of their programs and files without having to format and reinstall.
Any thoughts on what may be going on? Certainly the Gateway has a different chipset and MB, but I thought that would not cause any issues and I could just update drivers once Win loaded. I was able to do this when swapping my old drive from the old custom build to the new without issues.
Thanks!
Facebook
Twitter
Instagram