jlammi/winutil
1
0
Fork 0
mirror of https://github.com/ChrisTitusTech/winutil synced 2026-02-07 08:20:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove microwin (#3999)

Browse Source 
* Delete microwin functions

* Update main.ps1

* Remove oscdimg.exe which is used by microwin

* Delete config/autounattend.xml

* Update .gitignore

* Update bug_report.yaml

* Update themes.json

* Update Invoke-WinUtilFontScaling.ps1

* Update Invoke-AutoConfigDialog.ps1

* Update Invoke-WPFButton.ps1

* Update inputXML.xaml

* Delete docs/assets/images/microwin directory

* Delete docs/assets/images/MicroWinScreen.png

* Delete docs/assets/images/Microwin-Dark.png

* Delete docs/assets/images/Microwin-Light.png

* Update faq.md

* Update KnownIssues.md

* Update getting-started.md

* Update _index.md

* Delete docs/content/userguide/microwin directory

* Update architecture.md

---------

Co-authored-by: Chris Titus <dfm.titus@gmail.com>
This commit is contained in:
Gabi
2026-02-06 18:29:10 +02:00
committed by GitHub
parent ac116d7083
commit fcc5481477
42 changed files with 7 additions and 3270 deletions
Download Patch File Download Diff File Expand all files Collapse all files

45
docs/content/KnownIssues.md
View File

@@ -43,51 +43,6 @@ If you are still having issues, try using a **VPN**, or changing your **DNS prov
If you have not installed anything using PowerShell before, you may be prompted to configure WinGet. This requires user interaction on first run. You will need to manually type `y` into the PowerShell console and press enter to continue. Once you do it the first time, you will not be prompted again.
### MicroWin: Error `0x80041031`
This error code typically indicates an issue related to Windows Management Instrumentation (WMI). Here are a few steps you can try to resolve the issue:
1. **Reboot Your Computer:**
Sometimes, a simple reboot can resolve temporary issues. Restart your computer and try mounting the ISO again.
2. **Check for System Corruption:**
Run the System File Checker (SFC) utility to scan and repair system files that may be corrupted.
```powershell
sfc /scannow
```
3. **Update Your System:**
Make sure your operating system is up-to-date. Check for Windows updates and install any pending updates.
4. **Check WMI Service:**
Ensure that the Windows Management Instrumentation (WMI) service is running. You can do this through the Services application:
- Press `Win`+`R` to open the Run dialog.
- Type `services.msc` and press Enter.
- Locate _Windows Management Instrumentation_ in the list.
- Make sure to set its status to "Running" and the startup type to "Automatic".
5. **Check for Security Software Interference:**
Security software can sometimes interfere with WMI operations. Temporarily disable your anti-virus or security software and check if the issue persists. WMI is a common attack/infection vector, so many anti-virus programs will limit its usage.
6. **Event Viewer:**
Check the Event Viewer for more detailed error information. Look for entries related to the `80041031` error and check if there are any additional details that can help identify the cause.
- Press `Win`+`X` and select _Event Viewer_.
- Navigate to _Windows Logs_ > _Application_ or _System_.
- Look for entries with the source related to WMI or the application use to mount the ISO.
7. **ISO File Integrity:**
Ensure that the ISO file you are trying to mount is uncorrupted. Try mounting a different ISO file to see if the issue persists.
If the problem persists after trying these steps, additional troubleshooting is required. Consider seeking assistance from Microsoft support or community forums for more specific guidance based on your system configuration and the software you use to mount the ISO.
## Windows Issues
### Windows takes longer to shut down

21
docs/content/dev/architecture.md
View File

