Self-host KMS with py-kms (Docker) Aktivasyon Yöntemi 2026 — Tam Rehber

Overview

Self-host KMS with py-kms (Docker) is fully supported in the 2026 build of KMSAuto.software — free, portable, offline, no telemetry, no installer. This guide walks the exact steps that still work after Microsoft's 2026 licensing changes, with full commands, screenshots and fixes for every common error code on both consumer and Enterprise editions.

Step-by-step

Five steps, under two minutes from download to activated.

• Pause Windows Defender real-time protection for ~2 minutes
• Extract the ZIP with password to C:\Tools\KMSAuto
• Right-click KMSAuto.exe → Run as administrator
• Pick HWID for Windows, Ohook for Office, TSforge for Server/LTSC
• Wait for 'Successfully activated' and reboot

Supported editions

Covers every modern Microsoft product still in the wild.

• Windows 11 24H2 / 25H2 (Home, Pro, Enterprise, Education, LTSC, IoT)
• Windows 10 22H2 + LTSC 2021/2019
• Windows Server 2025 / 2022 / 2019 / 2016
• Office 2024 / 2021 / 2019 / 2016 LTSC + Retail
• Microsoft 365 Apps for Enterprise (Ohook patch)
• Project & Visio 2024 / 2021

Why this build

Original Ratiborus image — SHA-256 public, VirusTotal report public, ZIP password , no installer, no ads, no telemetry, no background service, no remote PowerShell. Each release is signed by the original author and mirrored from the official source.

Troubleshooting

90% of activation failures come from Defender quarantining the EXE mid-run, a stale KMS cache (slmgr /upk + slmgr /rilc), or picking the wrong product edition. Extract to a Defender exclusion folder (C:\Tools\KMSAuto), run elevated, choose HWID for Windows, Ohook for Office, TSforge for Server. For 0xC004F074 / 0xC004C003 / 0x80070005 see our error-code index.

Self-host KMS with py-kms (Docker) System Requirements & Compatibility (2026)

Self-host KMS with py-kms (Docker) is engineered for the modern Microsoft activation stack. The tool runs on Windows 7 SP1, Windows 8.1, Windows 10 (all builds from 1507 to 22H2) and every Windows 11 release including 23H2 and 24H2. Both x64 and ARM64 hardware are supported, and the activator also recognises Server SKUs such as Server 2016, 2019 and 2022. On the Office side, Click-to-Run installations of Office 2013, 2016, 2019, 2021, 2024 and Microsoft 365 are detected automatically — including LTSC channels. You do not need to uninstall a previous KMS client or remove an existing product key: the script reads the current edition through slmgr and routes it to the correct activation method (HWID for Windows, Ohook for Office).

• Windows 7 SP1 / 8.1 / 10 / 11 — all editions (Home, Pro, Education, Enterprise, IoT, LTSC)
• Windows Server 2008 R2 through Server 2025
• Office 2010, 2013, 2016, 2019, 2021, 2024 and Microsoft 365 Apps
• Architectures: x86, x64, ARM64
• .NET Framework 4.6+ (preinstalled on Windows 8.1 and later)

Self-host KMS with py-kms (Docker) Troubleshooting: Common Errors & Fast Fixes

Most Self-host KMS with py-kms (Docker) failures fall into three buckets: antivirus interference, missing administrator rights, or a corrupted Software Protection Service. If you see error 0xC004F074 the KMS host could not be contacted — disable Defender real-time scanning for two minutes, then re-run the activator. Error 0xC004C003 means the product key is blocked by Microsoft; switch to the HWID method, which bypasses key validation entirely by binding the licence to your motherboard's hardware ID. Error 0x80070005 (Access Denied) is always a UAC issue — right-click the executable and select "Run as administrator". If activation succeeds but reverts after reboot, open services.msc, set "Software Protection" to Automatic, and restart sppsvc.exe. For Office, run the Office Click-to-Run repair from Settings → Apps → Microsoft 365 → Modify → Quick Repair before retrying Ohook.

• 0xC004F074 — pause antivirus, re-run as administrator
• 0xC004C003 — switch to HWID (no key required)
• 0x80070005 — UAC denied, use "Run as administrator"
• Activation reverts on reboot — set "Software Protection" service to Automatic
• Office not detected — run Quick Repair, then re-run Ohook