# Tiny11 Automated Builder: From Manual Scripting to CI/CD Automation

**Author:** kelexine  
**Date:** 2025-12-10  
**Category:** Windows  
**Tags:** Windows 11, PowerShell, CI/CD, Automation, Debloating, GitHub Actions  
**URL:** https://kelexine.is-a.dev/blog/tiny11-automated-builder

---

# Tiny11 Automated Builder: From Manual Scripting to CI/CD Automation

In the world of Windows customization, few projects have captured the imagination of power users quite like Tiny11. What started as a manual debloating script by the original author has evolved into a fully automated CI/CD pipeline that can generate optimized Windows 11 ISO images at the click of a button.

## The Origin Story: ntdevlabs' Tiny11

The Tiny11 project was originally created by **ntdevlabs**, a developer known for pushing the boundaries of what's possible with Windows customization. The original scripts (`tiny11maker-BASE.ps1` and `tiny11Coremaker-BASE.ps1`) were interactive PowerShell tools that allowed users to manually create lightweight Windows 11 installations.

These scripts gained popularity for their ability to:
- Remove over 40+ built-in Windows apps and bloatware
- Disable telemetry and privacy-invasive features
- Bypass Windows 11's stringent hardware requirements (TPM, CPU, RAM)
- Create significantly smaller Windows installations

However, the original tools required manual intervention, local Windows environments, and significant technical expertise to operate.

## The Inspiration: Why Automation?

As someone who frequently needed to deploy Windows in various scenarios - from VM testing environments to older hardware revival projects (All those are lies, i just love thinkering and f**king with stuffs) - I found myself spending countless hours manually running these scripts. The process was:

