Troubleshoot

A symptom-first troubleshooting path for MAS activation failures, with links to the relevant method guides, tools and the official Massgrave issue tracker.

This page is an independent troubleshooting reference for Microsoft Activation Scripts (MAS). It does not replace the official Massgrave documentation or the issue tracker — use those for bug reports.

Start here

  • Read any blue-coloured lines the script prints. MAS writes the exact cause and the recommended next step there; most failures are explained on screen.
  • Make sure you are running the current upstream release. Older copies fail against newer Windows builds. See the version history, which reads the official release feed directly.
  • Confirm the copy you are running really came from the project. Follow the checks on the security and verification page before blaming the script.

Choose by symptom

SymptomLikely areaWhere to look
Script closes immediately or PowerShell blocks the commandExecution policy, antivirus, or a blocked domainPowerShell issues
Activation fails with a 0x… error codeLicensing service or store stateError decoder
Windows shows activated, then revertsRenewal task missing, or hardware changeKMS activation explained
Office keeps saying the license is not genuineOhook install or a leftover licenseOffice activation guide
Digital licence not applied after reinstallHWID / Microsoft account linkingHWID deep dive
Wrong edition after activationEdition mismatchEdition converter

Before asking for help

  1. Note your exact Windows or Office build and edition.
  2. Check the current status with the commands on the activation status checker.
  3. Take a screenshot of the full script output, including the blue lines.
  4. Compare your case with the troubleshooting hub and the glossary for unfamiliar terms.

Where to report

Bugs belong upstream, with the people who maintain the scripts:

This site is an independent documentation resource and cannot fix the scripts themselves.

Get MAS from the official project

This site does not host its own build of the scripts. The buttons below go to the project’s own repository and mirrors, so what you get is what the developers published.

PowerShell one-liner published by the project:

irm get.activated.win | iex

Check the domain before running it, and see how to verify what you run.

Activation tooling is routinely classified as riskware by antivirus software. That is expected for this category and is not by itself evidence of malware — nor proof that a particular copy is clean. Verify the source before running anything.