MAS-1.4 and HW*Dgen 62.01 will easily perform this method of activation... I have done this many times without issue...
HwID based activations can be easily tracked by MS, they are unique and verify their activation state regularly. If you don't have an issue with that, go for it.
KMS38 is a completely offline based activation procedure which is valid till 2038 and just like every other activation technique, there is no disadvantage features wise.
https://forums.mydigitallife.net/threads/kms_vl_all-smart-activation-script.79535/#post-838808 is the new version from creator
Not really, KMS38 is not the same as or related to kms_vl_all. KMS38 is developed by whatever/mspaintmsi along the way of the hwid activation, first it was hwid generation based on kms activated OS, then they came across the 19 year activation later called KMS38 (originated in 2019, iirc, and worked till 2038) and they decided to keep it aside of the hwid activation.
if OP is using LTSB 2016 (v1607), it can be activated with either HWID or KMS38 newer LTSCs like LTSC 2019 (v1809) can be activated with KMS38 only (not HWID) oldest LTSB version like LTSB 2015 (v1507) can be activated with HWID only (not KMS38)
HWID is available for all consumer, business and LTSB/C (LTSC non N only) sku's except server. Spoiler: KMS38 Supported Products Code: ==================================================================================================== Supported Products: ==================================================================================================== Windows 10: Core CoreCountrySpecific CoreN CoreSingleLanguage Education EducationN Enterprise EnterpriseG EnterpriseGN EnterpriseN EnterpriseS [LTSB 2016 & LTSC 2019] EnterpriseSN [LTSB 2016 & LTSC 2019] Professional ProfessionalEducation ProfessionalEducationN ProfessionalN ProfessionalWorkstation ProfessionalWorkstationN ServerRdsh ------------------------ Windows Server: ServerCloudStorage [Server 2016] ServerDatacenter [Server 2016 & 2019] ServerDatacenterCor [Server 2016 & 2019] ServerSolution [Server 2016 & 2019] ServerSolutionCor [Server 2016 & 2019] ServerStandard [Server 2016 & 2019] ServerStandardCor [Server 2016 & 2019] ServerAzureCor [Server 2016 & 2019] ServerDatacenterACor [All versions] ServerStandardACor [All versions] Note - X86-X64 and ARM64 architecture systems are supported. - Any Evaluation version of Windows and Server (i.e. 'EVAL' LTSB/C) cannot be activated. - KMS38 only supports Windows/server version 14393 (1607) and newer versions. Spoiler: HWID supported products Code: ==================================================================================================== Supported Products: ==================================================================================================== Windows 10 Versions that can be activated: Core CoreCountrySpecific CoreN CoreSingleLanguage Education EducationN Enterprise EnterpriseN EnterpriseS [LTSB 2015/2016 & LTSC 2019] EnterpriseSN [LTSB 2015/2016] Professional ProfessionalEducation ProfessionalEducationN ProfessionalN ProfessionalWorkstation ProfessionalWorkstationN ServerRdsh IoTEnterprise Note - X86-X64 and ARM64 architecture systems are supported. - Any Evaluation version of Windows (i.e. 'EVAL' LTSB/C) cannot be activated.
KMS and KMS38 is completely offline activation, provided you disable the online Genuine ticket feature.
That is true for KMS but not for KMS38. 'KMS Client Online AVS Validation' is only triggered when the system gets a successful activation event, and in KMS client, that is only possible if it gets a successful response from the KMS server. Since in KMS38, it doesn't connect to the working KMS server, it never triggers a successful activation event (errorlevel is not zero in slmgr /ato), and the system doesn't send the data to MSFT because of that.