Office Activado Pide Activaci%c3%b3n

cscript ospp.vbs /unpkey:XXXXX   (replace XXXXX with last 5 chars of installed key from /dstatus)
cscript ospp.vbs /remhost

Then reactivate with:

cscript ospp.vbs /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
cscript ospp.vbs /act

| Symptom | Likely Cause | Best Solution | |---------|--------------|----------------| | “Activated” but “Activation needed” banner | Token corruption | Delete licensing folder → reactivate | | Works for days, then asks activation again | KMS expiration | Run ospp.vbs /act regularly via scheduled task | | Shows old user name but should be activated | Cached Microsoft account | Sign out → clear credential manager | | Happens after hardware change | Activation binding broken | Run Office repair → reactivate | | Multiple Office versions installed | Edition conflict | Uninstall all → reinstall one version |

For volume license editions (ProPlus, VL), KMS clients reactivate every 180 days. If they can’t reach the KMS host, they fall back to “activation required” state after a grace period.

Not all “activations” are permanent. Open Word → File → Account. Look under “Product Information”: office activado pide activaci%C3%B3n

| License type | Meaning | Typical fix | |-------------|---------|--------------| | Subscription (Microsoft 365) | Requires monthly/annual payment | Sign out and back in | | Retail (one-time purchase) | Permanent for 1 PC | Re-enter your key | | Volume (KMS) | Needs periodic re-activation (every 180 days) | Connect to your company’s network | | Non-genuine / crack | Likely blocked by update | Uninstall and buy a legitimate license |

If you see “KMS” or “Volume” and you are not in a large organization or school, your activation method is likely unsupported and will fail again soon.

Having both MSI-based and Click-to-Run Office versions installed causes this error. cscript ospp

Alternatively, use the Office Scrub script (search for “Microsoft Office uninstall support tool”).

Si no tienes acceso a Internet o prefieres activar por teléfono:

En entornos corporativos o educativos con KMS real, este error sucede porque el cliente no encuentra el servidor KMS en la red. Solución para administradores: Then reactivate with: cscript ospp

slmgr /skms dns:nombre-de-tu-servidor
slmgr /ato

Si el cliente se ha "caído" del grupo de volumen, ejecuta:

ospp.vbs /rearm

(permite 5 reactivaciones).