About Win10 on Early Intels: pitfalls and workarounds ...
During the last 4 weeks I was forced to update my office-machines from Win7 to Win10, since with the next quarterly update my bread&butter software will stop to support Win7 and WinServer2008.
I was happy, that I could "convert" 4 early-intel c2duo iMacs and an early-intel 2009 15" MBP into Win10pro machines at nearly no extra-costs (except from new SSD's).
There were Win7/9 licences from old PC-workstations, that were retired about 4-5y ago, when iMacs replaced them.
Now I'm on the way back from a TerminalClient-Server network (with Macs/RDP as ThinClients) back to a Win10Pro-FileServer with connected Win10pro workstations.
The learning-curve back to Win10 had been pretty steep for an old chap like me, but now I feel quite save to cope with the new challenge.
Unfortunately Windows10 is not OSX/macOS, when it comes to simply swapping system-drives between two machines as a quick solution, if hardware should ever fail or if it is because of just out of a mood.
Installing Win10 is kind of a marriage, a bond for life - at least, if you've started installation with an OEM-version and took the free Win10-update-path.
"Therefore, examine whoever binds forever, Whether the heart finds its way to the heart. The madness is short, the regret is long" (Schiller).
So for any case of major changes in hardware it's advisable to have your Win10-installation/Mac combined/registered with an Outlook/MS-account, which should preserve your digital licence.
I took this serious - except for one "other" machine: a mid2012 15" MBP with two drives (one as a replacement for the defective optical drive. Caddy came for less than 10 bucks) - one for Mojave, the other for Win10Pro.
Went through the whole Win7=>Win10Update process. BootCamp-Driver installation. Updates. Installation of all essential software. The whole (really awkward) configuration-settings, etc. But I forgot to match the MacBook with my Outlook-account.
And then I was uncautious and tried to boot the "BootCamp"-Win10 within macOS/VMwareFusion ... "Dang!" Major changes in hardware-configuration detected. Licence expired! Even after I went back and booted directly into Win10 there's was no chance to revive the licence with the credentials, I got from ShowKeyPlus-App. Telephone-support just told me, there's no support for Win7/8-OEM-versions that are updated to Win10 beyond the hardware, it had been initially installed on.
Only suggestion from telephone support: to buy a Win10Pro reg-code from MS (but I wasn't in the mood for it...)
So I repeated installation Win7/8=>10, which fortunately proofed to be working.
Now all Win10-Macs are registered with my Outlook-account and I have a bootable clone-copy of that specific Win10-drive (made with a bootable version of PartitionWizard9Free).
But I don't know, what happens, if I move the Win10-drive into another Mac or what happens, if I try VMware on the Win10-partition again.
Win10 is amazingly slick and fast on old SSD-attached C2Duo Mac-hardware!
Configuration is really laborious. Licence-management is a hassle.
Guess, which one has better performance and workflow: the early2008-c2duo MBP or the mid2011-i5 ASUS book?