Documentation

1. Getting Started

Download and install

Head to the download page and grab the installer (MSI) for the Builder, or the portable exe for the Runner.

• Builder (MSI) — Full GUI for creating profiles, exporting scripts, and building standalone exes. Requires a license key.
• Runner (portable exe) — Free. Applies .baseconf profiles to any machine. No install, no license.

System requirements

• Windows 10 21H2 or later / Windows 11
• .NET 8 Desktop Runtime (bundled with the MSI installer)
• Administrator privileges for applying settings

Your first profile

1. Open BaseConf and go to Create Profile.
2. Choose a preset (e.g., MSP Workstation) or start from scratch.
3. Toggle the settings you want, then click Save Profile.
4. Go to Apply Profile, select your saved file, and click Apply.

2. Creating Profiles

Using presets

The Create Profile page includes a preset library. Pick one and all settings are pre-filled. You can then adjust anything before saving.

Custom settings

Every setting category has its own tab: Updates, Power, Privacy, Debloat, and Visuals. Toggle individual options on or off. Hover over a setting to see what registry key or PowerShell command it maps to.

Custom PowerShell

Need to run something BaseConf doesn't cover? Add custom PowerShell scripts directly inside a profile. These run during apply (and optionally during revert). Your scripts are validated for syntax before saving.

Saving profiles

Profiles are saved as .baseconf files. By default they go to:

You can also save to any location — USB, network share, or cloud sync folder.

3. Applying Profiles

GUI apply

Open BaseConf, go to Apply Profile, browse to a .baseconf file, review the settings, and click Apply. A backup is created automatically before any changes are made.

CLI apply

For automation and RMM deployment, use the command line:

Add --silent for no UI prompts. Add --log to write a log file.

Runner exe

The Runner is a standalone portable exe that applies profiles without a Builder license. Double-click a .baseconf file or pass it on the command line:

4. CLI Reference

Examples

Apply a profile silently with logging:

Export a profile to PowerShell:

Revert a profile:

Inspect a profile:

5. Exporting

PowerShell scripts

Export any profile as a standalone .ps1 script. The generated script contains every registry edit and PowerShell command from your profile. Run it directly or push it via RMM.

.reg files

Export the registry-only portion as a .reg file. Useful for Group Policy or manual import.

Revert scripts

Every export includes a matching revert script that undoes all changes. The revert script restores original values from the backup taken at apply time.

How to export

1. Open BaseConf and go to Export Scripts.
2. Select a saved profile.
3. Choose your format: PowerShell, .reg, or both.
4. Click Export and pick the output folder.

6. Standalone Exe

Build a self-contained executable from any profile. The resulting exe embeds the profile and applies it when run — no BaseConf installation required on the target machine.

Building a standalone exe

1. Go to Standalone Exe in the sidebar.
2. Select a saved profile.
3. Optionally add a custom PowerShell script to run during apply.
4. Click Build Exe.
5. The output is a single .exe file you can copy anywhere.

Custom PowerShell to exe

You can embed arbitrary PowerShell scripts into the standalone exe. This is useful for running install commands, setting up scheduled tasks, or anything not covered by built-in settings. The script runs with admin privileges during apply.

Distribution

Copy the exe to a USB drive, network share, or push it via RMM. It runs on any Windows 10/11 machine with admin rights. No .NET runtime or other dependencies needed on the target.

7. File Locations

All data is stored locally under %LOCALAPPDATA%\BaseConf\. Nothing is sent to the cloud. Profiles and backups can be copied freely between machines.

8. Deployment Guide

For MSP techs and IT admins, there are several ways to deploy BaseConf configurations to client machines.

Option 1: Portable Runner

Copy baseconf-runner.exe and your .baseconf file to a USB drive or network share. Run on each machine. No install needed.

Option 2: MSI Installer

Deploy the full Builder MSI via Group Policy, SCCM, Intune, or your RMM. The installer includes the Runner and registers .baseconf file association.

Option 3: Runner via RMM

Push baseconf-runner.exe and the profile file to target machines via your RMM tool. Execute with --silent --log flags. Check exit code 0 for success.

Option 4: Standalone Exe

Build a standalone exe that embeds the profile. Push the single exe to target machines. No companion files needed. Ideal for one-off deployments or non-technical handoffs.

Choosing the right method

9. FAQ