PatchW11 (Core Version of WinAuto)

Enterprise-grade Windows 11 configuration management in a single, self-contained PowerShell file.

PatchW11 is the core, standalone delivery of the full WinAuto suite. It is a powerful, lightweight automation script designed to streamline configuration, security hardening, and maintenance of Windows 11 systems—consolidated entirely into one interactive file.

🚀 Key Features

• Interactive Dashboard: A modern, arrow-key driven CLI interface for manual and automated operations.
• SmartRUN Automation: Intelligent orchestration that audits system state and only applies changes where configuration drift is detected.
• Security Hardening: Automates Microsoft Defender, Memory Integrity, Kernel Stack Protection, LSA Protection, App & browser control, and Windows Firewall.
• Application Management: Built-in application setups utilizing WinGet and direct downloads with silent deployment.
• Automated Maintenance: One-touch system repair (SFC/DISM), drive optimization, and temp file cleanup.
• UI Automation: Robust handling of Windows Settings that cannot be managed via the registry alone.

🛠️ Usage

1. Elevate: Open a PowerShell window as Administrator.
2. Run: Execute the core script:

   .\PatchW11.ps1

3. Navigate: Use the ^ and v arrow keys to select sections.
4. Execute: Press Space to run the selected section or SmartRUN.
5. Info: Press I to view the functional outline. From the Info page, press Enter to export a technical CSV map or Esc to return to the dashboard.

📁 Repository Structure

Unlike the full WinAuto suite, the PatchW11 repository relies on a strictly single-file architecture:

• PatchW11.ps1: The complete standalone core script comprising the interactive dashboard and all automation logic. No external dependencies or separate folders required.

🛡️ Requirements

• Operating System: Windows 11 (Build 22000+)
• Privileges: Administrator
• Execution Policy: Set to RemoteSigned (handled automatically by the script).

⚖️ Disclaimer

1. Test First: Always run in a non-production environment first.
2. Back up: Critical data should be backed up before running maintenance tasks.
3. Responsibility: The authors are not responsible for any system instability or data loss.

---

Maintained by KeithOwns | Open Source MIT License