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.

  • DreadPotato@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    2
    ·
    edit-2
    1 year ago

    I recently tried ubuntu on my laptop, every time i brought it back from sleep/hibernation my touchpad wasn’t working and i had to reboot. It’s been a few years since i used it last, i was expecting significantly better stability than that…

    • CeeBee@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      There’s sometimes the odd little issue here and there with things like touchpads. The issue is that device manufacturers keep their device drivers closed sourced, and have zero interest in contributing to things like Linux. So it’s up to open source devs to develop their own drivers.

      Sometimes there’s a bug or two, especially in things like laptops. If you’re using Ubuntu, you’re on an older kernel. The bug may have already been fixed but not made into Ubuntu yet.

      I bet if you tried out something newer like OpenSUSE Tumbleweed or an Arch based (like EndeavourOS, I recommend it) you might find the issue gone.

      • DreadPotato@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        It’s a 9 year old laptop, so things really should be ironed out on the HW side IMO. It didn’t have issues last i used ubuntu, think it was 18.04 i used back then.

        • CeeBee@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Regressions happen. One bugfix might introduce a new bug, or interfere with an old one.

          Code is incredibly complex and pulling on one string can unravel another.