Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
Rules have been updated! Here

Thread Rating:
  • 6 Vote(s) - 4.17 Average
  • 1
  • 2
  • 3
  • 4
  • 5

[-]
Tags
windows install kms predecessor license kms38™ generation licens upgrade hwid 10 digital or without

[Windows 10] Digital License (HWID) & KMS38™ Generation
#1
NOTE: When attempting to switch from default KMS to KMS38 (LongLife) activation, run the KMS38 process by selecting from the drop-down-menu, then; if no Office is installed repeat process in 'Clean' mode (same menu), if Office is installed use 'Rearm'.

Make sure the Office KMS activation is excluding Windows KMS38.




It's actually quite simple and doesn't mess with any system files and leaked (*errrm stolen) keys.

In Windows 10 all systems no matter how they were activated (be it via Upgrade from Windows 7/8.1 or by using a bought Retail or an embedded BIOS aka MSDM license) will be converted to a Digital License which is based on the Hard Ware ID (HWID) of the respective machine. This License is stored at MS Servers and will activate this machine every time it's freshly installed. Only hardware changes will cause the License being invalidated. By binding it to a Microsoft Account (MSA) you will be able to transfer it in latter case.
 
The process only needs to be performed once per machine. In later installs just skip any key prompts (choose 'I have no product key' during setup) and at first online contact the MS Server will regocnize the HWID and grant activation automatically.



The ticket creation has been appropriately refined for each MS SKU edition so that the Manual Method below is fully applicable to all of them. The Automated Method has been included as well for an easiest activation and works with all MS SKU editions and was specifically devised for the following ones:
 

Supported Windows 10 editions (SKUs):
  • Core (Home) (N) (HWID/KMS38)
  • CoreSingleLanguage (N) (HWID/KMS38)
  • Professional (N) (HWID/KMS38)
  • ProfessionalEducation (N) (HWID/KMS38)
  • ProfessionalWorkstation (N) (HWID/KMS38)
  • Education (N) (HWID/KMS38)
  • Enterprise (N) (HWID/KMS38)
  • EnterpriseS  (N) 2015(HWID)
  • EnterpriseS (N) 2016 (HWID/KMS38)
  • EnterpriseS  (N) 2019 (KMS38)
  • ServerStandard(Core) (N) (KMS38)
  • ServerDatacenterCore) (N) (KMS38)
  • ServerSolution(Core) (N) (KMS38)
 
 
REWORKED MANUAL PROCESS FOR HWID AND KMS38:


Prerequisites:

# the files:


Code:
The contents of this section are hidden
Register to view


# key and SKU-ID see the respective info TXT in files pack.


The Process:


#1. Copy files to a work folder, create exclusion in AV or disable temporarily. I will use d:\work as example.

#2. Install default generic key. Volume key (gVLK) for KMS38 or OEMRET for HWID (see included info TXT files).
Code:
The contents of this section are hidden
Register to view

    #2.a KMS38 only: Create dummy KMS adress entry using the demo IP range.
Code:
The contents of this section are hidden
Register to view

#3 LTSB 2015 only: rename gatherosstateLTSB15.exe to gatherosstate.exe (rename or overwrite the other).

#4. Depending on chosen process rename respective TargetSKU_XXXX.txt to TargetSKU.txt.

TargetSKU content syntax:
Show ContentSpoiler:



#5.  Run gatherosstate.exe by (double-)clicking.

#6. To apply ticket:
Code:
The contents of this section are hidden
Register to view
(note the trailing \)
    
    #6.a HWID only: force activation with:

Code:
The contents of this section are hidden
Register to view

#7. DONE. Congrats.
 

AUTOMATED METHOD:
 
NOTE:   The tool performs several system checks and may need a moment to appear (depending on your system specs), no need to panic, just wait a moment. Thanks.

Code:
The contents of this section are hidden
Register to view

Silent Mode:


Code:
The contents of this section are hidden
Register to view


MIRROR1 Download:

Code:
The contents of this section are hidden
Register to view





Hashes (EXE):

Code:
The contents of this section are hidden
Register to view
Reply
#2
Since i'm a noob on this, this should work like KMS but without using KMS tools right ?
[-] The following 5 users say Thank You to BALTAGY for this post:
  • an1a, jcvo, KRS, Neptune, nickwooshorr
Reply
#3
(05-15-2018, 03:44 PM)BALTAGY Wrote: Since i'm a noob on this, this should work like KMS but without using KMS tools right ?

This creates digital license by slightly abusing the way the upgrade Win 7/8.1 to Win 10 creates it.
[-] The following 4 users say Thank You to s1ave77 for this post:
  • ARMOUR, BALTAGY, jabrwky, KRS
Reply
#4
@s1ave77r I'm a bit confused here:
Quote:1. Get GatherOsState.exe from Windows 10 17134 ISO
So this ISO is needed? Does it matter which ISO from this build is used?

Quote:7. Enter default Retail/OEM key from products ini
where can we find the key?

