jlammi/winutil
1
0
Fork 0
mirror of https://github.com/ChrisTitusTech/winutil synced 2026-04-06 06:38:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

removed windows 10 reference and pages edits (#4185)

Browse Source 
* removed any windows 10 reference

* update links

* page clean up

* Update _index.md

* clean up getting started page

* clean up more pages

* Update faq.md

* Update _index.md

* more clean up
This commit is contained in:
Sean (ANGRYxScotsman)
2026-03-11 15:24:46 +00:00
committed by GitHub
parent a30664002b
commit 3da0221fb4
10 changed files with 143 additions and 108 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/content/userguide/automation/_index.md
View File

@@ -3,11 +3,25 @@ title: Automation
weight: 7
---
The Automation option in Winutil allows you to run Winutil from an exported config file.
Use Automation to run Winutil from an exported configuration file.
You can create your own config in the app by clicking the gear icon in the top-right corner, then choosing Export and saving the file.
To create a config file:
You can automate Winutil launch with this command:
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" -Run
```
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.