# nirevil/windows-activation architecture

> Architecture diagram of the GitHub repository nirevil/windows-activation, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-03-29). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/nirevil/windows-activation
- Repository: https://github.com/nirevil/windows-activation

## Overview

##### Main Components
- User’s Windows Machine – This is the client executing commands.
- Command Interface – Represent this as two options (PowerShell & CMD) since the process is executed via these shells.
- External Activation Service – Show the interaction with external resources:
◦ Activation Script Host (get.activated.win): for method 1, where a script is dynamically downloaded and executed.
◦ KMS Server (kms8.msguides.com): which is contacted to verify and complete the activation.

##### Relationships and Data Flow
◦ The initial trigger: “User initiates command interface”.
◦ For Method 1: Flow from the command interface to “Download & Execute Activation Script” (via get.activated.win), then to “KMS Server” for completing activation, and finally back to update Windows activation status.

##### Architectural Patterns and Design Principles
- Command-driven, sequential nature of the process.
- Make it clear that the activation process depends on communication with external servers to validate and activate the OS.

##### Integrate Relevant Technologies
- Mention Windows OS (including the versions supported: Home, Pro, Education, Enterprise, etc.).
- That PowerShell and CMD are the two primary interfaces.
- Labels for external URLs (https://get.activated.win and kms8.msguides.com) to show dependency on remote resources.
- That the commands use the slmgr utility, which is specific to Windows activation.

##### Suggested Elements
- Labels for each component:
◦ User’s Device (with Windows 10/11)
◦ PowerShell & CMD interfaces (show branching options)
◦ Activation Script Execution (via get.activated.win)
◦ KMS Activation Server (kms8.msguides.com)
◦ Initiation by user
◦ Command execution flow
◦ Interaction with external services and return feedback for activation.
◦ Local execution environments (PowerShell/CMD)
◦ Remote dependencies (activation script host, KMS server)
◦ Commands or actions (e.g., license installation, KMS address setting, final activation check).

## Diagram (Mermaid)

```mermaid
flowchart TD
    U["User's Windows Machine (Windows 10/11)"]:::local

    %% Branching for Method 1 (PowerShell)
    U --> PS["Open PowerShell"]:::local
    PS --> PS2["Download & Execute Activation Script"]:::local
    PS2 --> DS["Download Script (get.activated.win)"]:::external
    DS --> KMS["Contact KMS Server (kms8.msguides.com)"]:::external

    %% Branching for Method 2 (CMD)
    U --> CMD["Open CMD"]:::local
    CMD --> CMD2["Install License Key (slmgr /ipk)"]:::local
    CMD2 --> CMD3["Set KMS Address"]:::local
    CMD3 --> CMD4["Activate OS (slmgr /ato)"]:::local
    CMD4 --> KMS

    %% Convergence to final activation confirmation
    KMS --> AS["Activation Successful"]:::local

    %% Documentation subgraph
    subgraph "Documentation"
        A1["Activation Instructions"]:::doc
        A2["Supplementary Activation Documentation"]:::doc
        A3["Licensing Information"]:::doc
    end

    %% Click Events
    click A1 "https://github.com/nirevil/windows-activation/blob/main/README.md"
    click A2 "https://github.com/nirevil/windows-activation/blob/main/README-FA.md"
    click A3 "https://github.com/nirevil/windows-activation/tree/main/LICENSE"

    %% Class Definitions for styling
    classDef local fill:#cfe2f3,stroke:#084298,stroke-width:2px;
    classDef external fill:#f8d7da,stroke:#842029,stroke-width:2px;
    classDef doc fill:#d1e7dd,stroke:#0f5132,stroke-width:2px;
```
