I am trying to do a clean
uninstall of the Hyper-v integration tools from a guest OS. I insert
the disk into the virtual drive, and run
D:\support\x86\setup /uninstall
as an administrator.
This does uninstall the tools, but at the end gives an error of
"access denied". On Windows 2003 and prior it seems to uninstall things
correctly. On Windows 2008 Server in the guest OS, it seems to
uninstall, since the mouse stops moving out of the window so nicely, etc., but after you reboot, at some point the tools are magically
installed again and all the services are back running!
I do eject the integration services disk before rebooting, so it
can't be reinstalling from there. I am definitely doing this as an
admin on the box.
How can I get a clean uninstall of the integration tools for Hyper-V
if setup /uninstall doesn't work?
when I last used Windows 7 and 2008 in a Hyper V VM I noticed that the HyperV tools are already part of the operating system.
I did not even have to install them ...
maybe thats why you can not uninstall them ???
Are you sure that you need to uninstall them at all ?
___________________________________
VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay
The way to get them out is pretty tricky because they cannot be uninstalled. Here's the process that I use to move hyperV machines to a machine running Virtual PC.
1. Copy the VM vhd file to machine running Virtual PC
2. Add the vhd as a secondary drive to another VPC that is of same OS and processor architecture but is without HyperV integration services.
3. Start up the non-integration services vpc
4. Browse the file system of the vhd which has integration services, and open the windows\system32 directory.
(you have to rename the hal.dll file in the system32 directory, so you have to change ACLs on the hal.dll file next)
5. Open a command prompt, and CD to , then perform the following
a. takeown /f e:\windows\system32\hal.dll
b. cacls e:\windows\system32\hal.dll /G administrator:F
At this point you should be able to rename the hal.dll file to hal.dll_old
6. Copy the hal.dll from the non-integration services vhd to the vhd of the one that had integration services installed (the same one which you renamed the hal.dll file to hal.dll_old)
7. Shut down the VM
8. Remove the secondary vhd