1. **Time-consuming**: Each ISO build took 50-160 minutes of active monitoring (Depending on host machine's power).
2. **Error-prone**: Missing a single prompt could break the entire build.
3. **Inconsistent**: Results varied based on the host system's configuration
4. **Inaccessible**: Required Windows with PowerShell and specific tools installed

The solution was clear: transform these manual scripts into an automated pipeline that could run anywhere, anytime, without human intervention.

## The Journey: From Script to CI/CD

### Phase 1: Headless Conversion

The first challenge was converting the interactive scripts into headless versions. This involved:

- **Removing all user prompts** and replacing them with command-line parameters
- **Implementing proper parameter validation** for ISO paths and image indices
- **Adding comprehensive logging** to track the build process
- **Creating error handling** that would fail gracefully and provide meaningful feedback

### Phase 2: GitHub Actions Integration

With headless scripts ready, the next step was creating GitHub Actions workflows. This enabled:

- **Cloud-based builds** that could run on manual trigger
- **Parallel processing** for different Windows editions and languages
- **ISO Image upload** to [SourceForge](https://sourceforge.net/projects/tiny-11-releases/) after modification and iso recreation is done.
- **Artifact storage** for generated ISO files (serves as fallback if SourceForge upload fails)
- **Automated releases** with proper versioning and naming conventions

### Phase 3: Optimization and Reliability

The final phase focused on making the builds reliable and efficient:

- **Caching mechanisms** for Windows ADK tools and dependencies
- **Retry logic** for network operations and DISM commands
- **Resource optimization** to fit within GitHub's runner constraints
- **Comprehensive testing** across different Windows versions

## Key Technical Achievements

### Registry Function Standardization

One major improvement was implementing a standardized `Set-RegistryValue` function that ensures all registry modifications are consistent and properly error-handled:

```powershell
function Set-RegistryValue {
    param([string]$path, [string]$name, [string]$type, [string]$value)
    # Standardized registry operations with error handling
}
```

### DISM Operation Optimization

The build process uses Deployment Image Servicing and Management (DISM) extensively. Key optimizations include:

- **Parallel component removal** to reduce build time
- **Incremental commits** to prevent data loss on failure
- **Proper cleanup** to avoid disk space issues

### Workflow Architecture

The CI/CD pipeline consists of two main workflows:

1. **Standard Tiny11 Build** (`build-tiny11.yml`)
   - Maintains Windows serviceability
   - Removes 40+ apps while keeping WinSxS intact
   - Suitable for general use

2. **Tiny11 Core Build** (`build-tiny11-core.yml`)
   - Aggressive WinSxS removal
   - Ultra-minimal footprint
   - No update capability (for VMs and old hardware only)

## Current Features

### Automated Build Process
- **One-click builds** via GitHub Actions
- **Multiple language support** (English, Spanish, French, German, Portuguese)
- **Customizable parameters** (Windows edition, .NET 3.5 inclusion, cleanup options)
- **Automatic release creation** with proper versioning

### Quality Assurance
- **ISO verification** after creation
- **MD5/SHA256 checksums** for integrity verification
- **Build logs** for troubleshooting
- **Rollback capabilities** on failure

### Distribution
- **GitHub Releases** with organized assets
- **Direct download links** for each build
- **Release notes** with build details
- **Version history** tracking

## The Results: Impact and Usage

Since implementing the automated pipeline:

- **Build time reduced** from ~2hrs minutes manual to 45-60 minutes automated
- **Success rate improved** from ~70% to ~95%
- **Consistency achieved** across all builds
- **Accessibility increased** - anyone can trigger a build

The project has attracted users (Just Me and whomever stumbles upon it) ranging from:
- **IT professionals** needing lightweight Windows for testing
- **Retro computing enthusiasts** reviving old hardware
- **VM administrators** requiring minimal Windows installations
- **Privacy-conscious users** wanting telemetry-free Windows

## Important Disclaimers and Warnings

⚠️ **Critical Security Notice**: This tool creates modified Windows images that:
- Remove Windows Defender completely (core builds)
- Disable Windows Updates (core builds)
- Bypass security requirements (TPM/CPU/RAM/SecureBoot)
- May violate Microsoft's Terms of Service
- Are intended for educational and testing purposes ONLY

⚠️ **Legal Considerations**:
- Users must have valid Windows licenses
- Generated ISOs should not be distributed commercially
- Use at your own risk - no warranty provided
- Not affiliated with Microsoft or ntdevlabs

⚠️ **Technical Limitations**:
- Tiny11 Core may not receive Windows Updates
- Some applications may not work properly
- Windows Defender is permanently removed (core builds)
- System restore points are disabled

## January 2026 Update: AI, Privacy, and Performance

The latest release brings significant improvements targeting the new Windows 11 25H2 update. We've gone deeper into optimization while maintaining stability.

### 1. Complete AI Removal
Windows 11 25H2 introduced deep integrations for Copilot, Recall, and AI Fabric. The latest Tiny11 update completely purges these components:
- **Copilot**: Removed from taskbar, registry, and AppX packages.
- **Windows Recall**: The controversial "snapshot" feature is fully nuked.
- **AI Fabric**: Background AI services are disabled and removed.

This saves approximately **220MB** per build and significantly reduces background processing.

### 2. Enhanced Privacy & Telemetry
We've expanded the telemetry blocking to include:
- **Device Name Exclusion**: Your device name is no longer sent in diagnostic data.
- **Feedback Notifications**: Completely disabled.
- **Enhanced Registry Tweaks**: Additional keys to block 25H2-specific tracking.

### 3. Gaming Optimizations
By popular demand, we've included VRAM and gaming-specific optimizations:
- **DirectX Registry Tweaks**: Optimized for lower overhead.
- **VRAM Allocation**: Improved settings for better gaming performance.
- **Service Removal**: Non-essential services (Diagnostics, Telemetry, etc.) are now disabled by default, freeing up CPU cycles.

## Future Roadmap

The project continues to evolve with planned improvements:

### Next Goals
- **ARM64 support** for Windows on ARM builds (🙃)
- **Additional language packs** for broader accessibility
- **Web interface** for easier build triggering (Bollocks)
- **Build notifications** via email/webhook (Maybe)

## Lessons Learned

### Technical Insights
1. **PowerShell's power** in automation cannot be overstated (still loves bash more)
2. **GitHub Actions** provide robust CI/CD capabilities for free
3. **Error handling** is critical in long-running processes
4. **Logging** saves countless debugging hours

### Project Management
1. **Start small** - automate one script at a time
2. **Test thoroughly** - edge cases will bite you
3. **Document everything** - future you will thank present you
4. **Community feedback** is invaluable for improvement

## Acknowledgments

This project stands on the shoulders of giants:

- **[ntdevlabs](https://github.com/ntdevlabs/tiny11builder)** for the original Tiny11 scripts
- **The Windows community** for testing and feedback (Just me again). **Don't like Windows by the way**
- **GitHub** for providing free CI/CD infrastructure
- **Microsoft** for PowerShell and Windows (even if they won't approve of this use case, and Shoving AI up our A$$es)

## Conclusion

The Tiny11 Automated Builder represents more than just a technical achievement - it's a testament to the power of open-source collaboration and automation. By transforming manual, error-prone processes into reliable, accessible workflows, we've made Windows customization available to everyone, regardless of their technical expertise.

Whether you're an IT professional needing quick Windows deployments or an enthusiast wanting to breathe life into old hardware, the automated pipeline delivers consistent, high-quality results at the click of a button.

The journey from manual scripts to full CI/CD automation demonstrates that with vision, persistence, and community support, even the most complex technical challenges can be solved. As the project continues to evolve, we remain committed to providing free, accessible tools for Windows customization while respecting the legal and ethical boundaries of software modification.

> NOTE: Not all images are tested, download and install at your own perils, or be a tester and provide feedback (I'd love that). Or you can push some PRs for Collaboration.

---

*Ready to try it yourself? Visit the [Tiny11 Automated Builder repository](https://github.com/kelexine/tiny11-automated) and trigger your first build today!*

## Download Pre-built ISOs

If you prefer not to build the ISOs yourself, pre-built Tiny11 images are available for download:

**SourceForge Downloads**: [Click Here](https://sourceforge.net/projects/tiny-11-releases/)

This mirror provides ready-to-use Tiny11 ISO files built using the automated pipeline, saving you time and computational resources.

**Developer**: Franklin Kelechi [@kelexine](https://github.com/kelexine/)
**Project Repository**: [Tiny11 Builder](https://github.com/kelexine/tiny11-automated)
**Original Author**: [ntdevlabs](https://github.com/ntdevlabs/tiny11builder)

---

<div class="glass-effect p-6 rounded-xl border border-white/10 my-8">

**🚀 Visit the Project Homepage**: [Tiny11 Project Page](/tiny11) — Explore the complete Tiny11 builder platform with an interactive overview of features, build statistics, and quick access to all resources in one place.

**🔥 Want even more extreme?** Check out the [Nano11 Project Page](/nano11) — Our most aggressively stripped Windows 11 with ~1.5GB ISO and ~5GB installed size.

</div>

---

*This content is available at [kelexine.is-a.dev/blog/tiny11-automated-builder](https://kelexine.is-a.dev/blog/tiny11-automated-builder)*