Skip to main content

What is BCU-console?

BCU-console is the command-line interface for Bulk Crap Uninstaller, enabling automated and scriptable management of Windows applications. It provides powerful uninstall capabilities that can be integrated into deployment pipelines, system maintenance scripts, and IT automation workflows.

Key Features

Batch Uninstallation

Uninstall multiple applications at once using predefined uninstall lists (.bcul files)

Application Export

Export comprehensive application data to XML format for inventory management

List Applications

Display all installed applications with version and source information

Junk Cleanup

Automatically remove leftover registry entries and files after uninstallation

Quiet Mode

Use silent uninstallers wherever possible for unattended operations

Automation Ready

Fully scriptable with exit codes for integration into automation workflows

Use Cases

System Administration

Automatically remove unwanted software across multiple machines in an enterprise environment:
BCU-console uninstall C:\Scripts\bloatware.bcul /U /Q

Software Deployment

Clean up old versions before deploying new software:
BCU-console uninstall C:\Deploy\old-versions.bcul /Q /J=VeryGood

Inventory Management

Export application data for compliance auditing and license management:
BCU-console export C:\Inventory\%COMPUTERNAME%-apps.xml

Automated Maintenance

Schedule regular cleanup tasks using Windows Task Scheduler:
BCU-console uninstall C:\Maintenance\cleanup.bcul /U /Q /V

Basic Usage

BCU-console follows a simple command structure:
BCU-console <command> [arguments] [switches]

Getting Help

Display the help screen with all available commands and switches:
BCU-console help
or
BCU-console /?

Available Commands

uninstall

Uninstall applications using a .bcul list file

export

Export installed application data to XML

list

Display all installed applications

Quick Start Example

1

List installed applications

First, view what’s currently installed on your system:
BCU-console list
2

Create an uninstall list

Use the GUI version of BCU to create a .bcul uninstall list file by selecting target applications and using File > Save selection.
3

Test the uninstall

Run the uninstall command without the /U flag to review what will be uninstalled:
BCU-console uninstall C:\Lists\myapps.bcul
4

Execute unattended

Once verified, run the uninstall in unattended mode:
BCU-console uninstall C:\Lists\myapps.bcul /U /Q

Return Codes

BCU-console uses standard Windows return codes for automation and error handling:
CodeMeaningDescription
0SuccessThe operation completed successfully
1Invalid argumentsCommand syntax error or invalid parameters
13Unexpected errorAn unhandled system exception occurred
87Invalid syntaxMissing required arguments or invalid file path
1223CancelledThe operation was cancelled by the user

Checking Return Codes in Scripts

BCU-console uninstall C:\Lists\apps.bcul /U /Q
IF %ERRORLEVEL% EQU 0 (
    ECHO Uninstall completed successfully
) ELSE (
    ECHO Uninstall failed with error code %ERRORLEVEL%
    EXIT /B %ERRORLEVEL%
)

Important Warnings

Use Unattended Mode with CautionThe /U (unattended) flag bypasses all user confirmation prompts. Always test your uninstall lists thoroughly before using unattended mode. Uninstall lists should be as specific as possible to avoid false positives.There are no warranties. Use with extreme caution.
Junk Cleanup Risk LevelsThe /J (junk cleanup) flag will permanently delete registry entries and files. Only use confidence levels below “VeryGood” if you fully understand the risks:
  • VeryGood: Safest option, only removes clearly identified leftovers (recommended)
  • Good: Removes items with high confidence
  • Questionable: May remove items that could still be in use
  • Bad: High risk of removing important data
  • Unknown: Extreme risk, not recommended
There are no warranties. Use extreme caution.

Next Steps

All Commands

Complete command reference with all flags and parameters

Scripting Examples

Real-world automation scenarios and script templates

Build docs developers (and LLMs) love