Resource center

Microsoft software resources

Official ISO downloads, product-key format references, deactivation walkthroughs and an activation-error lookup table.

Everything below points to a Microsoft-hosted file, a Microsoft Learn article, or a reproducible PowerShell command. We do not host installers, cracks or pre-activated images — only the original sources, indexed and explained.

Our sourcing policy

We refresh every link the first Monday of each month and remove any URL that has redirected to a marketing page. Tables and PowerShell snippets are re-tested on a clean Windows 11 24H2 build with the latest cumulative update before publishing.

How to use the resource centre

A Microsoft licence problem is almost always one of four things: the wrong installation media, a key in the wrong format, a licence still bound to a machine you no longer own, or an activation error code you have not looked up yet. The resource centre is organised around exactly those four failure points, so you can start from the symptom rather than from the product name.

Every download link points at a Microsoft-hosted file. Every command is PowerShell you can paste into an elevated prompt and read before you run it. Nothing here requires a third-party tool, a registry hack or a downloaded activator — if a page ever tells you otherwise, it is not one of ours.

4
reference areas: media, keys, deactivation, errors
12
activation error codes with fixes
Monthly
link and hash re-verification
0
third-party tools required

Start from your symptom

Match what you are seeing on screen to the resource that solves it. Most tickets we receive are resolved by one of these five rows.

SymptomMost likely causeWhere to go
Setup refuses the key you boughtMedia edition does not match the key edition (Home vs Pro, retail vs volume)Official ISO downloads
Key looks wrong (too short, has dashes in odd places)You have an installation ID, a digital-entitlement receipt or a MAK, not a retail keyProduct key formats
"This key is already in use"The licence is still activated on a previous deviceDeactivation walkthroughs
A numeric code such as 0xC004C003Server-side activation rejection, usually recoverableActivation error lookup
Office installs but says "unlicensed product"Signed in with the wrong Microsoft account, or a stale Office licence tokenActivation error lookup

Pre-flight checklist before you install

  • Confirm the edition on your invoice matches the ISO you are about to download — Home keys will not activate a Pro install.
  • Compare the SHA-256 hash Microsoft publishes with the hash of your downloaded file before mounting it.
  • Deactivate the licence on the old machine first if you are moving a retail licence, not after.
  • Note your Windows build (winver) — some activation errors only occur on specific cumulative updates.
  • Have the invoice number to hand; support can re-issue a key in minutes with it and not at all without it.
  • Disconnect VPNs during activation — a mismatch between billing country and exit node triggers avoidable rejections.

Resource centre FAQ

Do you host the ISO files yourself?
No. Every download link resolves to microsoft.com, learn.microsoft.com or aka.ms. We index and explain the official sources; we never mirror, repackage or pre-activate installation media.
How do I verify an ISO is genuine?
Microsoft publishes a SHA-256 hash next to each download. On Windows run Get-FileHash .\file.iso -Algorithm SHA256 in PowerShell and compare the two strings character for character. If they differ, delete the file.
Can I reuse a retail key on a new computer?
Yes. A retail licence is transferable once it has been deactivated on the previous device. OEM licences are permanently bound to the original motherboard and cannot be moved.
Why does my key fail with error 0xC004C008?
That code means the key has been activated more times than its licence allows. Deactivate the older installation, wait for the server-side counter to clear, then retry — or contact us with your invoice for a re-issue.
Are the PowerShell commands safe to run?
They are read-only or licence-scoped commands from Microsoft's own documentation (slmgr, Get-FileHash, DISM). Each page states what the command changes before you run it, and none of them touch personal data.
How current is this material?
Links and hashes are re-verified on the first Monday of each month, and every table is re-tested on a clean Windows 11 24H2 build with the latest cumulative update installed.

Related reading