Helper Tools

Bulk Crap Uninstaller uses a modular architecture with specialized helper tools to handle different types of applications. These helper executables provide clean separation of concerns and enable BCU to work with various platform-specific technologies.

Architecture Overview

Helper tools are small, focused executables that:

Run independently from the main BCU application
Communicate via command-line interface (CLI)
Output structured data (typically JSON or XML)
Can be used standalone in scripts
Provide isolation for platform-specific code

Helper tools enable BCU to interface with technologies that require separate runtime environments or elevated privileges.

Available Helper Tools

SteamHelper

Manages Steam game detection and uninstallation

StoreAppHelper

Handles Windows Store app operations via PowerShell

WinUpdateHelper

Interfaces with Windows Update for update removal

OculusHelper

Manages Oculus VR application detection

ScriptHelper

Executes custom uninstall scripts

SteamHelper

Handles all Steam-related operations including game detection, metadata extraction, and uninstallation.

Features

Game Detection

Locates Steam installation directory
Parses libraryfolders.vdf to find all library locations
Reads app manifest files (appmanifest_*.acf)
Extracts game metadata (name, ID, size, install date)

Metadata Extraction

Game/app name and App ID
Installation directory
Size on disk
Last update timestamp
DLC and workshop content detection

Usage Example

Command Line

SteamHelper.exe --list
SteamHelper.exe --appid 730 --info
SteamHelper.exe --uninstall 730

Output Format

{
  "appId": "730",
  "name": "Counter-Strike: Global Offensive",
  "installDir": "C:\\Program Files (x86)\\Steam\\steamapps\\common\\Counter-Strike Global Offensive",
  "sizeOnDisk": "26843545600",
  "lastUpdated": "1647532800"
}

SteamHelper requires the Steam client to be installed. It reads Steam’s internal manifest files directly.

StoreAppHelper

Provides interface to Windows Store (UWP) applications using PowerShell cmdlets.

Features

App Detection

Uses PowerShell Get-AppxPackage cmdlet to query:

All user packages
System-wide packages
Provisioned packages
Package families

App Removal

Uses Remove-AppxPackage cmdlet:

Per-user removal
All-users removal
Provisioned package removal (prevents reinstallation)

Usage Example

PowerShell Interface

StoreAppHelper.exe --list
StoreAppHelper.exe --package "Microsoft.WindowsCalculator" --info
StoreAppHelper.exe --remove "Microsoft.WindowsCalculator_8wekyb3d8bbwe"

Output Format

{
  "name": "Microsoft.WindowsCalculator",
  "packageFullName": "Microsoft.WindowsCalculator_10.2103.8.0_x64__8wekyb3d8bbwe",
  "installLocation": "C:\\Program Files\\WindowsApps\\Microsoft.WindowsCalculator_10.2103.8.0_x64__8wekyb3d8bbwe",
  "publisher": "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US",
  "version": "10.2103.8.0",
  "isFramework": false,
  "isBundle": false,
  "isResourcePackage": false
}

Some Windows Store apps are protected and cannot be removed. StoreAppHelper will report an error for these.

WinUpdateHelper

Interfaces with Windows Update to list and remove installed updates.

Features

Update Detection

Queries Windows Update database:

Installed updates (KB articles)
Update metadata (title, description, date)
Update classification (security, feature, driver)
Update size and installation date

Update Removal

Uses WUSA or DISM to remove updates:

Generates appropriate removal command
Handles restart requirements
Validates removal prerequisites

Usage Example

Command Line

WinUpdateHelper.exe --list
WinUpdateHelper.exe --kb KB5010342 --info
WinUpdateHelper.exe --remove KB5010342

Removal Command Generated

wusa.exe /uninstall /kb:5010342 /quiet /norestart

Removing Windows Updates can destabilize the system. Only remove updates if you understand the implications.

OculusHelper

Manages Oculus VR application detection and metadata extraction.

Features

App Detection

Locates Oculus installation directory
Parses Oculus manifest files
Extracts VR application metadata
Identifies installed DLC and add-ons

Metadata Extraction

Application name and Oculus ID
Installation directory
Size on disk
Version information
Required Oculus runtime version

Usage Example

Command Line

OculusHelper.exe --list
OculusHelper.exe --appid "1234567890" --info

OculusHelper requires Oculus software to be installed. It reads Oculus library manifests directly.

ScriptHelper

Executes custom uninstall scripts with sandboxing and logging.

Features

Script Execution

Runs PowerShell, batch, or VBScript files
Provides sandboxed execution environment
Captures output and exit codes
Enforces timeout limits
Logs all operations

Security Features

Script signature validation (optional)
Execution policy enforcement
Resource usage limits
User confirmation for untrusted scripts

Usage Example

Command Line

ScriptHelper.exe --script "uninstall.ps1" --timeout 300
ScriptHelper.exe --script "cleanup.bat" --verbose

Always review scripts before execution. ScriptHelper can execute arbitrary code.

Helper Communication Protocol

All helpers follow a standard communication protocol:

Command-Line Interface

Standard Switches

