Bump version

* remove support for uninstalling old sunset apps

* Add color legend on app removal screen

* Remove legacy app list generator and custom apps file support
Replaced by GUI config export/import, dynamic RemovalMethod, and
CLI app removal settings saved to LastUsedSettings.json.

* Verify app removal by checking actual installation state instead of trusting winget output

.github/CONTRIBUTING.md

@@ -1,6 +1,7 @@
 # How to Contribute?
 
 We welcome contributions from the community. You can contribute to Win11Debloat by:
+
 - Reporting issues and bugs [here](https://github.com/Raphire/Win11Debloat/issues/new?template=bug_report.yml)
 - Submitting feature requests [here](https://github.com/Raphire/Win11Debloat/issues/new?template=feature_request.yml)
 - Testing Win11Debloat
@@ -15,6 +16,7 @@ You can help us test the latest changes and additions to the script. If you enco
 > The prerelease version of Win11Debloat is meant for developers to test the script. Don't use this in production environments!
 
 You can launch the prerelease version of Win11Debloat by running this command:
+
 ```ps1
 & ([scriptblock]::Create((irm "https://debloat.raphi.re/dev")))
 ```
@@ -28,12 +30,14 @@ You can launch the prerelease version of Win11Debloat by running this command:
 1. **Fork the project** on GitHub by clicking the "Fork" button at the top right of the repository page.
 
 2. **Clone the repository** to your local machine:
+
    ```powershell
    git clone https://github.com/YOUR-USERNAME/Win11Debloat.git
    cd Win11Debloat
    ```
 
 3. **Create a new branch** for your contribution:
+
    ```powershell
    git checkout -b feature/your-feature-name
    ```
@@ -42,11 +46,14 @@ You can launch the prerelease version of Win11Debloat by running this command:
 
 1. Open PowerShell as an administrator
 2. Enable script execution if necessary:
+
    ```powershell
    Set-ExecutionPolicy Unrestricted -Scope Process -Force
    ```
+
 3. Navigate to your Win11Debloat directory
 4. Run the script:
+
    ```powershell
    .\Win11Debloat.ps1
    ```
@@ -57,18 +64,31 @@ You can launch the prerelease version of Win11Debloat by running this command:
 
 Understanding the project structure is essential for contributing effectively:
 
-```
+```text
 Win11Debloat/
 ├── Win11Debloat.ps1             # Main PowerShell script
+├── Run.bat                      # Batch launcher for the quick launch method
 ├── Scripts/                     # Additional PowerShell scripts and functions
-│    └── Get.ps1                 # Script used for the quick launch method to automatically download and run Win11debloat
+│   ├── Get.ps1                  # Script used for the quick launch method to automatically download and run Win11debloat
+│   ├── AppRemoval/              # App package removal logic
+│   ├── CLI/                     # Command-line interface helpers
+│   ├── Features/                # Feature apply/undo logic (e.g. InvokeChanges.ps1, ReplaceStartMenu.ps1)
+│   ├── FileIO/                  # File input/output helpers
+│   ├── GUI/                     # GUI window definitions and logic
+│   ├── Helpers/                 # Shared helper functions
+│   └── Threading/               # Threading utilities
 ├── Config/
 │   ├── Apps.json                # List of supported apps for removal
 │   ├── DefaultSettings.json     # Default configuration preset
 │   ├── Features.json            # All features with metadata
 │   └── LastUsedSettings.json    # Last used configuration (generated during use)
-├── Regfiles/                    # Registry files for each feature
-└── Schemas/                     # XAML Schemas for GUI elements
+├── Regfiles/                    # Registry files for all features
+│   ├── Undo/                    # Registry files for reverting features
+│   └── Sysprep/                 # Registry files for Sysprep mode
+├── Schemas/                     # XAML Schemas for GUI elements
+├── Assets/                      # Static assets (icons, start menu templates)
+├── Backups/                     # Registry backups (generated during use)
+└── Logs/                        # Script logs (generated during use)
 ```
 
 ### Best Practices
@@ -98,20 +118,20 @@ Avoid these common mistakes when contributing:
 
 1. **Forgetting Get.ps1**: When adding a new command-line parameter, contributors often remember to add it to `Win11Debloat.ps1` but forget to add the same parameter to `Scripts/Get.ps1`. Both files **must** have matching parameters.
 
-2. **Missing Registry Files**: Always create an `Undo` registry file for reversibility, aswell as a `Sysprep` registry file for Sysprep mode.
+2. **Missing Registry Files**: Always create an `Undo` registry file for reversibility, aswell as a `Sysprep` registry file for applying changes to other users and Sysprep mode.
 
-3. **Incorrect Registry Hives for Sysprep**: Sysprep registry files apply changes to Windows' default user, registry keys in the `HKEY_CURRENT_USER` hive must use `hkey_users\default` instead. Ensure you update **all** registry keys in the file.
+3. **Incorrect Registry Hives for Sysprep**: Sysprep registry files are meant to apply changes to a different user. Registry keys in the `HKEY_CURRENT_USER` hive must use `hkey_users\default` instead. Ensure you update **all** registry keys in the file.
 
 4. **Wrong Registry File Location**:
    - Main action files go in `Regfiles/`
    - Undo files go in `Regfiles/Undo/`
    - Sysprep files go in `Regfiles/Sysprep/`
 
-   Placing files in the wrong directory will cause the script to fail when trying to apply or undo changes.
+   Placing files in the wrong directory may cause the script to fail when trying to apply or undo changes.
 
-6. **Not Testing Undo Functionality**: Always test that your undo registry file properly reverts all changes. A feature that can't be undone will frustrate users.
+5. **Not Testing Undo Functionality**: Always test that your undo registry file properly reverts all changes.
 
-7. **Not Testing User/Sysprep Functionality**: Always test that your feature works when applied to another user or to the Windows default user with Sysprep. Sysprep changes can be tested by creating new users after running the script.
+6. **Not Testing User/Sysprep Functionality**: Always test that your feature works when applied to another user or to the Windows default user with Sysprep. Sysprep changes can be tested by creating new users after running the script.
 
 7. **Missing Category**: Features without a `Category` field (set to `null`) won't appear in the GUI. This is intentional for command-line-only features, make sure this is what you want before submitting.
 
@@ -127,11 +147,13 @@ Avoid these common mistakes when contributing:
 To add a new app that can be removed via Win11Debloat:
 
 1. **Find the AppId**: To find the correct AppId for an app:
+
    ```powershell
    Get-AppxPackage | Select-Object Name, PackageFullName
    ```
 
 2. **Edit `Config/Apps.json`**: Add a new entry to the `"Apps"` array:
+
    ```json
    {
      "FriendlyName": "Display Name",
@@ -142,9 +164,10 @@ To add a new app that can be removed via Win11Debloat:
    ```
 
 3. **Follow the Guidelines**:
-- Use clear, user-friendly names for `FriendlyName`
-- Set `SelectedByDefault` to `true` only for apps that are largely considered bloatware, otherwise set to `false`
-- Provide a concise description explaining what the app does
+
+   - Use clear, user-friendly names for `FriendlyName`
+   - Set `SelectedByDefault` to `true` only for apps that are largely considered bloatware, otherwise set to `false`
+   - Provide a concise description explaining what the app does
 
 ### Adding a New Feature
 
@@ -162,6 +185,7 @@ Create new registry files in the `Regfiles/` directory:
 - **Sysprep file**: `Sysprep/Disable_YourFeature.reg` (for Sysprep mode)
 
 Example registry file structure:
+
 ```reg
 Windows Registry Editor Version 5.00
 
@@ -170,6 +194,7 @@ Windows Registry Editor Version 5.00
 ```
 
 A Sysprep registry file should apply the same changes as the normal action. Replace the hive of registry keys that start with `HKEY_CURRENT_USER` with `hkey_users\default`. For example:
+
 ```reg
 Windows Registry Editor Version 5.00
 
@@ -179,7 +204,7 @@ Windows Registry Editor Version 5.00
 
 #### 1b. Implement the Feature Logic
 
-If your feature requires more than just applying a registry file, add custom logic to the main script in the appropriate section. In most cases this will involve creating a new entry in the `ExecuteParameter` function for your new feature.
+If your feature requires more than just applying a registry file, add custom logic to the main script in the appropriate section. In most cases this will involve creating a new entry in the `Invoke-FeatureApply` function (in `Scripts/Features/InvokeChanges.ps1`) for your new feature. If your feature also requires custom undo logic (beyond a simple registry file import), add a corresponding entry to the `Invoke-FeatureUndo` function in the same file.
 
 #### 2. Add Feature to Features.json
 
@@ -192,35 +217,39 @@ Add your feature to the `"Features"` array in `Config/Features.json`:
   "ToolTip": "Detailed explanation of what this feature does and its impact.",
   "Category": "Privacy & Suggested Content",
   "Priority": 1,
-  "Action": "Disable",
   "RegistryKey": "Disable_YourFeature.reg",
-  "ApplyText": "Disabling your feature...",
-  "UndoAction": "Enable",
+  "ApplyText": "Disabling your feature",
+  "UndoLabel": "Short description for the undo",
+  "ApplyUndoText": "Enabling your feature",
   "RegistryUndoKey": "Enable_YourFeature.reg",
   "RequiresReboot": false,
+  "DisableWhenApplied": false,
   "MinVersion": null,
   "MaxVersion": null
 }
 ```
 
 **Field Descriptions**:
-- `FeatureId`: Unique identifier (must match parameter name in Win11Debloat.ps1 and Get.ps1)
-- `Label`: Short description shown in the UI, written in a way to fit with the Action or UndoAction prefixed
-- `ToolTip`: Detailed explanation of what the feature does, used for tooltips in the GUI
+
+- `FeatureId`: Unique identifier, this must match parameter name in the Win11Debloat.ps1 and Get.ps1 files.
+- `Label`: Short description shown in the UI and wiki documentation.
+- `ToolTip`: Detailed explanation of what the feature does, used for tooltips in the GUI.
 - `Category`: One of the predefined categories (see Categories array in Features.json), features without a category won't be loaded into the GUI.
 - `Priority`: Optional. The priority value (int) is used to sort features within a category. If this field is omitted the feature will be sorted based on the order in the Features.json file.
-- `Action`: Action word for the feature (e.g., "Disable", "Enable", "Hide", "Show")
-- `RegistryKey`: Filename of the registry file to apply (in Regfiles/ directory) or null if feature does not require registry changes
-- `ApplyText`: Message shown when applying the feature
-- `UndoAction`: Action word for reverting (e.g., "Enable", "Show")
-- `RegistryUndoKey`: Filename of the registry file to revert changes or null if feature does not require registry changes
-- `RequiresReboot`: Optional boolean. Set to `true` if the feature requires a system reboot to take effect
-- `MinVersion`: Minimum Windows build version (e.g., "22000") or null
-- `MaxVersion`: Maximum Windows version or null
+- `RegistryKey`: Filename of the registry file to apply (in Regfiles/ directory) or null if feature does not require registry changes.
+- `ApplyText`: Message shown when applying the feature.
+- `UndoLabel`: Short description for the undo shown in the UI.
+- `ApplyUndoText`: Message shown when undoing the feature.
+- `RegistryUndoKey`: Filename of the registry file to revert changes or null if feature does not require registry changes.
+- `RequiresReboot`: Optional boolean. Set to `true` if the feature requires a system reboot to take effect.
+- `DisableWhenApplied`: Optional boolean. Set to `true` if the feature has no supported undo method.
+- `MinVersion`: Minimum Windows build version (e.g., "22000") or null.
+- `MaxVersion`: Maximum Windows version or null.
 
 #### 3. Add Command-Line Parameter
 
 Add a corresponding parameter to both `Win11Debloat.ps1` AND `Scripts/Get.ps1`, the parameter name should match the FeatureId you have defined in `Features.json`. In most cases this will be a switch parameter, example:
+
 ```powershell
 [switch]$YourFeatureId,
 ```
@@ -233,12 +262,14 @@ Add a corresponding parameter to both `Win11Debloat.ps1` AND `Scripts/Get.ps1`,
 The default preset (`Config/DefaultSettings.json`) defines which features are automatically applied when users run Win11Debloat in "Default Mode" or with the `-RunDefaults` parameter. This preset should include features that are widely considered to improve the Windows experience without breaking functionality.
 
 **When to add a feature to the default preset:**
+
 - The feature removes obvious bloatware or distractions
 - The feature enhances privacy without breaking core functionality
 - The feature is generally non-controversial and beneficial to most users
 - The change can be easily reverted if needed
 
 **When NOT to add a feature to the default preset:**
+
 - The feature significantly changes core Windows behavior
 - The feature might break applications or workflows for some users
 - The feature is highly opinionated or preference-based
@@ -254,10 +285,12 @@ To add your feature to the default preset, edit `Config/DefaultSettings.json` an
 ```
 
 **Field Descriptions**:
+
 - `Name`: Must exactly match the `FeatureId` from Features.json
 - `Value`: Set to `true` to enable the feature in default mode
 
 **Example:**
+
 ```json
 {
   "Version": "1.0",
@@ -283,6 +316,7 @@ To add your feature to the default preset, edit `Config/DefaultSettings.json` an
 To add a new category for organizing features:
 
 - Add a new category entry to the `"Categories"` array in `Config/Features.json`:
+
   ```json
   {
     "Name": "Your Category Name",
@@ -320,17 +354,20 @@ UI Groups allow features to be grouped together in the GUI with a combobox (drop
 ## Submitting a Pull Request
 
 1. **Commit your changes** with clear, descriptive commit messages:
+
    ```powershell
    git add .
    git commit -m "Add feature: Description of your changes"
    ```
 
 2. **Push to your fork**:
+
    ```powershell
    git push origin feature/your-feature-name
    ```
 
 3. **Create a Pull Request** on GitHub:
+
    - Go to the original Win11Debloat repository
    - Click "New Pull Request"
    - Select your fork and branch
@@ -342,6 +379,7 @@ UI Groups allow features to be grouped together in the GUI with a combobox (drop
 # Questions?
 
 If you have questions about contributing, feel free to:
+
 - Open a [discussion](https://github.com/Raphire/Win11Debloat/discussions)
 - Comment on an existing issue
 - Ask in your pull request

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,6 +1,6 @@
 name: "🐞 Bug report"
 description: "Report an issue you encountered"
-labels: ["bug"]
+labels: ["bug", "unconfirmed"]
 
 body:
   - type: markdown

.gitignore

@@ -1,6 +1,3 @@
-LastSettings
-SavedSettings
 LastUsedSettings.json
-CustomAppsList
 Logs/*
-Win11Debloat.log
+Backups/*

Config/DefaultSettings.json

@@ -61,10 +61,6 @@
             "Name": "DisableDragTray",
             "Value": true
         },
-        {
-            "Name": "DisableFastStartup",
-            "Value": true
-        },
         {
             "Name": "Hide3dObjects",
             "Value": true

README.md

@@ -4,9 +4,9 @@
 [![Join the Discussion](https://img.shields.io/badge/Join-the%20Discussion-2D9F2D?style=for-the-badge&logo=github&logoColor=white)](https://github.com/Raphire/Win11Debloat/discussions)
 [![Static Badge](https://img.shields.io/badge/Documentation-_?style=for-the-badge&logo=bookstack&color=grey)](https://github.com/Raphire/Win11Debloat/wiki/)
 
- Win11Debloat is a lightweight, easy to use PowerShell script that allows you to quickly declutter and customize your Windows experience. It can remove pre-installed bloatware apps, disable telemetry, remove intrusive interface elements and much more. No need to painstakingly go through all the settings yourself or remove apps one by one. Win11Debloat makes the process quick and easy!
+ Win11Debloat is a lightweight, easy to use PowerShell script that allows you to quickly declutter and customize your Windows experience, no installation required! You can use it to remove pre-installed apps, disable telemetry, remove intrusive interface elements and much more. No need to painstakingly go through all the settings yourself or remove apps one by one. Win11Debloat makes the process quick and easy!
 
-The script also includes many features that system administrators and power users will enjoy. Such as a powerful command-line interface, support for Windows Audit mode and the option to make changes to other Windows users. Please refer to our [wiki](https://github.com/Raphire/Win11Debloat/wiki/) for more details.
+The script also includes many features that system administrators and power users will enjoy. Such as a powerful command-line interface, support for Windows Audit mode and the ability to make changes to other Windows users. Please refer to our [wiki](https://github.com/Raphire/Win11Debloat/wiki/) for more details.
 
 ![Win11Debloat Menu](/Assets/Images/menu.png)
 

Regfiles/Start_AllApps_Category.reg

@@ -0,0 +1,7 @@
+Windows Registry Editor Version 5.00
+
+[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Start]
+"AllAppsViewMode"=dword:00000000
+
+[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]
+"NoStartMenuMorePrograms"=-

Regfiles/Start_AllApps_Grid.reg

@@ -0,0 +1,7 @@
+Windows Registry Editor Version 5.00
+
+[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Start]
+"AllAppsViewMode"=dword:00000001
+
+[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]
+"NoStartMenuMorePrograms"=-

Regfiles/Start_AllApps_List.reg

@@ -0,0 +1,7 @@
+Windows Registry Editor Version 5.00
+
+[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Start]
+"AllAppsViewMode"=dword:00000002
+
+[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]
+"NoStartMenuMorePrograms"=-