I keep on reading the horrific experiences over in tenforums, where either the upgrade install or the clean install post-update, bombs, hangs, or trashes the machine. At this point, there are maybe 200 such reports, and that means thousands more unreported problems, are occurring. We've seen some here, as well.
As Insiders, we had generally pleasant installations (though my initial experience with build 10130 was straight from Hades) -- so why is that? What's the essential difference between our experience, and 'theirs'?
THE LICENSE KEY WAS NOT AN ISSUE.
But of course it is and should be an issue, in the real upgrade installations of real and official, Win10. So perhaps the license key sleuthing in the installer, is misprogrammed? To wit:
1. Johnny's COA on his machine was originally Vista but he upgraded it to Win7, with a valid Win7 upgrade. But the installer, is programmed to look at the mobo for the key, and it's Vista. So the installer silently bombs or goes into a hang, because it also finds Win7 with SP1 on there, active, but doesn't find the key so doesn't know what to do. Johnny, of course, gets no feedback but rather spends his day mystified and angry.
2. Jane's COA on her machine is Win7 with SP1 but is 32-bit, and her brother changed it to 64-bit with an OEM System Builder, but again since the license key doesn't match, the Win10 installer doesn't know what to do, but goes farther since both are Win7.. and then bombs in some other way. Maybe saying 'Installation Failed' or 'Something went wrong'. So clearly the installer's programmer didn't want to clarify the problem is a licensing conflict.
3. brainout's COA on her machine is Windows 7, but brainout used a clean disk to install a brand new retail 8.0; its own key was not accepted to activate; yet that was magically fixed remotely by MSFT when she called MSFT post-install, to activate it. Then, brainout updated to 8.1 via the Windows Store, not being given a new key. So Win10 'saw' that 8.0 key when prompting brainout to type it in during build 10162 install: so now at 10240, Win10 is activated.
4. Fabio's COA is Windows 7 64-bit and so too his OS at the time of Win10 installation: same initial OS, same key, same everything except added Win7 updates and third-party programs. The Win10 installer has no problem finishing on his machine, because both COA and OS, match.
See the difference? The 'purpose' of the install bombing, might be to force a customer to call MSFT, so it can remotely verify the license key. But no one is told this, and of course not all license keys validly extant, are yet recorded by MSFT employees, who are frazzedly trying to finish that job.
Ergo, this topic: have you solved an install by calling in your key to activate? What kind of error was it you experienced prior, just in case there's a pattern here so another can say your experience resembles his?
If this is considered a stupid topic, please delete it. My heart just breaks for all those suffering over installation.
EDIT: someone sent me this great Forbes article on the tie-in between successful installation, and licenses: click here.
Edited by brainout, 30 July 2015 - 11:30 AM.