mirror of
https://github.com/ChrisTitusTech/winutil.git
synced 2024-11-14 22:55:52 -06:00
Added MicroWin documentation (#2349)
* Add MicroWin documentation * Change style of headers of option types * Fixed typo of EdgeWebView2
This commit is contained in:
parent
e798ec9126
commit
b1e995fcaf
BIN
docs/assets/MicroWinScreen.png
Normal file
BIN
docs/assets/MicroWinScreen.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 102 KiB |
@ -81,6 +81,68 @@
|
|||||||
|
|
||||||
### MicroWin
|
### MicroWin
|
||||||
|
|
||||||
|
**MicroWin** lets you customize your Windows 10 and 11 installation images by debloating them however you want.
|
||||||
|
|
||||||
|
![MicroWin](assets/MicroWinScreen.png)
|
||||||
|
|
||||||
|
#### Basic usage
|
||||||
|
|
||||||
|
1. Specify the source Windows ISO to customize
|
||||||
|
|
||||||
|
* If you don't have a Windows ISO file prepared, you can download it using the Media Creation Tool for the respective Windows version. [Here](https://go.microsoft.com/fwlink/?linkid=2156295) is the Windows 11 version, and [here](https://go.microsoft.com/fwlink/?LinkId=2265055) is the Windows 10 version
|
||||||
|
|
||||||
|
2. Configure the debloat process
|
||||||
|
3. Specify the target location for the new ISO file
|
||||||
|
4. Let the magic happen!
|
||||||
|
|
||||||
|
**NOTE:** this feature is still in development and you may encounter some issues with the generated images. If that happens, don't hesitate to report an issue!
|
||||||
|
|
||||||
|
#### Options
|
||||||
|
|
||||||
|
* **Download oscdimg.exe from CTT GitHub repo** will grab a OSCDIMG executable from the GitHub repository instead of a Chocolatey package
|
||||||
|
|
||||||
|
OSCDIMG is the tool that lets the program create ISO images. Typically, you would find this in the [Windows Assessment and Deployment Kit](https://learn.microsoft.com/en-us/windows-hardware/get-started/adk-install)
|
||||||
|
|
||||||
|
* Selecting a scratch directory will copy the contents of the ISO file to the directory you specify instead of an automatically generated folder on the `%TEMP%` directory
|
||||||
|
* You can select an edition of Windows to debloat (**SKU**) using the convenient drop-down menu
|
||||||
|
|
||||||
|
By default, MicroWin will debloat the Pro edition, but you can choose any edition you want
|
||||||
|
|
||||||
|
|
||||||
|
##### Customization options
|
||||||
|
|
||||||
|
* **Keep Provisioned Packages**: leaving this option unticked (default) will try to remove every operating system package
|
||||||
|
|
||||||
|
Some packages may remain after processing. This can happen if the packages in question were permanent ones or had been superseded by newer versions
|
||||||
|
|
||||||
|
* **Keep Appx Packages**: leaving this option unticked (default) will try to remove every Microsoft Store app from the Windows image
|
||||||
|
|
||||||
|
This option will exclude some applications that are essential in the case that you want or need to add a Store app later on
|
||||||
|
|
||||||
|
* **Keep Defender**: leaving this option unticked will try to remove every part of Windows Defender, including the Windows Security app
|
||||||
|
|
||||||
|
Leaving this option unticked is **NOT recommended** unless you plan to use a third-party antivirus solution on your MicroWin installation. On that regard, don't install AVs with bad reputation or rogueware
|
||||||
|
|
||||||
|
* **Keep Edge**: leaving this option unticked will try to remove every part of the Microsoft Edge browser using the best methods available
|
||||||
|
|
||||||
|
Leaving this option unticked is not recommended because it might break some applications that might depend on the `Edge WebView2` runtime. However, if that happens, you can easily [reinstall it](https://developer.microsoft.com/en-us/microsoft-edge/webview2)
|
||||||
|
|
||||||
|
|
||||||
|
##### Driver integration options
|
||||||
|
|
||||||
|
* **Inject drivers** will add the drivers in the folder that you specify to the target Windows image
|
||||||
|
* **Import drivers from current system** will add every third-party driver that is present in your active installation
|
||||||
|
|
||||||
|
This makes the target image have the same hardware compatibility of the active installation. However, this means that you will only be able to install the target Windows image and take full advantage of it on computers with **the same hardware**. To avoid this, you'll need to customize the `install.wim` file of the target ISO in the `sources` folder
|
||||||
|
|
||||||
|
|
||||||
|
##### Ventoy options
|
||||||
|
|
||||||
|
* **Copy to Ventoy** will copy the target ISO file to any USB drive with [Ventoy](https://ventoy.net/en/index.html) installed
|
||||||
|
|
||||||
|
Ventoy is a solution that lets you boot to any ISO file stored in a drive. Think of it as having multiple bootable USBs in one. Do note though that your drive needs to have enough free space for the target ISO file
|
||||||
|
|
||||||
|
|
||||||
## Automation
|
## Automation
|
||||||
|
|
||||||
* Some features are available through automation. This allows you to save your config file pass it to Winutil walk away and come back to a finished system. Here is how you can set it up currently with Winutil >24.01.15
|
* Some features are available through automation. This allows you to save your config file pass it to Winutil walk away and come back to a finished system. Here is how you can set it up currently with Winutil >24.01.15
|
||||||
|
Loading…
Reference in New Issue
Block a user