# memstechtips/unattendedwinstall architecture

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

- Interactive diagram: https://gitdiagram.com/memstechtips/unattendedwinstall
- Repository: https://github.com/memstechtips/unattendedwinstall

## Overview

##### Project Type and Purpose
- This is an infrastructure/customization tool rather than a full application. It is focused on automating Windows installations by modifying settings (registry tweaks, service configurations, removing bloatware, etc.) during setup.
- The answer file (autounattend.xml) represents the core engine that applies various Windows configuration customizations, while the UWScript.ps1 provides a way to reapply or revert these settings post-installation.

##### Major Components
a. Windows Installation Media
- Represents the official Windows ISO used as a base.
b. UnattendedWinstall Answer File (autounattend.xml)
- It as the central component that holds all configuration settings, customization instructions, registry tweaks, and scheduled task modifications.
- Role in being read during the Windows Setup process.
c. Configuration/Customization Scripts (UWScript.ps1)
- This as the supplementary execution tool for applying (or reapplying) settings to an already installed Windows system.
d. External Tools and Integration Points
- Although not housed in this repo, include supporting references such as:
- WIMUtil (for customizing ISOs and creating bootable media)
- Media tools (Rufus, AnyBurn, Ventoy) which are mentioned in the README to indicate usage scenarios.
- As external systems (or optional integration modules) that interact with the UnattendedWinstall process.
e. Documentation and Support Files

##### Relationships and Interactions
- A flow where the User (or System Administrator) takes a base Windows ISO, injects the autounattend.xml file into the root of that ISO (or USB media), and then boots the target system for Windows installation.
- During the Windows Setup process, the installer reads the answer file and applies the configuration customizations.
- After installation, the UWScript.ps1 can be executed (with administrator privileges) to ensure that any post-installation changes (or reinstallations of tweaks) are applied.

##### Highlighted Architectural Patterns and Design Principles
- Separation of Concerns: The answer file handles installation-time settings, while the PowerShell script manages post-installation adjustments.
- Modularity and Extensibility: The design supports additional customizations, registry tweaks, and integration with various external ISO modification and USB creation tools.
- Transparency and Auditability: All changes are visible within the answer file, making configuration transparent and verifiable.

##### Elements
- From “User/IT Admin” to “ISO Preparation Tools” (WIMUtil, Rufus, Ventoy).
- From “ISO with autounattend.xml” to “Windows Setup/Installation Process.”
- From “Windows Setup” to “Installed System.”
- From “Installed System” running “UWScript.ps1” for system tweaks.

## Diagram (Mermaid)

```mermaid
flowchart TD
    subgraph "Stage 1: ISO Preparation"
        A["User/IT Admin"]:::process
        B["WIMUtil (External Tool)"]:::external
        C["Rufus (External Tool)"]:::external
        D["Ventoy (External Tool)"]:::external
        E["Official Windows ISO"]:::external
        F["Inject autounattend.xml into ISO"]:::process
    end

    A --> F
    B --> F
    C --> F
    D --> F
    E --> F

    subgraph "Stage 2: Windows Setup Process"
        G["autounattend.xml – Answer File Engine"]:::input
        H["Windows Installation Process"]:::process
    end

    F --> G
    G --> H

    subgraph "Stage 3: Post-Installation Customizations"
        I["Installed Windows System"]:::process
        J["UWScript.ps1 – Post-Installation Script"]:::input
    end

    H --> I
    I --> J

    subgraph "Documentation & Support Files"
        K["README.md"]:::doc
        L["LICENSE.md"]:::doc
        M["CHANGELOG.md"]:::doc
        N["TROUBLESHOOTING.md"]:::doc
    end

    A --> K

    click G "https://github.com/memstechtips/unattendedwinstall/blob/main/autounattend.xml"
    click J "https://github.com/memstechtips/unattendedwinstall/blob/main/UWScript.ps1"
    click K "https://github.com/memstechtips/unattendedwinstall/blob/main/README.md"
    click L "https://github.com/memstechtips/unattendedwinstall/blob/main/LICENSE.md"
    click M "https://github.com/memstechtips/unattendedwinstall/blob/main/CHANGELOG.md"
    click N "https://github.com/memstechtips/unattendedwinstall/blob/main/TROUBLESHOOTING.md"

    classDef process fill:#a8e6cf,stroke:#000,stroke-width:1px;
    classDef input fill:#ffcc5c,stroke:#000,stroke-width:1px;
    classDef external fill:#96ceb4,stroke:#000,stroke-width:1px;
    classDef doc fill:#ff6f69,stroke:#000,stroke-width:1px;
```
