How sycnex/windows10debloater works
Project type and purpose
• This is an open-source PowerShell utility suite for “debloating” Windows 10.
• It offers three main user-facing interfaces:
• Interactive CLI (Windows10Debloater.ps1)
• GUI application (Windows10DebloaterGUI.ps1)
• Silent/Sysprep version with switches (Windows10SysPrepDebloater.ps1)
• Under the hood it orchestrates dozens of smaller scripts (the “Individual Scripts” folder) to remove preinstalled apps, tweak registry keys, disable tasks, etc.
Main components
a. User Interfaces
• PowerShell Console (Interactive CLI)
• PowerShell GUI Host (WinForms/WPF wrapper in the GUI script)
• Deployment Automation (silent SysPrep script with parameters)
b. Core Engine & Modules
• Core entrypoint scripts (Windows10Debloater*.ps1)
• Individual command modules (each .ps1 in “Individual Scripts”)
c. System APIs & Subsystems
• AppX Package Manager (Remove-AppxPackage, Remove-AppxProvisionedPackage)
• Windows Registry (Get/Set-ItemProperty for privacy keys)
• Task Scheduler (Disable-ScheduledTask)
d. External Services (minimal)
• Windows Update/Telemetry endpoints (indirectly through registry)
• Microsoft Store sources (for reinstall/revert operations)
Relationships and data flow
• User selects a script/interface → calls Core entrypoint → parses switches/prompts → invokes specific Individual Scripts modules → each module calls one or more OS subsystems (AppX, Registry, Scheduled Tasks) → returns status back up to UI.
• The silent SysPrep script is invoked by MDT or other deployment tools to run automatically without user interaction.
Architectural patterns & design principles
• Modular design: each “Individual Script” encapsulates one debloat or revert function.
• Layered separation:
• Presentation (CLI/GUI)
• Orchestration (entrypoint scripts)
• Domain modules (Individual Scripts)
• Infrastructure (OS APIs)
• Use of idempotent operations and switch parameters for repeatable automation.
Detailing components
• “Windows10DebloaterGUI.ps1” and “Windows10Debloater.ps1” as two separate UI blocks.
• “Windows10SysPrepDebloater.ps1” as an automation block with switch parameters (-SysPrep, -Debloat, -Privacy).
• “Individual Scripts” folder as a module library: list a few representative modules (e.g., Debloat, Remove-Keys, Protect-Privacy, Stop-EdgePDF, Revert-Changes).
• OS Subsystems cluster:
• AppX Package Manager
• Registry Hive (HKLM:\…, HKCU:\…)
• Task Scheduler Service
• Clear component labels (script names, module functions, OS subsystems)