VMoreCloud › Windows Server 2025 › Hyper-V › Storage Live Migration
WINDOWS SERVER 2025 • HYPER-V • STORAGE • LIVE MIGRATION

Step by Step Hyper-V Storage Live Migration on Windows Server 2025 (GUI and PowerShell)

Need to move a running virtual machine to a new disk, volume or file share without shutting it down? Hyper-V storage live migration moves the VM’s files while the VM keeps running. This guide shows the Hyper-V Manager method and the Move-VMStorage PowerShell method, plus how to verify and troubleshoot.

Author: Khurram Shahzad
Platform: Windows Server 2025
Technology: Hyper-V, PowerShell
Management: Hyper-V Manager, Move-VMStorage
Level: Intermediate
Reading Time: 11 minutes
Hyper-V storage live migration step by step on Windows Server 2025

Move a running VM’s storage without shutting it down

Storage live migration copies a virtual machine’s virtual hard disks and configuration files to a new location while the VM stays powered on, then switches over and removes the old files. It is the safe way to retire a volume, rebalance storage or move to a faster disk.

HV
What this tutorial covers How storage live migration differs from other Hyper-V migrations, what you need before you start, the exact steps in Hyper-V Manager and in PowerShell, how to move disks to different folders, how to move to an SMB share, how to do a shared-nothing live migration between hosts, and how to verify and troubleshoot.
01

The VM stays running

Only the storage moves. The VM keeps serving users while its files are copied.

02

Two ways to do it

Use the Move wizard in Hyper-V Manager, or Move-VMStorage in PowerShell for repeatable work.

03

Plan space and backups

The destination needs enough free space, and you should have a backup before moving production VMs.

Introduction

Storage fills up, disks get replaced and arrays are retired. In each case you may need to relocate the files of virtual machines that cannot be turned off. Hyper-V storage live migration solves this by moving the VM’s virtual hard disks and related files to a different folder, volume or share while the VM remains online.

Example scenario In the vmorecloud.com lab, the Hyper-V host HV01 stores VMs on C:\VMs, which is nearly full. A new volume D: has plenty of space. You move the running VM VM01 to D:\Hyper-V\VM01 without any downtime for its users.

How Storage Live Migration Works

Hyper-V copies the virtual hard disk to the new location while the VM keeps running. Changes made during the copy are tracked so that the destination ends up identical to the source. When the copy is complete, the VM switches to the new files and the old files are removed.

Option in the wizardWhat moves
Move all of the virtual machine’s data to a single locationConfiguration, virtual hard disks, checkpoints and smart paging files go into one folder you choose
Move the virtual machine’s data to different locationsYou pick a separate destination for each item, such as configuration, each disk or checkpoints
Move only the virtual machine’s virtual hard disksOnly the selected disks move; the VM configuration stays where it is
Expect some extra disk activity The VM stays online, but copying a large disk uses I/O on both the source and destination storage. For busy production VMs, run the move during a quieter period.

Requirements

  • A Windows Server 2025 host with the Hyper-V role installed (lab example: HV01)
  • A VM that is running or off, using virtual hard disks (VHD or VHDX)
  • A destination folder, volume or SMB share with enough free space for all the files being moved
  • Administrator rights on the Hyper-V host
  • For SMB destinations: the permissions described later in this guide
  • A current backup of the VM
Disks that cannot be moved this way Storage live migration works with virtual hard disks. Physical (pass-through) disks attached directly to a VM are not virtual files and must be handled separately. Check the VM’s disk configuration first.
1

Step 1: Check Where the VM’s Files Are Now

Open an elevated PowerShell window on the Hyper-V host and list the VM’s current paths:

Get-VM -Name VM01 | Select-Object Name, State, Path, ConfigurationLocation, SnapshotFileLocation, SmartPagingFilePath Get-VMHardDiskDrive -VMName VM01 | Select-Object VMName, ControllerType, ControllerNumber, Path

Note every path. After the move you will compare them against the new locations.

2

Step 2: Prepare the Destination

Create the destination folder and confirm there is enough free space:

New-Item -Path 'D:\Hyper-V\VM01' -ItemType Directory -Force Get-Volume -DriveLetter D | Select-Object DriveLetter, SizeRemaining, Size Get-VMHardDiskDrive -VMName VM01 | Get-VHD | Select-Object Path, VhdType, FileSize, Size

Compare the destination’s free space with the file sizes. A dynamically expanding disk can grow up to its maximum size over time, so leave extra room.

