The wbadmin start backup command creates a backup from the command line using the same engine as Windows' built-in system image tool. To make a system image of Windows on a PC, open Command Prompt as administrator and run wbadmin start backup -backupTarget:E: -include:C: -allCritical -quiet, replacing E: with your backup drive. Windows writes the image to a WindowsImageBackup folder on that drive, and you can restore it later with System Image Recovery.
Below is the syntax, the options that matter, worked examples, how to schedule it, and the limits you should know before you rely on it.
Before you start
- Run it elevated. You must be in the Administrators or Backup Operators group, and run wbadmin from an elevated prompt. Right-click Command Prompt or Windows Terminal and choose Run as administrator.
- Use a separate drive. The backup target cannot be one of the volumes you are backing up. An external USB drive, a second internal drive or a network share all work.
- Check space. Plan for roughly the used space on the drives being imaged, more if you want several versions.
- Format. A local target should be NTFS.
wbadmin start backup syntax
The full syntax, as documented by Microsoft, is:
wbadmin start backup [-backupTarget:{<drive> | <\\server\share>}] [-include:<items>] [-exclude:<items>] [-allCritical] [-systemState] [-noVerify] [-user:<name>] [-password:<password>] [-noInheritAcl] [-vssFull | -vssCopy] [-quiet]
The options you will use most:
| Option | What it does |
|---|---|
-backupTarget:E: | Where to save the backup: a drive letter, a volume GUID path, or a UNC path such as \\nas\backups. |
-include:C:,D: | Comma-separated list of volumes to include. |
-allCritical | Adds every volume Windows needs to start (the system drive, EFI and recovery partitions). This is what makes it a bare-metal system image. |
-quiet | Runs without asking for confirmation. Required for scheduled use. |
-vssCopy / -vssFull | Copy backup (the default) leaves application logs and other backup tools' history alone. Full updates that history; avoid it if another product backs up the same apps. |
-user: / -password: | Credentials for a network share target. |
-noInheritAcl | On a network share, restricts access to the backup folder to the account given in -user. |
The command line also offers -include for individual folders, -exclude and -systemState, but these are aimed at Windows Server. On Windows 10 and 11, wbadmin is best treated as a volume-level imaging tool.
Examples
System image of the Windows drive to an external drive
wbadmin start backup -backupTarget:E: -include:C: -allCritical -quiet
This is the everyday command. It images C: plus the hidden partitions needed to boot.
Include a second data drive
wbadmin start backup -backupTarget:E: -include:C:,D: -allCritical -quiet
Save to a network share
wbadmin start backup -backupTarget:\\nas\backups -include:C: -allCritical -user:nas\backupuser -password:YourPassword -quiet
Putting a password on the command line is not ideal, because it can end up in scripts and logs. Use a dedicated account that can only write to the backup share.
List the backups on a drive
wbadmin get versions -backupTarget:E:
This shows each backup's date and version identifier, which you need if you restore with wbadmin rather than through the recovery screens.
How wbadmin stores versions
This is the part that surprises people.
- Local drive: the backup is stored as virtual hard disk files inside
WindowsImageBackup\<PC name>. Each new run updates them, and older versions are kept as shadow copies on the target drive. When space runs low, Windows deletes the oldest versions automatically. You cannot set a retention rule such as "keep 30 days". - Network share: only one version is kept. Microsoft's documentation notes that a new backup of the same PC to the same share overwrites the previous one, and if that backup fails partway, you can lose the old one without getting a usable new one. Microsoft suggests using subfolders and allowing twice the space.
Because shadow copies live on the target drive, browsing the drive in File Explorer only shows the latest backup. Use wbadmin get versions to see the older ones.
How to schedule wbadmin with Task Scheduler
- Open Task Scheduler and click Create Task (not Create Basic Task, which hides the options you need).
- On the General tab, name it, choose Run whether user is logged on or not, and tick Run with highest privileges.
- On the Triggers tab, add a schedule, for example weekly on Sunday at 1 a.m.
- On the Actions tab, set the program to
wbadminand the arguments tostart backup -backupTarget:E: -include:C: -allCritical -quiet. - On the Conditions tab, untick Start the task only if the computer is on AC power if needed, and consider Wake the computer to run this task.
- On the Settings tab, tick Run task as soon as possible after a scheduled start is missed.
- Click OK and enter your password.
Right-click the task and choose Run once to test it. If it does not start as expected, our guide to a scheduled backup not running in Windows lists the usual causes.
How to restore a wbadmin backup
- Boot into the Windows Recovery Environment: hold Shift while clicking Restart, or boot from Windows installation media or a recovery drive and choose Repair your computer.
- Go to Troubleshoot → Advanced options → See more recovery options → System Image Recovery (wording varies slightly between versions).
- Connect the backup drive. Windows finds the latest image, or you can pick an older one.
- Follow the wizard. Restoring replaces everything on the target drives.
Our guide to restoring a system image to a new hard drive covers the replacement-drive case in detail.
Limits to know about
- Deprecated tooling. Microsoft lists the Backup and Restore (Windows 7) system image feature as deprecated. wbadmin still works in Windows 10 and 11 but is not being developed.
- No encryption. The image is not encrypted. Anyone with the drive can mount the virtual disk and read your files, unless the drive itself is protected with BitLocker.
- No retention control. Versions disappear when space runs out, not according to a rule you choose.
- No alerts. A failed run only shows up in the event log or Task Scheduler history.
- Restoring single files is awkward. You can attach the virtual disk file in Disk Management to copy files out, but it is a manual process.
When a backup program is the better fit
wbadmin is a good tool for a scripted image, and it is already on your PC. If you want images that run on their own and tell you when something is wrong, Rocket Backups schedules system images hourly, daily, weekly or monthly or on triggers such as plugging in the backup drive, runs them incrementally, encrypts them with AES-256, keeps versions by rules you set, verifies each backup and emails you if a job fails. Restoring single files is a matter of picking a date and browsing, and a rescue USB handles full restores when Windows will not start. Rocket Backups can also mount a system image as a drive letter, so copying one file out of last week's image takes seconds. For a broader look at the options, see how to create a system image in Windows 11.
Frequently asked questions
Do I need administrator rights to run wbadmin?
Yes. You must be in the Administrators or Backup Operators group and run it from an elevated Command Prompt or Windows Terminal (Run as administrator).
How do I restore a wbadmin backup?
Boot into the Windows Recovery Environment and use System Image Recovery, which can read the WindowsImageBackup folder that wbadmin creates.
Can wbadmin keep more than one system image?
On a local drive, older backups are kept as shadow copies on the target and the oldest are removed when space runs low. On a network share, each new backup overwrites the previous one.
