Windows 10: Clean Install Windows 10 Directly without having to Upgrade First

Hi All,

I was wondering if this XML file could be used on multiple machines or whether you need to generate a new XML file for each machine. I have a room of PCs all with Win7 Pro OEM licences that I would like to put Win10 on. This tutorial will make that so much easier to do legitimately, just wondering if I can avoid running the exe and copying the file on each machine, or if there's a way to automate it.


Thanks,

 

It is specific to the computer on which it was made - otherwise there would be one file that everyone could use universally.

 

For a key "Good for All" you then need to get into looking at Volume Licensing which falls under a totally different category. Large companies as well as small businesses and hardware vendors typically those types. You can use one key on 100 machines type licenses are the usual there.

Custom builders on the other hand selling custom built pcs like Alienware will have another single pc "OEM for System Builder" type license also an option available at Newegg, TigerDirect, etc. as well as the full retail license if you have multiple systems planned. For the gatherosstate.exe file described here you have to run that on separately on each machine that already has the activated installation for one of the previous versions. 7 with SP1, 8, or 8.1 qualifying. Home or Home Premium to 10 Home along with Pro or Ulimate(Windows 7 only not 8, 8.1) for the 10 Pro.

 

Yep, that's correct... I wrote this script to display the hardwareID (save as a .ps1 file in the the same folder as GT.xml - this is based on one from Win 7 but works with Win 8 GT's as well)

Code: $Path = $PSScriptRoot + "\GenuineTicket.xml" [xml]$GT = Get-Content ($Path) $node = $GT.genuineAuthorization.genuineProperties.properties $Split = $node -split (';') if (($Split[0] -like '') -or ($Split[1].StartsWith("OA3"))) { $SessionID = $Split[2] -replace ("SessionId=") } else { $SessionID = $Split[0] -replace ("SessionId=") } $Decoded = [System.Text.Encoding]::Unicode.GetString([System.Convert]::FromBase64String($SessionID)) $Split = $Decoded -split (';') $HwID = $Split[4] -replace ("Hwid=") $HwID = [System.Text.Encoding]::Unicode.GetString([System.Convert]::FromBase64String($HwID)) $Path = $Path -replace ("GenuineTicket.xml", "SessionID.txt") $key = $GT.genuineAuthorization.genuineProperties.signatures.signature.key $downlevelGTkey = [System.Text.Encoding]::Unicode.GetString([System.Convert]::FromBase64String($key)) "SessionID:`n" + $Decoded -replace (';',"`n") | Set-Content $Path "Hwid is RSA-SHA256 encrypted!:`n" + $HwID | Add-Content $Path "`nDownlevelkey:`n" + $key | Add-Content $Path "`nKey is RSA-SHA256 encrypted!:`n" + $downlevelGTkey | Add-Content $Path Invoke-Item $Path[/quote]

 

Well, after going over the details (salivating of course), I'm having an issue doing a Win10 clean install as per OP.
Following OP, I figured the activation servers were busy, thus I waited, however I believe it should have activated after several days n Reboots.
...details as follows.....

Activation
Error code: 0xC004C003
Error Description: The activation server determined the specified product key has been blocked.

My Travels:
1- Win7 Pro; Ensured latest updates for OS & MSE (even did another MSE Quick Scan); several reboots; left system on overnight & looked for additional updates; confirmed Windows is activated via msg on system about page; then ensured validation via legitcheck.hta & WindowsActivationUpdate.exe and confirmed the page that displays MSE is available for this device.
2- After confirming validation, another reboot; ran gatherosstate.exe w/elev privledges & copied the generated GenuineTicket.xml to another partition on laptop HDD.
3- Installed Win10 via contents of the 32bit Win10 N Pro iso (same directory from which I grabbed the Gatherosstate.exe); ran setup from /sources directory (to bypass the hardware compatibility check).
4- Followed OP for placement of GenuineTicket.xml

System Details:
Dell Inspiron notebook, Atom n270 cpu, 2g ram. Several cpu utils depict varying info as to PAE, NX bit, SSE2 EM64T, etc, thus I ran Sysinternal's Coreinfo.exe confirming EM64T, NX, PAE & SSE2.

I know this is an outdated system & that it may not run, performance and all that stuff, so please save your breath. I like the exercise and I've been using Win10 on this in a dual-boot config since February and I'm very content, especially since it outperforms Win7 on only 2g of ram (yeh, I am still surprised about that).
I would simply like to know why I'm getting this error, cannot activate and what I may be overlooking.
thx

 

Hello sos, *Smile

If you have a Windows 7 Pro, then you would need to install Windows 10 Pro, and not a W10 N Pro.

If you used the same key to activate more than one installation at the same time, then this could be why it was blocked.

 

That's for sure! The "N" in 10 Pro N when seeing it with "7 Pro" as in "7 Pro N" equals "NO GO" or simply "Not Happening"! You are defeating your own efforts there. sos1043

As far as seeing multiple 10 installs activated on the same machine I would think it would be a day or so between separate installs on the same machine unless upgrading from two separate editions of previous versions one Home the other Pro to see both 10 Home and 10 Pro simultaneously since each install needs the correct upgrade path.

 

Matching installs for 32, 64, Home & Pro, understood, but I'd have never thought 'N' would have any correlation. Not to sound doubtful, but along with salvaging a weekend I hope you're right *Cool
As for keys, there's none, it's an upgrade and only performing one install.
Much appreciate the info here and your post!

 

Regional Distribution plays a role since an N build wouldn't what you would see in the US, UK, Canada, and other countries in these parts of the globe. But you have to remember that MS news pointing to 192 which includes the Eastern European block as well as Asia and South America as well as the African continent and Middle East since MS is global. Back when Vista Basic and 7 Starter were seen those were directed to developing countries. And to this day you will still find 34 language packs in the Optional updates available.

 

I'd read that N is without the media player. Is that the same distro as the "MS news pointing to 192"? Or is that another distro?
thx.

 

The MS page explains in detail about the differences between the US based and EU releases. What is a Windows 7 N edition? Windows 7 N editions offer choice

With the free upgrade to 10 the new Windows DVD Player option is provided as an update. If you replace the upgrade install or go for the clean install method here bypassing the upgrade entirely you would need to buy the player separately at the MS online store. MS threw in the Windows DVD Player otherwise $30US as an incentive for people to try the free upgrade to 10 out.

Another reference that explains further about special editions is the blog seen at Windows 7, 8, 8.1 and 10: N, K and KN Special Editions

 

Great info, thx.
Omitted the N build iso; straight 10-Pro, worked w/o a hitch, thx, thx.
Updated 'N'otes *Wink