My Son has an iMac on which he was running Windows 7 Pro via bootcamp.
He wanted a clean install of Windows 10 Pro ...
Installed the upgrade all went well.
Made sure Windows was activated.
Grabbed keys using Magic Jelly (now know this was flawed ) just in case.
Started the revert process saying no to retain settings and format partition.
On Start up got BSOD with message Inaccessible Boot device ...
Obviously the boot sector on the windows partition got screwed up ...
Booted back to OSX, used bootcamp assistant to wipe the old partition, then create a new one and re-install from official iso (downloaded using my MSDN subscription).
Installed fine but would not active, message said key ending "3V66T" had been blacklisted grrrr, so much for auto re-activation. Maybe the "new" bootcamp had a different signature???
So had to use up one of my MSDN keys for him, no big deal for me, but a right pain in the ... for anyone without an MSDN subscription.
I have done a search for the key and I can confirm that the key ending "3V66T" seems to a generic key baked into the iso.
I upgraded then clean installed on my macbook air with not problem, when doing the clean install you shouldn't enter any serials and just skip/do this later at the prompts, then when the install completes it just recognizes the hardware and auto-activates.
Due to the huge amount of activity on the MS activation servers there have been quite a few reports of blacklisted keys on otherwise Ok installs, this has been blamed on issues at Microsoft's end due to the servers not being able to cope mayb give it a few days and try the old "blacklisted" key again
Are you using bootcamp to dual boot?I upgraded then clean installed on my macbook air with not problem, when doing the clean install you shouldn't enter any serials and just skip/do this later at the prompts, then when the install completes it just recognizes the hardware and auto-activates.
When we re-installed after BSOD, we changed to size of the partition, maybe this was enough to trip up the auto activation.
To be expected ...Due to the huge amount of activity on the MS activation servers there have been quite a few reports of blacklisted keys on otherwise Ok installs, this has been blamed on issues at Microsoft's end due to the servers not being able to cope mayb give it a few days and try the old "blacklisted" key again
Maybe better to wait till the dust settles to do clean installs.
Are you using bootcamp to dual boot?
When we re-installed after BSOD, we changed to size of the partition, maybe this was enough to trip up the auto activation.
Yep it was bootcamp on dual boot, after the upgrade I went into OSX and deleted the partition and then recreated (50/50 split) and reinstalled - everything went fine.
Same as we did, must have been due to load on activation servers.Yep it was bootcamp on dual boot, after the upgrade I went into OSX and deleted the partition and then recreated (50/50 split) and reinstalled - everything went fine.
Although we had 60/40 (OSX/Win) split before BSOD.
