Install Carbon

4 min read

This guide walks every step of installing Carbon on a Windows machine. Allow 15 to 20 minutes from a clean machine — the prerequisite installs (Database Engine, .NET Framework, Azure PowerShell) each take a few minutes and require User Account Control approval.

When the installer finishes, you reboot and then run the Setup Wizard on first launch.

Before you start

Confirm you have:

A Windows machine where you have local administrator rights.
An internet connection (the installer may download prerequisites).
The Carbon installer executable.

If your migration target is VMware vCenter, also review the VMware permissions reference and prep the service account before you start — you will need its credentials during the Setup Wizard that follows install.

Prerequisites the installer needs

Carbon depends on three components, all installed automatically by the Prerequisites Setup Wizard if missing:

Database Engine (Microsoft Access Database Engine) — used for Carbon's local data store.
Microsoft .NET Framework 4.7.2 — runtime for the Carbon console application.
Microsoft Azure PowerShell — used for Azure subscription enumeration and disk operations.

Plus the standing requirement: administrative privileges on the Windows machine.

Step 1: Download the installer

Visit the Carbon product page and request a trial or licence. Smikar emails you the download link. Save the Carbon executable to a folder you can find again.

Step 2: Launch the Prerequisites Setup Wizard

Double-click the Carbon executable. If any prerequisites are missing, the Prerequisites Setup Wizard launches automatically. Click Next to proceed.

Step 3: Select prerequisites to install

The wizard displays the required components: Database Engine, .NET Framework 4.7.2, and Azure PowerShell. Components missing from your system are automatically selected for installation. Click Next.

Step 4: Approve the Database Engine install

A Windows User Account Control prompt appears requesting permission to install the Database Engine. Click Yes. The Database Engine installer runs in a separate window. Wait for it to complete before the wizard moves on.

Step 5: Approve the .NET Framework install

A second UAC prompt requests permission for the Microsoft .NET Framework 4.7.2 setup. Click Yes.

Step 6: Accept the .NET licence terms

The .NET Framework setup displays its licence. Tick I have read and accept the licence terms and click Install. The .NET install runs; wait for completion.

Step 7: Approve the Azure Command-Line Tools install

A third UAC prompt requests authorisation for Azure Command-Line Tools (the Azure PowerShell modules). Click Yes.

Step 8: Installation complete

A confirmation message states Carbon has been successfully installed. Click Close.

Step 9: Restart

A final prompt requests a system restart to apply configuration changes. Click Yes for immediate restart or No to restart manually later. Carbon will not launch correctly until the system has rebooted.

What runs next

After reboot, find Carbon in the Start menu and launch it. The Setup Wizard runs on first launch — Azure authentication, target hypervisor connection, email notifications, licence registration — all in one 10-step flow.

Troubleshooting

Windows blocks the installer with a SmartScreen warning. Right-click the file → Properties → tick Unblock, then re-run. The installer is signed by Smikar Software.

A UAC prompt is denied. The prerequisite that needed approval stays uninstalled and the wizard cannot continue. Re-run the installer and approve every UAC prompt.

A prerequisite installation fails. Re-run the installer; prerequisite detection re-runs and only installs what is still missing. If a specific component repeatedly fails, install it directly from Microsoft and re-run the Carbon installer.

The download link in your email has expired. Resubmit the request form, or email support@smikar.com for a fresh link.

The system is asked to restart but you cannot reboot right now. Click No and finish the restart later. Carbon will not work correctly until the reboot has happened.