Quote:   if you have Enterprise N or LTSB 2016 N use this in elevated Powershell:

Code:
::EnterpriseN
((Get-Content '.\gatherosstate.exe') -replace "`0" | Select-String -Pattern "(.....-){4}C372T" -AllMatches).Matches | Select-Object -ExpandProperty Value

::EnterpriseSN
((Get-Content '.\gatherosstate.exe') -replace "`0" | Select-String -Pattern "(.....-){4}VMJWR" -AllMatches).Matches | Select-Object -ExpandProperty Value
Do we have to replace the dots in (.....-) with anything when using these commands in elevated powershell?
[Image: XeGouw2s_o.png]
[-] The following 2 users say Thank You to Skunk1966 for this post:
  • KRS, s1ave77
Reply
#5
Thread stuck on top Windows forum.
Anything wrong?!
Doubt about something in the forums?!

Please push Report button or send me a PM!!! 

The contents of this section are hidden

The contents of this section are hidden

The contents of this section are hidden
======================================================================================

AiOwares is a community whose existence takes place by itself, not by movements unrelated to it.

======================================================================================
[-] The following 3 users say Thank You to WALLONN7 for this post:
  • Dahaka, KRS, s1ave77
Reply
#6
(05-16-2018, 07:48 AM)Skunk1966 Wrote: @s1ave77r I'm a bit confused here:
Quote:1. Get GatherOsState.exe from Windows 10 17134 ISO
So this ISO is needed? Does it matter which ISO from this build is used?

Quote:7. Enter default Retail/OEM key from products ini
where can we find the key?

Quote:   if you have Enterprise N or LTSB 2016 N use this in elevated Powershell:

Code:
::EnterpriseN
((Get-Content '.\gatherosstate.exe') -replace "`0" | Select-String -Pattern "(.....-){4}C372T" -AllMatches).Matches | Select-Object -ExpandProperty Value

::EnterpriseSN
((Get-Content '.\gatherosstate.exe') -replace "`0" | Select-String -Pattern "(.....-){4}VMJWR" -AllMatches).Matches | Select-Object -ExpandProperty Value
Do we have to replace the dots in (.....-) with anything when using these commands in elevated powershell?
Recommened ISO for the gatherosstate.exe is 17134.1.

I add the list from products.ini to OP. Interestingly the INI is in the \sources\ folder of the UUP>>ISO creation but not part of Techbench/MVS ISOs.

The powershell lines have to be used as they are.
[-] The following 4 users say Thank You to s1ave77 for this post:
  • jabrwky, KRS, Skunk1966, WALLONN7
Reply
#7
Added the urgent recommendation to use the tool from a folder on systemdrive with no spaces in the path.
[-] The following 6 users say Thank You to s1ave77 for this post:
  • ARMOUR, BALTAGY, Delboy, jabrwky, KRS, WALLONN7
Reply
#8
New version incoming ... now all needed files are compiled along with the EXE, start, hit patch and wait....

RELEASE: v6.66

AiO with all files included. Hit patch and wait 1.
[-] The following 6 users say Thank You to s1ave77 for this post:
  • ARMOUR, BALTAGY, jabrwky, KRS, PriSim, Skunk1966
Reply
#9
RELEASE: v6.67

--some visual upgrades
[-] The following 4 users say Thank You to s1ave77 for this post:
  • ARMOUR, jabrwky, Skunk1966, WALLONN7
Reply
#10

.log   HWID.log (Size: 788 bytes / Downloads: 0)
(05-16-2018, 09:27 PM)s1ave77 Wrote: AiO with all files included. Hit patch and wait 1.
so no need to run the scripts manually? All is automated now?

EDIT: I tried to activate Windows 10 2016 Ent. LTSB x64 but failed.

HWID.log:
Quote:Starting activation at 17 mei 2018 09:42:49...

Installing key NK96Y-D9CD8-W44CQ-R8YTK-DYJWX...
Productcode NK96Y-D9CD8-W44CQ-R8YTK-DYJWX is ge‹nstalleerd.

Adding registry entries...
Running GatherOsState...
Removing registry entries...

Applying GenuineTicket.xml...
Done.
Converted license Microsoft.Windows.125.X21-05035_8wekyb3d8bbwe and stored at (null).
Successfully converted 1 licenses from genuine authorization tickets on disk.
Done.

Activating...
Windows®, EnterpriseS edition (706e0cfd-23f4-43bb-a9af-1a492b9f1302) activeren...
Fout: 0x80070422 Kan de service niet starten omdat deze is uitgeschakeld of omdat het geen ingeschakelde apparaten met zich heeft verbonden.  (SWbemObjectEx)

Failed to activate EnterpriseS. License status: Notification

Is it possible that this has anything to do with Destroy Windows Spying? I ran DWS over a year ago. Also when I look at System and click on Activate button I see that Windows can't connect to activation servers
[Image: XeGouw2s_o.png]
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)