@@ -55,9 +55,6 @@ winutil/
│ ├── public/ # User-facing functions
│ │ ├── Initialize-WPFUI.ps1
│ │ └── ...
│ └── microwin/ # MicroWin specific functions
│ ├── Invoke-Microwin.ps1
│ └── ...
├── config/ # JSON configuration files
│ ├── applications.json # Application definitions
│ ├── tweaks.json # Tweak definitions
@@ -126,7 +123,6 @@ winutil/
**Purpose**: WPF GUI layout and design.
**Structure**:
- TabControl for main tabs (Install, Tweaks, Config, MicroWin)
- Buttons with event handlers
- TextBoxes for input
- CheckBoxes for options
@@ -320,22 +316,6 @@ if (!(Get-Command choco -ErrorAction SilentlyContinue)) {
choco install $app.choco -y
```
## MicroWin Architecture
MicroWin operates in phases:
1. **Mount ISO**: Extract Windows image
2. **Modify Image**: Remove components, apply tweaks
3. **Inject Drivers**: Add custom drivers (optional)
4. **Create Unattend**: Generate automated install configuration
5. **Rebuild ISO**: Package modified image into new ISO
**Key Files**:
- `Invoke-Microwin.ps1`: Main orchestration
- `Microwin-RemovePackages.ps1`: Remove Windows packages
- `Microwin-RemoveFeatures.ps1`: Disable features
- `Microwin-NewUnattend.ps1`: Create unattend.xml
## Error Handling
Winutil uses PowerShell error handling:
@@ -489,7 +469,6 @@ Outputs `winutil.ps1` in the root directory.
**Optional (auto-installed)**:
- WinGet (Windows Package Manager)
- Chocolatey
- oscdimg.exe (for MicroWin)
## Performance Considerations

24
docs/content/faq.md
View File

@@ -128,25 +128,6 @@ Winutil focuses on installation. To uninstall:
### Will installed apps auto-update?
Applications with built-in update mechanisms will auto-update. You can also update them via WinGet/Chocolatey commands or through Winutil's "Upgrade Selected" feature.
## MicroWin
### What is MicroWin?
MicroWin is a feature that creates custom Windows installation ISOs with bloatware removed, optimizations applied, and unnecessary components stripped out before installation.
### Is MicroWin legal?
Modifying Windows ISOs is a gray area legally. Use MicroWin for personal/educational purposes. You still need a valid Windows license to use the resulting installation.
### Can I install Windows updates on MicroWin?
Yes, Windows Update works normally on MicroWin installations. Some removed components may be restored by updates.
### How much smaller is a MicroWin ISO?
Depends on what you remove. Typically:
- Standard Windows 11: ~5.5 GB ISO, ~20-25 GB installed
- MicroWin (aggressive): ~3.5 GB ISO, ~10-15 GB installed
### Will all software work on MicroWin?
Most desktop applications work fine. Microsoft Store apps won't work if you removed the Store. Some features may be missing if you removed their dependencies.
## Updates & Maintenance
### Should I disable Windows Updates?
@@ -277,11 +258,6 @@ Winutil itself uses ~50-100MB while running. Once closed, it's removed from memo
- Check if antivirus is blocking changes
- Verify you have ownership of files/registry keys
### "File not found" errors during MicroWin
- Verify source ISO isn't corrupted
- Ensure sufficient disk space (20GB+)
- Check ISO is an official Windows ISO
### WinGet configuration prompt won't go away
Type `Y` and press Enter in the PowerShell window. This only happens on first use and configures WinGet for your system.

9
docs/content/userguide/_index.md
View File

@@ -13,7 +13,6 @@ Winutil (Chris Titus Tech's Windows Utility) is a comprehensive PowerShell-based
- **Apply Tweaks**: Optimize Windows for performance, privacy, and usability
- **Fix Issues**: Troubleshoot common Windows problems with one-click fixes
- **Manage Updates**: Control how and when Windows updates install
- **Create MicroWin**: Build custom, lightweight Windows installation ISOs
- **Access Tools**: Quick access to Windows panels and utilities
## Who Should Use Winutil?
@@ -60,12 +59,6 @@ Quick fixes for common Windows problems:
**[Read the Features Guide →](features/)**
### 🪟 MicroWin
Create custom Windows installation ISOs with bloatware removed, optimizations pre-applied, and unnecessary components stripped out.
**[Read the MicroWin Guide →](microwin/)**
### 🔄 Update Management
Take control of Windows Updates with options to:
@@ -94,7 +87,6 @@ Automate Winutil configurations for:
| Install applications quickly | [Application Store](store/) |
| Speed up my computer | [Tweaks Guide](tweaks/) |
| Fix Windows Update problems | [Features - Fixes](features/) |
| Create a lightweight Windows ISO | [MicroWin](microwin/) |
| Automate setup for multiple PCs | [Automation](automation/) |
| Understand what tweaks do | [Tweaks Guide](tweaks/) |
@@ -154,7 +146,6 @@ This User Guide covers everything you need to know:
2. **[Application Store](store/)** - Installing software, using presets
3. **[Tweaks](tweaks/)** - System optimizations and customizations
4. **[Features & Fixes](features/)** - Troubleshooting tools and utilities
5. **[MicroWin](microwin/)** - Creating custom Windows ISOs
6. **[Updates](updates/)** - Managing Windows Update behavior
7. **[Automation](automation/)** - Scripting and batch deployments

2
docs/content/userguide/getting-started.md
View File

@@ -91,7 +91,6 @@ Winutil opens with a clean, tabbed interface:
- **Tweaks**: Apply system optimizations and customizations
- **Config**: Access system tools and utilities
- **Updates**: Manage Windows updates
- **MicroWin**: Create custom, lightweight Windows ISOs
## Your First Actions
@@ -261,7 +260,6 @@ Now that you're set up, explore these guides:
- [Application Installation Guide](../store/) - Learn about installing software
- [Tweaks Guide](../tweaks/) - Understand system optimizations
- [MicroWin Guide](../microwin/) - Create custom Windows ISOs
- [FAQ](../../faq/) - Common questions and answers
## Getting Help

162
docs/content/userguide/microwin/_index.md
View File

@@ -1,162 +0,0 @@
---
title: Microwin
weight: 6
---
MicroWin is our in-house solution for customized and debloated Windows images. With MicroWin, you can create images that have minimal bloat and no interruptions. This has an upside: you can get more done and use Windows the way **you** want.
Due to MicroWin using standard Windows system administration tools, such as DISM (Deployment Image Servicing and Management), advanced Windows users (system administrators and tech enthusiasts) can continue making changes so that they can have their own set of customizations with their ISO files.
If you're excited to try this out, let's go through how to use it. You'll be done in a short time!
## Basic usage
To start with MicroWin, go to its tab. You will see the following:
{{< image src="images/microwin/microwin-screen" >}}
From this screen, you'll have to do one of the following:
- **Select the ISO file:** if you have already downloaded a Windows ISO file, select it and click OK
- **Get an ISO file automatically:** if you don't have an ISO file ready, and don't want to waste time going to the download page, you can grab the latest versions of Windows easily. Select your preferred version and the language of the ISO file, and its destination, and you will have an ISO file in no time.
{{< image src="images/microwin/microwin-downloader" >}}
> [!NOTE]
> When downloading your ISO file, network conditions (such as speed and location) can affect the time you have to wait for the download to complete and the availability of such download.
### Compatibility
You may be wondering if your Windows image is compatible with the MicroWin process. Because of this, we present to you a compatibility list:
| Version | Compatible? |
| :---------- | :----------------------------------------------------- |
| Windows 7 | ❌ Not supported |
| Windows 8 | ❌ Not supported |
| Windows 8.1 | ❌ Not supported |
| Windows 10 | ❌ Not supported, But may work on the latest versions. |
| Windows 11 | 👍 Supported (21H2-25H2) |
After getting information about your ISO file, you will see the following screen:
{{< image src="images/microwin/microwin-screen-full" >}}
### Requirements
To successfully use MicroWin with your Windows image, you need the following:
- **The latest versions of Windows 11**
- **Enough space**. We recommend having, at least, double the size of your ISO file. However, you may need more if you want to inject drivers
## Options
### Choosing your index
By default, MicroWin will target the Pro edition of Windows. The Pro edition is a good baseline for IT administrators **and** end-users, due to the inclusion of Group Policy, the ability to join domains, and more things that you can't find with the Home edition. For more information, check out [this comparison chart](https://en.wikipedia.org/wiki/Windows_11_version_history).
Obviously, you should pick the edition of Windows for which you have a license. To change the edition to process, select the drop-down menu under "Choose Windows SKU" and select your edition.
{{< image src="images/microwin/microwin-skuselect" >}}
### Injecting drivers
If you want to use MicroWin on a real system, you may want to include the drivers for it, to avoid setting them up after OS installation. That's where the options to inject drivers come in handy.
- **Injecting drivers:** if you want to install MicroWin on another system, simply check this option. Prepare a folder with the drivers of your system and specify it in the UI. To learn more about how to export the drivers, read the section "Exporting drivers"
- **Importing drivers:** if you want to install MicroWin on **your** system, you can apply the drivers of your system to the image by importing them. Combine that with the former option, and you can have your driver files stored permanently on your preferred location
- **Injecting VirtIO drivers:** if you plan on using the target Windows image with QEMU/Proxmox VE, or any UI that uses it (like `virt-manager` on Linux), you can automatically download the VirtIO driver ISO and put its contents into your ISO file
> [!NOTE]
> Injecting VirtIO drivers is only supported on v25.01.11 and later
Of course, you can continue without setting up drivers. Simply leave the options blank and continue with the process.
#### How do I export drivers?
To export the drivers, you can do the following on many utilities:
##### DISM
To export the drivers using DISM (via the command-line), do the following:
1. Launch the command-line interpreter you want (`cmd`, PowerShell...) **as an administrator**
2. Go to where you want to place the drivers with `cd`, and create a directory called "drivers" (`md drivers`)
3. Run the following command: `dism /online /export-driver /destination="<path-to-folder>"`
4. Wait for the drivers to be exported
##### Driver Store Explorer (RAPR)
To export the drivers using [Driver Store Explorer (RAPR)](https://github.com/lostindark/DriverStoreExplorer/), do the following:
1. Go to "File > Export All Drivers"
{{< image src="images/microwin/rapr_menu" >}}
2. Choose the folder to export all the drivers to and click OK
{{< image src="images/microwin/rapr_folderpicker" >}}
##### DISM++
To export the drivers using [DISM++](https://github.com/Chuyu-Team/Dism-Multi-language), do the following:
1. Select your active installation if you haven't (it's the first item)
2. Go to "Drivers", select "All" and select "Export"
{{< image src="images/microwin/dism++_drivercontrol" >}}
3. Choose the folder to export all the drivers to and click OK
{{< image src="images/microwin/dism++_driverexport" >}}
##### DISMTools
To export the drivers using [DISMTools](https://github.com/CodingWonders/DISMTools), do the following:
1. Select "Manage online installation" in the home screen and accept the warning
{{< image src="images/microwin/dt_activeinst" >}}
2. Go to "Commands > Drivers > Export driver packages..."
{{< image src="images/microwin/dt_exportdrvs" >}}
3. Choose the path to export the drivers to ("Export target") and click OK
{{< image src="images/microwin/dt_exporttarget" >}}
##### Other UIs
To export the drivers using another UI, read its documentation.
#### Using VirtIO drivers
After the drivers from the Ventoy ISO are copied, do the following if you can't see any drives on your QEMU VM:
1. In the disk selection screen, select "Load driver"
2. Click "Browse" and select `D:\VirtIO\vioscsi\w11\amd64` (replace `amd64` with `ARM64` if you want to use Windows on ARM)
3. Select all drivers in the list and click OK
You should be able to see your disks now.
### Copying to Ventoy
If you have a Ventoy drive, you can copy your ISO file to it quickly and easily. This is done after it has been created. To do this, simply check "Copy to Ventoy".
You can learn more about Ventoy drives [here](https://www.ventoy.net/en/index.html).
> [!NOTE]
> Newer versions of MicroWin images may have compatibility issues with ventoy.
### Setting up a custom user
If you want to set up a custom user, effectively creating a completely unattended installation, you can set up a user name and password:
{{< image src="images/microwin/microwin-customuser" >}}
> [!NOTE]
> To set up a custom user, you need to specify its name, which cannot surpass 20 characters. Otherwise, a user named "User" will be created. However, you don't need to set up a password. If you leave the password box blank, you can take advantage of auto-logons, but **do what you think it's best for your use case**.
After configuring all your desired settings, click "Start the process" and specify the location of your ISO file.
Now, you have to wait for the magic to happen. This can take between 5-10 minutes, but it depends on the performance of your computer.