3

Step 3: Move the Storage with Hyper-V Manager

  1. Open Hyper-V Manager and connect to the host.
  2. Right-click the VM and choose Move.
  3. On the Before You Begin page, click Next.
  4. Select Move the virtual machine’s storage and click Next.
  5. Choose how to move the data (see the table above), for example Move all of the virtual machine’s data to a single location, then click Next.
  6. Click Browse and select the destination folder, for example D:\Hyper-V\VM01, then click Next.
  7. Review the summary and click Finish.
Hyper-V Manager → right-click VM → Move → Move the virtual machine’s storage

The VM shows a progress indicator while the move runs, and it stays available the whole time.

4

Step 4: Move the Storage with PowerShell

For repeatable work, use Move-VMStorage. To move everything into one destination folder:

Move-VMStorage -VMName VM01 -DestinationStoragePath 'D:\Hyper-V\VM01'

To place different parts in different locations, for example the configuration on one volume and a data disk on another:

Move-VMStorage -VMName VM01 ` -VirtualMachinePath 'D:\Hyper-V\VM01' ` -SnapshotFilePath 'D:\Hyper-V\VM01\Snapshots' ` -SmartPagingFilePath 'D:\Hyper-V\VM01\SmartPaging' ` -VHDs @( @{ SourceFilePath = 'C:\VMs\VM01\VM01-OS.vhdx'; DestinationFilePath = 'D:\Hyper-V\VM01\VM01-OS.vhdx' }, @{ SourceFilePath = 'C:\VMs\VM01\VM01-Data.vhdx'; DestinationFilePath = 'E:\Data\VM01-Data.vhdx' } )

Use the exact source paths you recorded in Step 1. To move several VMs in one go, loop over them:

'VM01','VM02','VM03' | ForEach-Object { Move-VMStorage -VMName $_ -DestinationStoragePath "D:\Hyper-V\$_" }
Do one VM at a time while you learn Move a single test VM first and check the result before looping over many machines.
5

Step 5: Verify the Move

When the move finishes, re-run the commands from Step 1 and confirm all paths point to the new location:

Get-VM -Name VM01 | Select-Object Name, State, Path Get-VMHardDiskDrive -VMName VM01 | Select-Object Path Get-ChildItem 'D:\Hyper-V\VM01' -Recurse | Select-Object FullName, Length
  • The VM State is still Running
  • Each disk path is under the new location
  • Connect to the VM and confirm its applications work normally
  • Check that the old folder no longer holds the VM’s files, and remove any empty leftover folders

Moving to an SMB File Share

Hyper-V can store VM files on an SMB 3 share. The host that runs the VM needs access to the share, and the host’s computer account must have permission to it.

  • Grant the Hyper-V host’s computer account (for example VMORECLOUD\HV01$) Full Control on both the share permissions and the NTFS permissions of the destination folder
  • Use a UNC path such as \\fs01\VMStore\VM01 as the destination
  • If you start the move from a different machine than the Hyper-V host, Kerberos constrained delegation may be required so the host can access the share on your behalf
Move-VMStorage -VMName VM01 -DestinationStoragePath '\\fs01\VMStore\VM01'
Running the command on the host is simplest Running the move directly on the Hyper-V host avoids the delegation requirement. Test with a non-critical VM before moving production workloads to a share.

Shared-Nothing Live Migration Between Hosts

If you also need to move the VM to a different Hyper-V host, you can move the VM and its storage together in one step. This is often called shared-nothing live migration because the two hosts do not need shared storage.

On both hosts, enable live migration and choose an authentication method:

Enable-VMMigration Set-VMHost -VirtualMachineMigrationAuthenticationType Kerberos

Kerberos authentication needs constrained delegation configured for the hosts in Active Directory. If you want to avoid that setup, you can use CredSSP instead, but then you must start the migration while signed in to the source host. Then move the VM with its storage:

