How to Enable Windows 10 Pro Hyper-V Snapshots

Windows 10 Pro includes Hyper-V, Microsoft’s built-in virtualisation platform for running another operating system inside a virtual machine. Hyper-V uses the term checkpoint for what many users call a snapshot. A checkpoint records the virtual machine’s disk state and configuration so you can return to an earlier point without reinstalling the guest system.

This feature is useful when testing software, applying unfamiliar settings, or trying a Linux distribution before committing to a full installation. It can also help when practising Windows repairs in a contained environment. A checkpoint is not a complete backup, however, so it should not replace copies of important files.

The process involves enabling Hyper-V, confirming that hardware virtualisation is active, creating a virtual machine, and then adding checkpoints at suitable points. The names of some menus can vary slightly between Windows 10 updates, but the main steps remain consistent for Pro users.

What Hyper-V Checkpoints Do

A Hyper-V checkpoint captures the state of a virtual machine at a particular moment. Depending on the selected type, it can include the virtual machine’s virtual hard disk state, memory contents, and configuration. You can then continue working, install an application, or change settings while retaining the option to return to the earlier state.

Microsoft distinguishes between standard checkpoints and production checkpoints. A standard checkpoint saves the state much like a traditional snapshot, including information about the running session. A production checkpoint uses backup technology inside the guest operating system and is generally better suited to services or workloads that need a consistent file system state.

For everyday testing, a standard checkpoint is often the easiest option. It can reopen a running session close to the point where it was saved. Production checkpoints are more conservative and may restart the guest operating system when applied, so they are less convenient for preserving an interactive desktop session.

Check Hardware And Windows Edition

Hyper-V is available in Windows 10 Pro, Enterprise, and Education editions, but not in Windows 10 Home through the normal supported interface. To check your edition, open Settings, select System, choose About, and look under Windows specifications. You can also type winver into the Start menu search box.

Your computer must support hardware virtualisation. Intel systems usually describe this as Intel VT-x, while AMD systems use AMD-V or SVM. The processor also needs the appropriate second-level address translation capability. In firmware, these options may appear under names such as Intel Virtualization Technology, SVM Mode, or CPU Features.

Restart the computer and enter UEFI or BIOS setup, commonly by pressing Delete, F2, F10, or Esc during startup. Enable the virtualisation setting, save the change, and allow Windows to load. The exact key and menu layout depend on the computer manufacturer, including popular Australian-market brands such as Dell, Lenovo, HP, and ASUS.

A virtual machine also needs adequate memory and storage. If the host has only 4 GB of RAM, Hyper-V may run poorly once Windows and other programs are open. Systems with 8 GB or more provide a more practical starting point. Adjusting virtual memory settings may help general host performance, but it does not replace physical RAM for a demanding virtual machine.

Turn On Hyper-V In Windows 10

The quickest graphical method is to open the Start menu and search for Turn Windows features on or off. Open the result, locate Hyper-V, and tick the main box. Windows should select the related Hyper-V Management Tools and Hyper-V Platform components automatically. Click OK and restart when prompted.

You can also enable the feature through PowerShell. Open PowerShell as an administrator and run:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

Accept the restart request after the command completes. If Windows reports that the feature cannot be installed, revisit the firmware settings and confirm that virtualisation is enabled. A disabled setting in UEFI is one of the most common reasons Hyper-V appears unavailable.

After restarting, search for Hyper-V Manager. If it opens successfully, the local computer should appear in the left-hand pane. You can use this console to create virtual switches, build virtual machines, alter memory allocation, and manage checkpoints.

Create A Virtual Machine Before Taking A Snapshot

Hyper-V cannot create a checkpoint until at least one virtual machine exists. In Hyper-V Manager, select the computer name in the left pane, then choose New > Virtual Machine from the Actions panel. The wizard asks for a name, generation, memory allocation, network connection, virtual hard disk, and installation source.

Generation 2 is generally the preferred choice for modern 64-bit Windows and many current Linux distributions. Generation 1 may be required for older operating systems or specialised installation media. If you are unsure, check the guest operating system’s Hyper-V requirements before selecting the generation, because it cannot be changed later.

Choose a sensible amount of startup memory rather than assigning nearly all available RAM. A Windows 10 guest may need several gigabytes for comfortable use, while a lightweight Linux system can use less. Store the virtual hard disk on a drive with plenty of free space, particularly if the guest will receive large updates or applications.

When the virtual machine is ready, install the guest operating system and apply its basic updates. Sign in, confirm that the network works, and configure any essential software. Taking the first checkpoint after this clean setup gives you a useful recovery point.

