What the ebay seller has probably sold you is an OEM key, which is typically what custom built or pre-built computers use. I know for a fact and through my own experience is that Microsoft's download page for Windows 7 doesn't recognise ANY OEM key, no matter if it's used or not. That being said, I'd still try the key with a fresh ISO from another source (the digitalriver mirror at mirror.corenoc.de/digitalrivercontent.net/ comes to mind - I've used it in the past with no problems) and if it doesn't work, then push for a refund / new key.
Aug 5, 2017 6:10:56 GMT
Last Edit: Aug 5, 2017 6:11:24 GMT by Deleted: spelling boiii
The issue here @drninkeo is i have used HP OEM serial numbers before on that web page to download the win7 ISO & win10 home too, i don't actually need the ISO file, i was simply checking that MS would validate the number through that web page.. which i have done twice so far without issues till this serial number.
Also note i haven't installed win7 pro yet, i was just getting what i hopped would be a genuine MS win7 DVD and serial before they disappear or become really really expensive... most web site already sell win7 for more than win10 right now.
Also for further info on this issue, i don't actually want to use win7 but don't you know, 3 previous win10 updates back was the first update that caused an issue with my video card driver because there is no specific win10 driver for it.
This caused my video to give me a black screen on reboot after the update.. i was able to fix that.
But 3 updates have passed since then, and my win10 computer has started to blue screen every day, 5 minutes after boot up.
I went to the the MS website, had 2 MS tech guys use remote logmein sessions to look / fix the issue with the results being NOTHING FIXED . i had to look at the maintenance and security widget to list the errors and error codes, then bing those to find out the blue screen error was with my video card driver.
That started the win7 process for me in case win10 couldnt be fixed.
I have since removed the add-on video card and solved my win10 blue screen issue..
Now it seems i'll need to buy a new video card that is win10 certified and has a specific win10 driver.
Yet again a win10 ( i assume ) update has screwed up my 3dsmax install.. it still runs but the pandasoft xfile exporter is some how causing models to be shrunk to a 10th the actual size, and because rigidbodies don't support resizing.. it's a problem.
I could reinstall 3dsmax, but i'm trying to avoid that.
Long story shorter...
I decided to install win7 pro in a dual boot with win10..
A number of stories i read online mostly were saying that installing win7 after win10 was a problem that may not even work and could mess up your win10 install.
During a new search this morning i find 1 and only 1 website that lists the steps to install win7 after win10 in a dual boot..
Can you guess the steps needed ??
Another webpage that mentioned a possible issue was the boot menu to select witch OS to boot up in mite not show up... one guy actual said you have to wipe your windows drives and reinstall both win7 first then win10 to avoid problems... are you F****** kidding me buddy.
The moderator stepped in and said if that happens, just install BCD bootcfg or some utility that will correct the issue. It does, i have used it before with a winxp & ubuntu dual booting system.
So anyway, the process to install win7 after win10, simply EXACTLY the same as installing any OS, on my HP computer anyway.
I decided to shrink the windows C: volume because its a 1T drive with 700G available using the windows disk utility, no problems worked fine.
Created my win7 .ISO DVD from a win7 pro image i downloaded from MS's website...
BOBS YOUR UNCLE, the install worked perfectly, rebooted like 5 times during the install, which is normal.
After the second reboot, the boot menu showed up as expected, no BCD bootcfg required.
One little issue popped up, i didn't download the win7 drivers for my HP hardware before i did the install...
This caused my USB keyboard to be ignored until win7 fully booted up..
The side effect of this was, i got locked out of win10 because win7 being installed after win10 was listed first on the boot menu, and because my keyboard wouldn't work or mouse, i couldn't select win10 to boot into ..
Started to panic just a bit, but then remembered i could change the boot order in win7 with the config utility...
Do you think i could remember what the name was... not in your life, i even did a directory list from a command prompt hopping i would see it and remember its name...
45 minutes in and i find a piece of paper on my desk with the config utility name, BINGO, it was msconfig ....
I was searching for winconfig or similar....... brain fart.......
Changed the order, rebooted and all's well i'm back into win10 with a working win7 in a dual boot config.
All that BS online about the problems is just laughable.... win7 or win10 first doesn't matter.
Interestingly, i see and remember a number of similarities with win7 and win10, but going back to win7 does take a little getting use to.
Plus it's a really good idea to have your win7 drivers already to be used BEFORE you install win7, if your using an OEM system win7 disk, then your disks probably have the drivers already and you're good to go.