Move-VM -Name VM01 -DestinationHost HV02 ` -IncludeStorage -DestinationStoragePath 'D:\Hyper-V\VM01'
Same host or different host? Use Move-VMStorage to relocate storage on the same host, and Move-VM with -IncludeStorage when the VM changes hosts as well. Both keep the VM running.

Troubleshooting

Not enough disk space

Check free space on the destination and remember that dynamically expanding disks can grow. Free space or choose a larger volume before retrying.

Access denied on the destination

The account or the host’s computer account lacks permission. For local paths, check NTFS permissions. For SMB, grant the host’s computer account access to both the share and the folder.

Authentication or delegation errors

These appear when starting a move remotely or between hosts. Configure Kerberos constrained delegation, run the command on the host, or use CredSSP where appropriate.

A disk cannot be moved

Pass-through disks and some special configurations are not moved by this method. Review the VM’s disk types with Get-VMHardDiskDrive.

The move is very slow

Large disks and busy storage take time. Check disk and network throughput, and move during a quiet period. Avoid starting several large moves at once.

Old files remain behind

If a move was interrupted, review the VM’s current paths, then clean up unused files only after you confirm the VM is running from the new location.

Best Practices

  • Take a backup or checkpoint-free recovery point before moving production VMs
  • Check free space with a margin, especially for dynamically expanding disks
  • Move one large VM at a time and watch storage performance
  • Use consistent folder naming such as a folder per VM
  • Record the old and new paths for your documentation
  • Test SMB destinations with a non-critical VM first
  • Verify the VM and its applications after each move

Comparison of Hyper-V Migration Types

TypeWhat movesVM downtimeTypical command
Storage live migrationVM files, on the same hostNone (VM stays running)Move-VMStorage
Live migration (shared storage)Running VM to another host; storage is sharedNoneMove-VM
Shared-nothing live migrationVM and its storage to another hostNoneMove-VM -IncludeStorage
Export and importCopy of the VM to a pathNeeded for a consistent copy unless the VM is exported live where supportedExport-VM / Import-VM

Frequently Asked Questions

Does the VM need to be turned off for storage live migration?

No. The VM can stay running while its storage moves. It can also be moved while turned off.

What is the PowerShell command for Hyper-V storage live migration?

Move-VMStorage, for example Move-VMStorage -VMName VM01 -DestinationStoragePath ‘D:\Hyper-V\VM01’.

Can I move only one virtual hard disk?

Yes. In the wizard choose “Move only the virtual machine’s virtual hard disks”, or use the -VHDs parameter in PowerShell with source and destination paths for that disk.

Can I move a VM to an SMB share?

Yes. The Hyper-V host’s computer account needs permission to the share and folder, and constrained delegation may be needed if you start the move remotely.

What is the difference between storage migration and live migration?

Storage migration moves files on the same host. Live migration moves a running VM to another host, and shared-nothing live migration can move its storage too.

Will the old files be deleted?

After a successful move, Hyper-V removes the old files at the source. Verify the VM runs from the new location before cleaning up any leftover folders.

Conclusion

Summary checklist Record the VM’s current paths, prepare a destination with enough free space, run the Move wizard or Move-VMStorage, then verify the paths and the VM’s health. Use an SMB share only after setting the right permissions, and use Move-VM with -IncludeStorage when the VM also changes hosts.

Want more Hyper-V tutorials?

Explore practical Windows Server, Hyper-V and infrastructure guides on VMoreCloud.

Explore more tutorials →

Sources & Further Reading

Khurram Shahzad, Hybrid Cloud & Virtualization Engineer and author at VMoreCloud
👤 About the Author
Khurram Shahzad
Hybrid Cloud & Virtualization Engineer
Hybrid Cloud & Virtualization Engineer specializing in VMware (VCF, vSAN, Aria), Microsoft Azure, AWS, Windows Server, Microsoft 365, Entra ID, Intune, Linux, Nutanix, Proxmox, networking, backup & disaster recovery, Cisco and FortiGate. I share practical technical guides, infrastructure projects and insights to help IT professionals build and manage modern IT environments through VMoreCloud.
🖥️ VMware🔷 Azure☁️ AWS🪟 Windows Server🐧 Linux🗄️ Virtualization🛡️ Cybersecurity🔗 Networking💾 Backup & DR✖️ Nutanix🟠 Proxmox
📄
120+
Articles Published
👥
10K+
Readers
🎓
Learning & Sharing
A Stronger Tech Community
View all articles →
“Learn  |  Build  |  Share”
☁️ VMoreCloud|Tech Knowledge for a Better Tomorrow
IT  •  Cloud  •  Virtualization  •  Security  •  Open Source

Technical note: Steps were written for a Windows Server 2025 Hyper-V host. Host, VM and path names are lab examples. Test on a non-critical VM first, and confirm cmdlet behavior against Microsoft’s documentation for your Windows Server build.

Leave a Reply

Your email address will not be published. Required fields are marked *