+- AiOwares (https://www.aiowares.com)
+-- Forum: Software & Applications (https://www.aiowares.com/forumdisplay.php?fid=6)
+--- Forum: Multi-Platform Software (https://www.aiowares.com/forumdisplay.php?fid=14)
+---- Forum: Windows (https://www.aiowares.com/forumdisplay.php?fid=42)
+---- Thread: [Windows 10] Digital License (HWID) & KMS38™ Generation (/showthread.php?tid=246)
RE: [Windows 10] Digital License (HWID) & KMS38™ Generation - s1ave77 - 02-16-2019
Reworked the manual process for HWID and KMS38.
RE: [Windows 10] Digital License (HWID) & KMS38™ Generation - nimfu88 - 03-04-2019
hello, with the reworked manual process, can you explain how to upgrade my original windows 10 home single language (came with laptop, now activated with digital license).
additionally i don't understand what to put in TargetSKU.txt , where to put this TargetSKU.txt
also i tried various things, putting '48' , the gatherosstate.exe is throwing up error
RE: [Windows 10] Digital License (HWID) & KMS38™ Generation - s1ave77 - 03-05-2019
(03-04-2019, 01:15 PM)nimfu88 Wrote: The contents of this section are hiddenYou have No permissions
Are you trying to upgrade from CSL to Professional ? You'll need licenseswitch tool (see the mode drop-down-menu) to do so. That would explain why it fails.
RE: [Windows 10] Digital License (HWID) & KMS38™ Generation - s1ave77 - 03-31-2019
Update to v0.61.01
v61.01
--processes have been reworked
--AiO slc.dll for HWID and KMS38 processes
--new DLL uses gatherosstate.exe from 17134 ADK, only LTSB 2015 uses modded version of it
--processes now read SKU-ID directly from the OS
--channel is determined from DigitalProductId4, the SKU ID is determined from kernel value.
--TargetSKU.txt now uses generic values for OS detection and process
--TargetSKU.txt can still use SKU-ID value as fallback
--implemented checks for service functionality of wuauserv, clipsvc, wlidsvc and sppsvc
--System checks will try to enable any disabled service(s) temporarily and start them to assure working processes
--changes are redone after checking and during the processes
--error messages will help to determine problems
RE: [Windows 10] Digital License (HWID) & KMS38™ Generation - s1ave77 - 04-08-2019
Update to v0.62.01
v62.01
--added option to clean ClipSVC tokens, this can be used to activate System Images on different machines since
you cannot activate 2 systems using the same tokens
RE: [Windows 10] Digital License (HWID) & KMS38™ Generation - ASHERH4X - 05-17-2019
So does this tool work with Office 2016 & Office 2019? Or just Windows 10 and Server 2012-2019?
btw, I LOVE THIS TOOL.
RE: [Windows 10] Digital License (HWID) & KMS38™ Generation - Skunk1966 - 05-17-2019
(05-17-2019, 06:29 AM)ASHERH4X Wrote: The contents of this section are hiddenYou have No permissionsSupported editions:
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)
To activate Office use KMS_VL_All
RE: [Windows 10] Digital License (HWID) & KMS38™ Generation - shayan007 - 06-27-2019
https://www.virustotal.com/gui/file/af333dbeab9268398d985eb80c74adfaa84210a7e6222ab3fc1684a73f052ff1/detection
?
RE: [Windows 10] Digital License (HWID) & KMS38™ Generation - Skunk1966 - 06-28-2019
detections are false-positives; nothing to be worried about
RE: [Windows 10] Digital License (HWID) & KMS38™ Generation - The Undertaker - 06-30-2019
Hello
I am using the automated tool. It gives me two options (amongst others) of hwid and hwid_key. I am not able to differentiate between them properly. I am trying to activate Windows 1809 pro x64
Which is the preferred of the two in my case hwid or hwid_key?
Thank you.