Remove Unmounted Virtual Machine Files from Hyper-V Host

draft · os-and-system disk-managementhyper-v

Generated by docuprocessor (prompt article/v3) · 2026-04-22 06:06

Source thread

thread_id: spaces/AAAA05BdS6s/threads/7Eg2_Bz_w9Q · 8 msgs · first 2024-05-01 · participants: Tech ATech B

Tech A 2024-05-01 12:42

Hello, 👋 Got warning that DEGTYAREVA - SVR-HYPERV is running out of space, mostly occupied by Virtual machine that is not mounted in Hyper-V. I understand correctly it was migrated to SVR19 and can be safely removed?

Tech A 2024-05-01 12:43

Server is currently hosting eaglesoft on bare metal, and has other machine that is DC

Tech B 2024-05-01 13:03

Yes, we migrated vm to the bare metal on svr19. Check if vhd file is not being modified

Tech A 2024-05-01 13:04

Last modification date was 12/4/2023, and data size is significantly smaller than svr22 d:\ So it should be safe?

Tech A 2024-05-01 13:07

@Sergey Starodub Please don't make the joke that is is safe to remove, after 5 min saying no w8 a moment 🫠

Tech B 2024-05-01 13:12

kill it and we will see soon if it was safe to do so 🙂

Tech A 2024-05-01 13:14

(no text)

Tech A 2024-05-01 13:22

Yeah, well on Gen1 Hyper-v machines the virtual disk updates on daily basis. Meanwhile on Gen2 they update AVHDX rather than HDD virtual disk image. Good to know �

---
title: "Remove Unmounted Virtual Machine Files from Hyper-V Host"
category: os-and-system
tags: ["disk-management", "hyper-v"]
source_thread_id: "spaces/AAAA05BdS6s/threads/7Eg2_Bz_w9Q"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T06:06:49"
participants: ["Tech A", "Tech B"]
---

# Remove Unmounted Virtual Machine Files from Hyper-V Host

## Problem
A Hyper-V host server was running out of disk space due to virtual machine files that were no longer mounted in Hyper-V. The virtual machine had been migrated to bare metal on another server, but the original VHD files remained on the source host, consuming significant disk space. The server was running Eaglesoft on bare metal and hosting a domain controller VM.

## Resolution
1. Verify the virtual machine has been successfully migrated to the target server and is operational
2. Check the last modification date of the VHD file to confirm it is not actively being used
3. Compare the data size between the old VHD and current production data to validate the migration was complete
4. If the VHD file shows no recent modifications (months old) and the migrated system is confirmed working, remove the orphaned virtual machine files
5. Monitor the environment after removal to ensure no services are affected

Note: Generation 1 Hyper-V machines update the virtual disk daily, while Generation 2 machines update AVHDX files rather than the base VHD image, which can help determine if files are still in use.

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/7Eg2_Bz_w9Q`

Generated article

draft