s1ave77 1,999 Posted May 13 (edited) 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™. INFO: For adapted KMS_VL_ALL (Manual only) see download section beneath. 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. NOTE: When a Volume License version is installed from VLSC or MVS Business ISO, the default Retail/OEM key needs to be inserted to regain acticvation. It's actually quite simple and doesn't mess with any system files and leaked (*errrm stolen) keys. 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) <KMS19™> ServerStandard(Core) (N) <KMS38™> ServerDatacenterCore) (N) <KMS38™> ServerSolution(Core) (N) <KMS38™> MANUAL METHOD: 1. Get GatherOsState.exe from Windows 10 17134 ISO 2. Get latest version of slshim from https://github.com/vyvojar/slshim/releases 3. Extract slshim32.dll (for gatherosstate from x86 ISO) or slshim64.dll (for gatherosstate from x64 ISO) 4. Place gatherosstate and extracted slshim dll in the same directory 5. Rename slshim dll to slc.dll 6. Import this to registry: 6.1. Set the real value for %sku% from beneath list. edition=Cloud sku=178 edition=CloudN sku=179 edition=Core sku=101 edition=CoreCountrySpecific sku=99 edition=CoreN sku=98 edition=CoreSingleLanguage sku=100 edition=Education sku=121 edition=EducationN sku=122 edition=Enterprise sku=4 edition=EnterpriseN sku=27 edition=EnterpriseS sku=125 edition=EnterpriseSN sku=126 edition=Professional sku=48 edition=ProfessionalEducation sku=164 edition=ProfessionalEducationN sku=165 edition=ProfessionalN sku=49 edition=ProfessionalWorkstation sku=161 edition=ProfessionalWorkstationN sku=162 Replace the 'XXX' with the needed sku value. If using REG make sure the string is 7 digits long, the CMD will take the value from above. CMD: reg add "HKLM\SYSTEM\Tokens" /v "Channel" /t REG_SZ /d "Retail" /f reg add "HKLM\SYSTEM\Tokens\Kernel" /v "Kernel-ProductInfo" /t REG_DWORD /d XXX /f reg add "HKLM\SYSTEM\Tokens\Kernel" /v "Security-SPP-GenuineLocalStatus" /t REG_DWORD /d 1 /f reg add "HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers" /v "C:\gatherosstate.exe" /d "^ WIN7RTM" /f Make shure the XXX are peplaced by shown ID from above SKUID list. Adapt the above path to gatherosstate.exe to the actual path. 7. Enter default Retail/OEM key from products ini Key list from 17134.1 products.ini: Site: https://pastebin.comShareCode: /rYakstDc if you have Enterprise N or LTSB 2016 N use this in elevated Powershell: ::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 this will gather the key from within gatherosstate.exe 8. Run gatherosstate. After a few seconds you should get GenuineTicket.xml 9. (optional) Remove HKEY_LOCAL_MACHINE\SYSTEM\Tokens from registry. CMD: reg delete "HKLM\SYSTEM\Tokens" /f reg delete "HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers" /v "C:\gatherosstate.exe" /f 10. Place the created genuineticket at the root of c:\ and in admin CMD: clipup -v -o -altto c:\ 11. then force activation with: cscript /nologo %windir%\system32\slmgr.vbs -ato DONE. Congrats. AUTOMATED METHOD: In case any VPN is used, deactivate it for the process duration. 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. v40.08 --made the CoreToPro In-place-Upgrade in License Switcher fully automatic v40.01 --added Info Splash Screen and made it default Mode at tool start-up --added Rearm Mode in case Office is installed, else better use Clean (Reboot is mandatory for Rearm!) --changed Grace to show days --changed appearence of warning for silent modes (now at first/next user login) --added Modes to enable/disable the network adapter --added LicenseSwitch Tool: ++In-Place-Upgrade Core(N) to Professional(N), copies needed Pro(N) key to clipboard and invokes the 'Change Product Key' GUI, just Right-Click 'Paste. ++License-Switch versions from 1803 up to wished edition, reboot required. --added adapted version of KMS_VL_ALL (Manual Only) with KMS38™ detection to OP v30.18 --fixed borked silent mode v30.11 --switched to the new naming hence a refresh v30.08 --added KMS Host setting to KMS38™ process to avoid DNS queries v30.01 --added dedicated Modes for HWID, KMS38™, HWID/gVLK install and a Clean Mode to break the 180 days KMS lock --HWID: all normal editions with LTSB 2015/16 --KMS19™: [!!!offline!!!] all normal editions, LTSB 2016, LTSC 2019 and some Servers (see list above) --added refreshed system check to all processes --new silent switches: hwid and kms19 v20.01 --added 1809 gatherosstate.exe, added LTSC/Server (2016/19) support for offline KMS activation (19 years grace) v10.24 --fixed incorrect reg delete (thanks to angelkyo for the hint) v10.21 --corrected the Win 7 compat entry (thanks to the alert source) v10.18 --fixed broken LTSB 2016 process v10.15 --added Enterprise LTSB 2015 (N) support (tested on non-N version) (thanks to hwidmod for the gatherosstate.exe needed) v10.08 --added Key-Install-Mode (Drop-Down-Menu) to allow fast switch to Retail/OEM on re-Installs with VL ISO, which already have HWID and don't need the whole process, tool will show this key in System Info if not installed v10.01 --changed process slightly to run gatherosstate.exe in Win 7 compatibility mode, so created ticket will have operation system info set to Windows 7, this better mimiks the original ticket from a Win 7 system --optimized the Splash screens v9.32 --added hyperlinks to nsane and aiowares forums threads for info and support v9.25 --changed the initial Msgbox to splash screen with no user intervention v9.18 --reworked system check v9.11 --added LTSB 2015 (only non-N and not tested so far) and native splash screen to silent mode v9.04 --fixed spelling error in splash pic v9.01 --fixed the KMS detection (will work on activated KMS systems now) amd added silent mode v8.13 --added Messagebox to inform user tool-start-up might need a moment, fixed tool not closing when done via the 'X' v8.06 --changed disabled WU handling to: set to auto, start service, activate, stop service and set back to disabled v7.99 --added last checks and some code cleanup v7.77 --implemented disabled WU handling. Silent Mode: hwid.kms38.gen.mk5 hwid hwid.kms38.gen.mk5 kms38 HWID.KMS38™GEN DOWNLOAD: MIRROR1: Site: http://rgho.stSharecode: /7ynVwQ2ld MIRROR 2: Site: https://www.upload.eeSharecode: /files/9072366/hwid.kms38.gen.mk5.7z.html Pass (both): 3Fs44Rv#tZ4u3UOij656NgF____ Exe hashes: BLAKE2sp: 6977cd0ca7316ce01da842df7e331c6e6cc0483f087829f1f7bef155a9af3db1 CRC64: 589647030f727e81 MD5: 5c6f103f4ecb7d893f7186d8b935020d SHA-1: 54773a479f73757c832029b712082d6267b5ce88 SHA-256: 315b60d53d5e0223dcd709735e3f3d245fdae50b585378361ed977bce2e1393b SHA-384: 9a83d07a9494d72670945b5182c4fc4e27979f600ca7efccfa2cbb865b26e15aa54b8d557c75005c3604e4bff1ab01cd SHA-512: 01824096755e6547bebbe307de74d10b2e27d99ae7297bf22b5c4d96194ea22f783db12f164456bf80f4a38dd74a9a6260906938f2124f09516c7b3c9e34ff73 SHA3-224: 6bfc799f2a304abfd45720659bdaee2743c78dd67082481f889ea955 SHA3-256: bdebb5051e31095f95d059934e7c3ae8c924f74e9e2604c077727382867d0ced ADAPTED KMS_VL_ALL (MANUAL ONLY) DOWNLOAD: Site: https://www.upload.eeSharecode: /files/9064702/adapted_all.7z.html [all credits to the original creator] Pass: MDL2018 Edited 18 hours ago by s1ave77 98 110 1 Terminator90, pirrex, Wirya and 206 others reacted to this Share this post Link to post Share on other sites
R3dMan 277 Posted May 13 On 14/05/2018 at 12:18 AM, s1ave77 said: It's actually quite simple and doesn't mess with any system files and leaked (*errrm stolen) keys. . Get GatherOsState.exe from Windows 10 17134 ISO 2. Get latest version of slshim from https://forums.mydigitallife.net/threads/7096The requested thread could not be found.5/ 3. Extract slshim32.dll (for gatherosstate from x86 ISO) or slshim64.dll (for gatherosstate from x64 ISO) 4. Place gatherosstate and extracted slshim dll in the same directory 5. Rename slshim dll to slc.dll 6. Import this to registry: The current site for slshim get error "The requested thread could not be found." 3 2 IvanHor, Tiburcio, Melgas and 2 others reacted to this Share this post Link to post Share on other sites
s1ave77 Topic Author 1,999 Posted May 13 3 minutes ago, R3dMan said: The current site for slshim get error "The requested thread could not be found." I updated OP with the github link. MDL is bitchy about that topic :D. 7 5 metalinux, ByRH, sid_16 and 9 others reacted to this Share this post Link to post Share on other sites
jabrwky 230 Posted May 13 (edited) 36 minutes ago, s1ave77 said: GatherOsState.exe from Windows 10 17134 ISO This sure is a hytone coding job, and much in awe of your skills. I'm new to this one. Can I run the script in the same directory as the Win10 ISO, or need to copy "GatherOsState.exe" from Windows 10 17134 ISO -- to make this work. QUOTE: "Mount the ISO via (double)click and run the tool, when asked for the Drive Letter, enter it without colon i.e. d. Press (S) to start the process." Excellent instruction, thx. Edited May 13 by jabrwky 2 1 s1ave77, MiamiNights and Jordan reacted to this Share this post Link to post Share on other sites
s1ave77 Topic Author 1,999 Posted May 13 Just now, jabrwky said: I'm new to this one. Can I run the script in the same directory as the Win10 ISO, or need to copy "GatherOsState.exe" from Windows 10 17134 ISO -- to make this work. Mount the ISO via (double)click and run the tool, when asked for the Drive Letter, enter it without colon i.e. d. Press (S) to start the process. 3 2 SunLion, Recruit, jabrwky and 2 others reacted to this Share this post Link to post Share on other sites
coromonadalix 84 Posted May 14 (edited) okay if i get this right, it is a way to digitally sign an new/fresh windows 10 installation without upgrading or have any prevously installed windows ??? what do you mean by your method 2 bitchy installations ??? thks Edited May 14 by coromonadalix error Share this post Link to post Share on other sites
Freddyfre 1,415 Posted May 14 method 2 works fine with LTSB x64 6 fnsfernando, neofita, jamesDDI and 3 others reacted to this Share this post Link to post Share on other sites
Borgin 7 Posted May 14 Quote *For those who are running VL installs must insert the standard key (from the product.ini file) before running the gatherosstate.exe!!! What does this mean? Share this post Link to post Share on other sites
jabrwky 230 Posted May 14 (edited) After some major *revisions* (aka / *updates*) some time back -- My Win10 Ent. magically changed to Education Edition after reboot! -- And was deactivated! Using Method-*1* [one]: -- can i use a activation-key detecting tool to find and re-use the *activation key* -- after activating with method *1* -- ?? Or would it be useless to try to re-use the installed key to re-activate the OS? Thanks for all this excellent work. Edited May 14 by jabrwky 2 1 s1ave77, Jordan and ARMOUR reacted to this Share this post Link to post Share on other sites
compgen1534 3,166 Posted May 14 wow. workin on my end. tested in a VM with method 2 thanks! 4 1 ARMOUR, pnefyp, neofita and 2 others reacted to this Share this post Link to post Share on other sites
Borgin 7 Posted May 14 Is this method easier on Consumer or Business edition? Share this post Link to post Share on other sites
neofita 1,260 Posted May 14 (edited) it works here on LTSB x64 2nd method, previously KMS activated Edited May 14 by neofita 4 1 pnefyp, s1ave77, dcs18 and 2 others reacted to this Share this post Link to post Share on other sites
jonaaa20 157 Posted May 14 2nd method working on LTSB x64 too! 3 pnefyp, someone there and Jordan reacted to this Share this post Link to post Share on other sites
Freddyfre 1,415 Posted May 14 24 minutes ago, neofita said: it works here on LTSB x64 2nd method, previously KMS activated Yes, prerequisite activate with KMS (180 days) 1 1 s1ave77 and pnefyp reacted to this Share this post Link to post Share on other sites
s1ave77 Topic Author 1,999 Posted May 14 8 hours ago, coromonadalix said: okay if i get this right, it is a way to digitally sign an new/fresh windows 10 installation without upgrading or have any prevously installed windows ??? what do you mean by your method 2 bitchy installations ??? thks Yep, that's the idea behind it :). Both ways trick the gatherosstate.exe into thinking to activate legit licenses (the activation system has some serious holes). Method 1 had problems to activate i.e. ProfessionalEducation in several tests, Method 2 worked flawlessly with this edition. 3 hours ago, jabrwky said: After some major *revisions* (aka / *updates*) some time back -- My Win10 Ent. magically changed to Education Edition after reboot! -- And was deactivated! Using Method-*1* [one]: -- can i use a activation-key detecting tool to find and re-use the *activation key* -- after activating with method *1* -- ?? Or would it be useless to try to re-use the installed key to re-activate the OS? Thanks for all this excellent work. In Windows 10 the editions from Pro on got unified even more with 17XXX builds, one can go from Pro to higher editions and back by just changing the key. The default (aka installation key from products.ini) key only determines the edition installed, not the license used. Upgrade licenses are based on hardware IDs stored at MS Servers, so as long as the hardware isn't changed, the system will activate when online. This process uses the generic retail keys (the previously mentioned products.ini ones) but it's the HWID that grants the activation. Because the HWID license uses generic keys it makes no sense to save these keys. It's the generated genuineticket that activates the systems. You can enter the default Enterprise key to switch your edition back to Enterprise (needs a reboot to complete) and use Method 1 to activate the Enterprise with a generated ticket. Or just activate the Education edition you run now. 3 3 jonaaa20, MrX, jabrwky and 3 others reacted to this Share this post Link to post Share on other sites
Rudi1 3 Posted May 14 @s1ave77 Thank you,second method work fine for ltsb x64!Just one guestion.Can this method can be done via during instal os on $OEM$ folder? Share this post Link to post Share on other sites
s1ave77 Topic Author 1,999 Posted May 14 1 minute ago, Rudi1 said: @s1ave77 Thank you,second method work fine for ltsb x64!Just one guestion.Can this method can be done via during instal os on $OEM$ folder? Must admit was not tested so far. Thing is that it's only needed to be done once per system and not generally for each install. Would assume it's easier to do it manually after the install that one time per physical machine. Nevertheless theoretically it should work. 3 1 jabrwky, MrX, sid_16 and 1 other reacted to this Share this post Link to post Share on other sites
s1ave77 Topic Author 1,999 Posted May 14 NOTE: I added a comment from the source of this to OP. Method 1 should be prefered over Method 2 if working, since it doesn't rely on KMS activated system. Method 2 should be seen as fallback for bitchy editions like ProfessionalEnterprise and it's N version. 5 3 pnefyp, compgen1534, jabrwky and 5 others reacted to this Share this post Link to post Share on other sites
Rudi1 3 Posted May 14 You are right.No problem to run it manually :)This method is really amazing! 1 s1ave77 reacted to this Share this post Link to post Share on other sites
mehdibleu 5,504 Posted May 14 Great discovery!!! very good job. i think we've already met somewhere else. just to be clear, concerning "method 1" and seven point, you mentionned that for people who have Enerprise N and LTSB 2016 N installed on their machines, they have to run the mentionned command lines in admin mod, and what about the ones that don't have both of these versions installed on their machines, do they have to skip that step or do they have to run these command lines as well by entering the right Retail/OEM key for the right win10 installed version ? 2 pnefyp and ARMOUR reacted to this Share this post Link to post Share on other sites
s1ave77 Topic Author 1,999 Posted May 14 7 minutes ago, mehdibleu said: Great discovery!!! very good job. i think we've already met somewhere else. just to be clear, concerning "method 1" and seven point, you mentionned that for people who have Enerprise N and LTSB 2016 N installed on their machines, they have to run the mentionned command lines in admin mod, and what about the ones that don't have both of these versions installed on their machines, do they have to skip that step or do they have to run these command lines as well by entering the right Retail/OEM key for the right win10 installed version ? All users not having that specifically mentioned editions only need to make sure the generic Retail/OEM key for their edition is installed (if not needs manual install). 8 2 Recruit, MrX, LoveCyberLink and 7 others reacted to this Share this post Link to post Share on other sites
meohmy 16 Posted May 14 I cant seem to download method 1 and 2 from rgho.st, I have tried 3 different browsers as well as JDownloader and all failed. The files are there but nothing works to download them, any suggestions so that I can try this great post please? Or would someone be kind enough to upload elsewhere. Share this post Link to post Share on other sites
mehdibleu 5,504 Posted May 14 (edited) 19 hours ago, meohmy said: I cant seem to download method 1 and 2 from rgho.st, I have tried 3 different browsers as well as JDownloader and all failed. The files are there but nothing works to download them, any suggestions so that I can try this great post please? Or would someone be kind enough to upload elsewhere. method1 => Site: https://www108.zippyshare.comShareCode: /v/WjJBQ8KN/file.html method2 => Site: https://www96.zippyshare.comShareCode: /v/Xk13Vav2/file.html Edited May 15 by Crazycanuk Share-code Added 10 3 fnsfernando, LoveCyberLink, Crazycanuk and 10 others reacted to this Share this post Link to post Share on other sites
s1ave77 Topic Author 1,999 Posted May 15 I updated OP with AiO version of the tool. Now it uses Method 1 by default and only ProfessionalEducation (N) use Method 2 since 1 doesn't. Checked successfully with several installs. 5 7 Melgas, neofita, psyko666 and 9 others reacted to this Share this post Link to post Share on other sites
Pachuco 8 Posted May 15 I don't think I understand it. Had Win 10 Pro activated with KMS. When doing Method 2 (before update in previous post) it ran gatherosstate for Enterprise with the "Error: 0x803F7001 On a computer running Microsoft Windows non-core edition". Afterwards I tried the updated Method 1, which gave the same result. Any suggestions? Share this post Link to post Share on other sites
