PHEagleEye04
Eternal Poster
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):
Download link:
You do not have permission to view the full content of this post. Log in or register now.
You do not have permission to view the full content of this post. Log in or register now.
Hashes:
BLAKE2sp: 45527c3aeeda2c0bb34d73d3d5719b7888499ca705452b834dad252adf58c2ac
SHA-1: 40779e9f591f0ae04e6967095b4974d04a5f2984
SHA-256: af333dbeab9268398d985eb80c74adfaa84210a7e6222ab3fc1684a73f052ff1
SHA-384: a235cc6557252c76232890fe38098b205448039eddd29c37808c560c9b771a25d8fa4fc0f058cd9bed4e2990ec94e07f
SHA3-224: a4ae4cb97db166222370c3585df4db3c01d553f14cf3d0c18a461fb8
SHA3-256: d984607f3e72ce63e98d0c00a6637b1af2d8332e3a6561e13c6091a70714bf7c
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)
Download link:
You do not have permission to view the full content of this post. Log in or register now.
You do not have permission to view the full content of this post. Log in or register now.
Hashes:
BLAKE2sp: 45527c3aeeda2c0bb34d73d3d5719b7888499ca705452b834dad252adf58c2ac
SHA-1: 40779e9f591f0ae04e6967095b4974d04a5f2984
SHA-256: af333dbeab9268398d985eb80c74adfaa84210a7e6222ab3fc1684a73f052ff1
SHA-384: a235cc6557252c76232890fe38098b205448039eddd29c37808c560c9b771a25d8fa4fc0f058cd9bed4e2990ec94e07f
SHA3-224: a4ae4cb97db166222370c3585df4db3c01d553f14cf3d0c18a461fb8
SHA3-256: d984607f3e72ce63e98d0c00a6637b1af2d8332e3a6561e13c6091a70714bf7c