Files
winutil/docs/content/userguide/automation/_index.md
T
Gabi e6d8fdff75 fix import (#4447)
* Made -Config use Runspaces main.ps1

* Fix no-UI config autorun

* Skip empty no-UI autorun sections

* Update Invoke-WinUtilAutoRun.ps1

* Ignore blank DNS selection during autorun

* Update main.ps1

* Update Invoke-WPFRunspace.ps1

* Update Invoke-WPFRunspace.ps1

* Update Invoke-WinUtilAutoRun.ps1

* Update Invoke-WinUtilAutoRun.ps1

* Update Invoke-WPFtweaksbutton.ps1

* Update start.ps1

* Update main.ps1

* Update Invoke-WPFtweaksbutton.ps1

* Update Invoke-WPFRunspace.ps1

* Update _index.md

* Merge branch 'ChrisTitusTech:main' into patch-3

* Merge branch 'ChrisTitusTech:main' into patch-3
2026-05-12 12:58:46 -05:00

30 lines
828 B
Markdown

---
title: Automation
weight: 7
prev: /userguide/updates/
next: /userguide/win11Creator/
---
Use Automation to run Winutil from an exported configuration file.
To create a config file:
1. Open Winutil.
2. Click the gear icon in the top-right corner.
3. Choose **Export**.
4. Save the exported JSON file.
Once you have exported a config, launch Winutil with it using this command:
```powershell
& ([ScriptBlock]::Create((irm "https://christitus.com/win"))) -Config "C:\Path\To\Config.json"
```
This is useful for:
- Applying the same Winutil configuration across multiple Windows 11 PCs
- Reusing a known-good baseline after reinstalling Windows
- Standardizing deployments for labs, workstations, or personal setups
> [!NOTE]
> Run the command in an elevated PowerShell session so Winutil can apply system-level changes.