--list              List all detected items
--info <id>         Get detailed information about specific item
--remove <id>       Remove/uninstall specific item
--version           Display helper version
--help              Show usage information
--verbose           Enable detailed logging
--json              Output in JSON format (default)
--xml               Output in XML format

Exit Codes

Standard Exit Codes

0 - Success
1 - Invalid arguments
2 - Item not found
3 - Permission denied
4 - Operation failed
5 - Timeout
13 - Unexpected error

Output Format

All helpers output structured data:

Standard JSON Structure

{
  "success": true,
  "data": [
    {
      "id": "unique-identifier",
      "name": "Application Name",
      "metadata": {
        // Helper-specific fields
      }
    }
  ],
  "errors": [],
  "warnings": []
}

Integration with BCU

BCU integrates helpers through factory classes:

SteamFactory.cs Integration

public class SteamFactory : IUninstallerFactory
{
    public IEnumerable<ApplicationUninstallerEntry> GetUninstallerEntries(
        ListGenerationProgress progressCallback)
    {
        // Execute SteamHelper
        var process = Process.Start(new ProcessStartInfo
        {
            FileName = "SteamHelper.exe",
            Arguments = "--list --json",
            RedirectStandardOutput = true,
            UseShellExecute = false
        });
        
        // Parse JSON output
        string output = process.StandardOutput.ReadToEnd();
        process.WaitForExit();
        
        var steamApps = JsonConvert.DeserializeObject<List<SteamApp>>(output);
        
        // Convert to ApplicationUninstallerEntry objects
        return steamApps.Select(app => new ApplicationUninstallerEntry
        {
            DisplayName = app.Name,
            UninstallString = $"steam://uninstall/{app.AppId}",
            UninstallerKind = UninstallerType.Steam,
            // ... other properties
        });
    }
}

Standalone Usage

Helpers can be used independently of BCU:

PowerShell
Batch Script

Using Helpers in PowerShell

# List all Steam games
$games = SteamHelper.exe --list --json | ConvertFrom-Json

# Display game information
foreach ($game in $games.data) {
    Write-Host "$($game.name) - Size: $($game.sizeOnDisk)"
}

# Uninstall a specific game
SteamHelper.exe --uninstall 730

Using Helpers in Batch

@echo off

REM List all Windows Store apps
StoreAppHelper.exe --list > apps.json

REM Remove specific app
StoreAppHelper.exe --remove "Microsoft.BingWeather" --verbose

if %ERRORLEVEL% EQU 0 (
    echo Successfully removed app
) else (
    echo Failed to remove app: %ERRORLEVEL%
)

Building Helper Tools

Helpers are built as part of the BCU solution:

Build Process

# Build all helpers
msbuild BulkCrapUninstaller.sln /t:SteamHelper;StoreAppHelper;WinUpdateHelper

# Build specific helper
msbuild source/SteamHelper/SteamHelper.csproj

Helper tools are .NET console applications targeting the same framework as BCU.

Troubleshooting

Helper Not Found

Ensure helper executables are in the same directory as BCUninstaller.exe or in the system PATH.

Permission Denied

Some helpers require administrator privileges. Run BCU as administrator.

Timeout Errors

Increase timeout values in BCU settings for slow operations (large Steam libraries, etc.).

Invalid JSON Output

Check helper logs in BCU’s log directory for detailed error messages.

Uninstaller Types

Learn about different installer systems BCU supports

Detection Methods

Understand how BCU discovers applications

Architecture

Explore BCU’s overall architecture

Development

Technical Details

Architecture Overview

Available Helper Tools

SteamHelper

StoreAppHelper

WinUpdateHelper

OculusHelper

ScriptHelper

SteamHelper

Features

Usage Example

StoreAppHelper

Features

Usage Example

WinUpdateHelper

Features

Usage Example

OculusHelper

Features

Usage Example

ScriptHelper

Features

Usage Example

Helper Communication Protocol

Command-Line Interface

Exit Codes

Output Format

Integration with BCU

Standalone Usage

Building Helper Tools

Troubleshooting

Uninstaller Types

Detection Methods

Architecture

Build docs developers (and LLMs) love

Development

Technical Details

​Architecture Overview

​Available Helper Tools

SteamHelper

StoreAppHelper

WinUpdateHelper

OculusHelper

ScriptHelper

​SteamHelper

​Features

​Usage Example

​StoreAppHelper

​Features

​Usage Example

​WinUpdateHelper

​Features

​Usage Example

​OculusHelper

​Features

​Usage Example

​ScriptHelper

​Features

​Usage Example

​Helper Communication Protocol

​Command-Line Interface

​Exit Codes

​Output Format

​Integration with BCU

​Standalone Usage

​Building Helper Tools

​Troubleshooting

​Related Topics

Uninstaller Types

Detection Methods

Architecture

Build docs developers (and LLMs) love

Architecture Overview

Available Helper Tools

SteamHelper

Features

Usage Example

StoreAppHelper

Features

Usage Example

WinUpdateHelper

Features

Usage Example

OculusHelper

Features

Usage Example

ScriptHelper

Features

Usage Example

Helper Communication Protocol

Command-Line Interface

Exit Codes

Output Format

Integration with BCU

Standalone Usage

Building Helper Tools

Troubleshooting

Related Topics