Skip to main content

How to completely remove a VM from Hyper-V

When a VM has done its job and it is time to say “c’est la vie” to it, getting rid of it completely may not be as cut and dry as you think.

First off, delete it from your Hyper-V Manager.  To do this, open Hyper-V Manager

Right click the VM you want to remove and click Delete.

Click Delete once more.

The Status column for that VM will show you Hyper-V Manager’s progress.

image

This only removed the VM from that Hyper-V Manager.  It did not delete the VMs files.  This could be both a good, and a bad thing.  The good thing is that you an always port this VM to another Hyper-V host or back into the original one.  The bad news is that it is still consuming your hard drive space.  If you truly want to get rid of this VM, browse to the location where it was stored and delete the parent folder.

Comments

Anonymous said…
Thanks for the post, I couldn't find this information on Microsoft site at all. However, how about more information on the 5 types of files and how to determine their locations.
If you are on Windows Server 2012 or Windows 8, Open PowerShell as an Administrator. Execute this command:

PS C:\Windows\system32> Get-VM -Name Test | Select-Object -Property *

You will be able to see where the files of the VM are stored.


VMName : test
VMId : 7e7629cd-2f64-4e29-8dc7-093ed8d75f5d
Id : 7e7629cd-2f64-4e29-8dc7-093ed8d75f5d
Name : test
State : Off
OperationalStatus : {Ok}
PrimaryOperationalStatus : Ok
SecondaryOperationalStatus :
StatusDescriptions : {Operating normally}
PrimaryStatusDescription : Operating normally
SecondaryStatusDescription :
Status : Operating normally
Heartbeat :
ReplicationState : Disabled
ReplicationHealth : NotApplicable
ReplicationMode : None
CPUUsage : 0
MemoryAssigned : 0
MemoryDemand : 0
MemoryStatus :
SmartPagingFileInUse : False
Uptime : 00:00:00
IntegrationServicesVersion :
ResourceMeteringEnabled : False
ConfigurationLocation : d:\VM\Test\Test1\test
SnapshotFileLocation : d:\VM\Test\Test1\test
AutomaticStartAction : StartIfRunning
AutomaticStopAction : Save
AutomaticStartDelay : 0
SmartPagingFilePath : d:\VM\Test\Test1\test
NumaAligned :
NumaNodesCount : 1
NumaSocketCount : 1
IsDeleted : False
ComputerName : JASONPC2
Notes :
Path : d:\VM\Test\Test1\test
CreationTime : 8/29/2013 12:59:08 PM
IsClustered : False
SizeOfSystemFiles : 27930
ParentSnapshotId :
ParentSnapshotName :
MemoryStartup : 1073741824
DynamicMemoryEnabled : False
MemoryMinimum : 536870912
MemoryMaximum : 1099511627776
ProcessorCount : 1
RemoteFxAdapter :
NetworkAdapters : {Network Adapter}
FibreChannelHostBusAdapters : {}
ComPort1 : Microsoft.HyperV.PowerShell.VMComPort
ComPort2 : Microsoft.HyperV.PowerShell.VMComPort
FloppyDrive : Microsoft.HyperV.PowerShell.VMFloppyDiskDrive
DVDDrives : {DVD Drive on IDE controller number 1 at location 0}
HardDrives : {Hard Drive on IDE controller number 0 at location 0}
VMIntegrationService : {Time Synchronization, Heartbeat, Key-Value Pair Exchange,
Shutdown...}

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the