mirror of
https://github.com/ChrisTitusTech/winutil
synced 2026-06-04 14:17:27 +00:00
Gabi
e6d8fdff75
* 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
828 B
828 B
title, weight, prev, next
| title | weight | prev | next |
|---|---|---|---|
| Automation | 7 | /userguide/updates/ | /userguide/win11Creator/ |
Use Automation to run Winutil from an exported configuration file.
To create a config file:
- Open Winutil.
- Click the gear icon in the top-right corner.
- Choose Export.
- Save the exported JSON file.
Once you have exported a config, launch Winutil with it using this command:
& ([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.