A great teacher spoke to me today.   A challenge, a task.

A friend stuck in a bind.

“I have a series of Virtual Machines for Demos but they were prepared for Virtual PC.  I need them to run in Hyper-V and have to remove the Virtual Machine Additions…”

“But master!” I the ignorant student was about to burst out “Just uninstall….”

“Ahhhh…” knowingly interrupted the Master. “But they are in Server 2008 Core environments”

A pause.

Just how DO you do that?

A quick search online found this excellent article Uninstall applications from Server Core by Michael Greene which yielded the answer.

But I decided to go, weeeellllll just a little overboard.

What CAN you do (say the installer is pooched, Murphy is having a particularly rotten day, whatever, to make sure the VMAdditions are dead and gone BEFORE Hyper-V?  Let’s just say you only have physical access to the VHD file.  

Yeah.  Mr. Murphy at his prime.

I came a few extra bits of ammo

Location in registry for Uninstall on VMaddtions


Command line to uninstall


MsiExec.exe /X{E799CA03-7E46-4AE7-A7B6-E904CCFD1529}

Command line to make changes (suspiciously the SAME! :} )


MsiExec.exe /X{E799CA03-7E46-4AE7-A7B6-E904CCFD1529}


If you’d like to just make sure the VMAdditions can’t RUN the next time round

Service names to End Task


Rename C:Program FilesVirtual Machine Additions

Here’s the start key in the Registry


Manually Delete the entry for “VMUserServices” or rename the contents by adding a “-“ to the beginning of the Command Line

Want to get MEAN and REALLY pull it out?

Fire up Notepad.exe (Yes, that’s in CORE)

Copy these contents in a file called “KILLIT.REG” and run that from a command line


Windows Registry Editor Version 5.00



That will stop it from loading automatically permanently


Copy these contents into a file called Deadkey.reg and run this from the command Line.  This will remove it from the “Add/Remove Programs” (which you really can’t see anyhow but is referenced by uninstallers)


Windows Registry Editor Version 5.00




Honestly, the first option (uninstall with the provided lines) should just work and there is no need for drastic measures.

But by renaming the folder, killing the start key, stopping the tasks and running the two reg files (And rebooting afterwards) enough of Virtual Machine Additions SHOULD be removed that Hyper-V shouldn’t care.

the Energized Tech