Time of death: 4:22 PM UTC September 26th

Notes, please read:

For those of you who don’t know, HWID was the holy grail for Windows activation, letting you generate licenses straight from Microsoft licensing servers, being registered as fully legitimate in microsofts servers and letting you keep the activation permanently, even after windows reinstalls being completely undetectable and with nothing on your system being modified. If you’re still using outdated activation methods and you missed out on this, I’m sorry

Existing HWID licenses are left unaffected. Only new requests are blocked, no licenses were revoked.

By the way, MAS still works and is the best option for Windows/Office activation. For permanent Office activation use it’s Ohook method (supports subscription products such as 365 as well) and KMS38 for Windows

ALL OTHER ACTIVATION METHODS ARE STILL WORKING, ONLY METHOD AFFECTED IS HWID.

All HWID activators are affected, not only MAS

Around that time, Microsoft servers unexpectedly started blocking the licensing requests HWID activation method sends to Microsoft. This was a slow rollout that spanned over a few hours, at the moment the exploit is completely dead. The best options for Windows activation now is KMS38 or vlmcsd.

Patching this would boost illegal key reselling websites which causes more harm to Microsoft than HWID exploit. We can only wonder why they patched this.

{“code”:“BadRequest”,“data”:[],“details”:[],“innererror”:{“code”:“PermanentTSLRejection”,“data”:[],“details”:[{“code”:“113”,“message”:“avsErrorCode”,“target”:null}],“message”:“The Purchase Service rejected the provided TSL; the client should destroy the TSL.”,“source”:“PurchaseFD”},“message”:“The calling client sent a bad request to the service.”,“source”:“PurchaseFD”}

TLS=Temporary Signed License=The tickets HWID activation sends. Microsoft servers are now just responding with “kill it.”

Transferring existing HWID licenses to other computers using Microsoft account is broken too.

  • berserker@lemm.ee
    link
    fedilink
    English
    arrow-up
    11
    ·
    1 year ago

    After reading through the docs on the MAS site, KMS38 still looks pretty robust. I get that it’s not ‘permanent’ but are there any major drawbacks aside from having to re-run MAS after a fresh Windows install?