Considering a new PC might lead to driver complications.
Considering a new PC might lead to driver complications.
Hi everyone, I might have asked this question a while back, but it seems the discussion hasn't really come to a close. My current setup uses an i9-10900k and an RTX 3090. I've been checking PCPartpicker for a potential upgrade because the 10900k is starting to lag, and I just want a fresh PC. I was thinking about going with AMD for this round, targeting a 9 800X3D. I plan to keep the same storage drives and boot drive, just swapping out the motherboard, CPU, RAM, and eventually the GPU when the RTX 50-series arrives. Could I run into issues with motherboard or chipset drivers during the first boot, like Intel trying to find an Intel chip but failing? Thanks, Rhys
Apologies for repeating your statement, but I understand. Based on what you described, running the system with the 10900k and its motherboard using sysprep.exe seems to be the correct approach. Should I avoid starting it again with the 10900k unless necessary, to prevent automatic driver reinstallation? It might be wise to search for and uninstall drivers before proceeding with the setup. Let me know if you need further guidance.
Sysprep > Generalize, enter OOBE. Shut down, swap hardware, power back up, install drivers, rock and roll. It's safe to look for driver installers ahead of time. No worries about removing drivers—sysprep will handle that.
I’m preparing a comparable upgrade from your i9-9900K to a Ryzen 9900X. I’m aware of the trade-offs—while X3D chips offer better performance for gaming, they’re beyond my budget. The Ryzen 9900X is the next best option. I’ve had worries about drivers and file safety, but I want to confirm if a new Windows key is required. It seems the key is tied to the motherboard, so even with a new GPU you’d need a replacement key.
Currently, the Windows activation is more connected to your Microsoft account than the hardware itself. As long as your installation stays tied to the same account, reactivation should work smoothly. I've tested this with several system changes using the same license key and haven't faced any issues.
Previously, it seemed like a mix of two systems. I logged in with a Microsoft account on an old laptop, then reinstalled Windows using just a local account (without the Microsoft account). When I handed over the laptop to my partner, Windows didn<|pad|>'s stay active, indicating it's linked to the hardware rather than just an account.