Create And Manage Hyper-V Snapshots

Open Hyper-V Manager, select the virtual machine, and look at the Checkpoints pane. Right-click the virtual machine and choose Checkpoint, or use the same command in the Actions panel. Hyper-V creates the checkpoint and displays it beneath the machine in the manager.

Rename the checkpoint immediately with a useful description, such as “Clean Windows install” or “Before graphics driver update”. A clear name is more helpful than a date alone, especially when several checkpoints exist. You can create additional checkpoints before major changes, such as installing an unfamiliar application or changing a system configuration.

To apply a checkpoint, right-click it and choose Apply. Hyper-V warns that the current state may be replaced. Choose Create Checkpoint and Apply if you want to preserve the current state before returning to the older one, or select Apply if you are certain the current state is no longer needed.

Checkpoints use differencing disks, so disk consumption can grow over time. A long chain can make storage management more difficult and may reduce performance. Delete obsolete checkpoints through Hyper-V Manager rather than manually removing files from File Explorer. Hyper-V merges the related disk data as part of the deletion process.

Select The Right Checkpoint Type

To review the checkpoint setting, right-click a virtual machine in Hyper-V Manager, select Settings, and open the Checkpoints section. Under the checkpoint type options, select Production Checkpoints or Standard Checkpoints, depending on your needs. You can also enable the option to create a standard checkpoint if a production checkpoint cannot be made.

Standard checkpoints are convenient for desktop experiments because they can preserve the guest’s memory state. If the virtual machine was running, applying the checkpoint can return you to an almost identical session. This convenience comes with a limitation: it is not the same as a fully reliable application-aware backup.

Production checkpoints aim for a consistent state using the guest’s backup services. Windows guests may use Volume Shadow Copy Service, while supported Linux guests can use suitable file system freeze mechanisms. When a production checkpoint is applied, the guest may boot rather than resume exactly where it was.

For a test machine, either type can be appropriate. Use standard checkpoints for quick configuration trials and production checkpoints where data consistency matters more than preserving an open desktop. Avoid treating either option as a substitute for a separate backup stored on another drive or location.

Resolve Common Checkpoint Problems

If the Checkpoint command is missing or Hyper-V Manager cannot connect to the host, confirm that the Hyper-V services are running. Open the Services app and check Hyper-V Virtual Machine Management. Also make sure the virtual machine is not in a failed, saved, or transitional state.

A checkpoint can fail when the host drive is nearly full, the virtual disk chain is damaged, or security software interferes with Hyper-V files. Free storage before creating another checkpoint and avoid moving .vhdx, .avhdx, or configuration files manually. If a merge is already in progress, allow it to finish before shutting down the computer.

Performance issues may come from assigning too much or too little memory, using a slow hard drive, or leaving many checkpoints in place. An SSD generally provides a smoother experience than a mechanical disk. On laptops, select a suitable power plan and keep the charger connected during large guest updates or disk merges.

Display problems inside a guest are usually separate from checkpoint operation. If colours or brightness appear different on the host after evening use, Windows features such as a Night Light schedule may be responsible rather than Hyper-V. Check the host display settings before changing the virtual machine’s video configuration.

Practical Habits For Safer Use

Checkpoint management is easier when each virtual machine has a clear purpose. A disposable test environment can use frequent checkpoints, while a machine holding valuable documents should rely on normal backups first. Keep personal files outside the guest’s system disk when practical, or copy them to protected storage before experimenting.

Australian users should also consider local conditions. A large Windows ISO downloaded over an NBN connection can still consume substantial data and time, particularly during evening congestion. If a laptop is used between Sydney, Melbourne, Brisbane, or regional locations, keep installation media and recovery files available rather than assuming the same network access everywhere.

Hyper-V checkpoints are especially useful for testing Australian tax, accounting, education, or business applications without immediately changing the main Windows installation. Check the software licence terms and regional requirements before running commercial programs in a virtual machine, particularly where activation is tied to hardware.

When an experiment is complete, remove checkpoints that no longer serve a purpose and keep the virtual machine updated. This leaves the host and guest easier to maintain and reduces the chance of a growing differencing-disk chain consuming the system drive.

Enable Hyper-V, build a small test virtual machine, and create a clearly named checkpoint before your next major change. With adequate storage, a separate backup routine, and sensible checkpoint cleanup, Windows 10 Pro can provide a dependable testing environment without putting the main installation at unnecessary risk.