Virtual Machine Additions Issue

All replies

• 

  

  0

  Sign in to vote

  Hello,
  
  When we encountered this issue we had to move the VM to an old Virtual Server 2005 system, remove the additions, then move it back to Hyper-V. 
  
  Nate

  • Proposed as answer by Peter Forster Monday, July 28, 2008 9:06 AM
  • Unproposed as answer by Graham Wager Tuesday, July 29, 2008 2:45 PM

  Monday, July 28, 2008 4:42 AM
• 

  

  2

  Sign in to vote

  i have migrated windows XP SP3 and Windows Server 2003 SP2 based virtual machines to Hyper-V from Virtual Server 2005 without any difficulty with uninstalling VM Additions.
  
  The process was fairly straightforward:
  
  1 - Moved the vhd drive to the Hyper-V server.
  2 - Create a new virtual machine using Hyper-V Manager and attach the vhd drive to it.
  3 - Boot the virtual machine and after logon cancel all the New Hardware Found installation dialog boxes that popup.
  4 - Uninstall vm additions and reboot the VM guest machine.
  5 - mount the vmguest.iso and let it install the new hal, reboot and continue until it is finished.
  
  As a matter of fact, since i was logged to the Hyper-V host remotely, I didn't have mouse control in the vm guests until the process was done so i had to do everything with just the keyboard. that was fun!
  
  The only problem i ran into with this migration was with one VM that was running Windows XP SP2 and it had to be upgraded to SP3 before it would play.
  
  In one of those migrations i kept the vhd drive on the old server and linked to it over a network share and it played. Both the Virtual Server 2005 host and the Hyper-V hosts are running Windows Server 2008 Standard Edition x64.
  
  

  ---

  Ted S. Antonakis

  Monday, July 28, 2008 10:03 AM
• 

  

  0

  Sign in to vote

  Thanks for your replies.
  
  Ted, whenever I try and uninstall VM Additions under Hyper-V, I simply get the error:
  "You can install Virtual Machine Additions only on a virtual machine that is running a supported guest operating system."
  Did this issue not come up with you? Maybe it's the version of VM Additions I'm using...
  
  Regards,

  ---

  ~~ Graham

  Monday, July 28, 2008 10:45 AM
• 

  

  3

  Sign in to vote

  You can only install the Virtual Machine additions from within Hyper-V if the virtual machine is running Windows XP SP3, Windows Vista SP1, Windows Server 2003 SP2 or Windows Server 2008 and the additions are version 13.803, 13.813, or 13.820.  If the operating system is different or the additions are different, they can only be removed from Virtual Server or Virtual PC.

  If you don't have another machine on which to install Virtual Server or Virtual PC to uninstall the additions, you will have to remove the Hyper-V role from your current box before you install Virtual Server/PC on it.  You cannot install both Hyper-V and Virtual Server/PC into the same instance of the operating system.  (Well, there is a way, but it involves using bcdedit and some registry changes, and it still requires a reboot.  So, in essence, they really aren't installed on the same instance.)

  tgc

  • Marked as answer by Graham Wager Tuesday, July 29, 2008 2:44 PM
  • Marked as answer by Graham Wager Tuesday, July 29, 2008 2:44 PM
  • Marked as answer by Graham Wager Tuesday, July 29, 2008 2:44 PM

  Monday, July 28, 2008 11:55 AM
• 

  

  1

  Sign in to vote

  Thanks Tim, unfortunately the version wasn't one of those, however I took the chance and run it on Virtual PC rather than set up another server and this has worked a treat!
  
  Thanks to all for your replies

  ---

  ~~ Graham

  • Marked as answer by Graham Wager Tuesday, July 29, 2008 2:44 PM

  Tuesday, July 29, 2008 2:44 PM
• 

  

  1

  Sign in to vote

  
  This will work with any Virtual Server 2005 or Virtual PC 2007 Virtual Machine that you moved to hyper-v and forgot to remove virtual machine additions.
  
  If you already put the vhd on your hyper-v server that was a Virtual Server 2005 or a Virtual PC 2007 and can't uninstall virtual machine additions or you can't install virtual guest services.
  
  
  Shutdown the Hyper-v Virtual machine. Share the vhd file on the network and use Microsoft Virtual PC 2007 to start the virtual machine and uninstall virtual machine additions. Remove the Virtual PC 2007 virtual machine, remove the share you created, and start the hyper-v machine. You can then successfully install virtual guest services if it failed earlier because of virtual machine additions.
  
  1.  Check Permissions on the vhd and folder where your hyper-v vhd is stored that you recently moved to hyper-v. Make sure you have read and write permissions for your group or user.  Use your common sense with security don't share it with everyone.

  2.  Share the folder where your vhd is stored on the hyper-v server. (Temporarily)
  
  3.  Shutdown the Hyper-v Virtual machine that you want to remove virtual machine additions
  
  4.  On your workstation that has Virtual PC 2007 Create a new virtual machine and use existing vhd and point it to the share you created and the vhd file in the share.
  
  5.  Start the machine login and uninstall virtual machine additions.
  
  6.  Shutdown Virtual PC 2007 Machine you recently created.
  
  7.  Remove Virtual PC 2007 Machine you recently created.
  
  8.  Login to Hyper-v Server
  
  9.  Remove the share you created earlier
  
  Now your hyper-v virtual machine is ready.  It is ready to install virtual guest services if that failed earlier because of virtual machine additions.

  Wednesday, May 6, 2009 12:06 AM
• 

  

  8

  Sign in to vote

  When uninstalling Virtual Machine Additions, Windows Installer loads the corresponding MSI from %windir%\Installer\xxx.msi.
  
  Now try this:
  - find the correct MSI file (Fileproperties, or launch to see window title)
  - Make a Backup of this file
  - Open this MSI file in a MSI Database Editor *
  - Inside the table InstallExecuteSequence delete the entries CA_CheckForRunningInsideAVirtualMachine and Error_CheckForRunningInsideAVirtualMachine
  - Save this MSI
  - Uninstall the Additions
  
  that's it.
  
  sisal
  
  
  * there are plenty, for example Orca, see http://support.microsoft.com/kb/255905/en-us
    or SuperOrca http://www.pantaray.com/msi_super_orca.html

  • Edited by martec Friday, May 29, 2009 9:26 AM link update
  • Proposed as answer by bwalls Sunday, August 9, 2009 2:37 AM

  Thursday, May 28, 2009 3:59 PM
• 

  

  1

  Sign in to vote

  Great advice. I had a Win2K3 Server created in Virual PC that I need to import into Hyper-V. After using VMC2HV for the import, I couldn't remove the previous Virtual Machine Additions. Following Sisal's post I did the following...
  
  - Windows Explorer: Tools | Options -> uncheck hide protected operation system files.
  - navigate to %windir%\Installs and performed a search for *.msi files with the word Virtual in the file. It came back with one result.
  - Downloaded InstEd (http://www.instedit.com/) MSI editor.
  - Created an ISO of the InstEd install file and installed on my new Hyper-V guest.
  - Inside the table InstallExecuteSequence deleted the entries CA_CheckForRunningInsideAVirtualMachine and Error_CheckForRunningInsideAVirtualMachine
  - Save this MSI
  - Uninstalled the Additions
  
  Worked like a charm & saved me a lot of time. Thanks :-)
  
  -Brian

  • Proposed as answer by richyms Wednesday, August 18, 2010 12:04 PM

  Sunday, August 9, 2009 2:47 AM
• 

  

  0

  Sign in to vote

  Excellent advise, Orca is a great tool for people willing to use it.
  
  You can download just Orca itself from Softpedia: http://www.softpedia.com/get/Authoring-tools/Setup-creators/Orca.shtml. It's a MUCH smaller download than the Platform SDK.

  Sunday, August 9, 2009 8:06 PM
• 

  

  0

  Sign in to vote

  Have just tried your suggestion and you're right it works like a dream. Have kept a copy for a just incase scenario. thanks for saving me a ____ of lot time.
  
  Serena

  Thursday, November 5, 2009 10:58 AM
• 

  

  0

  Sign in to vote

  On my older VPC installation that I had, it didn't have either of these entries. I looked and looked, and came up with something that had error in it and deleted that line, and also one of the lines that had something to do with CA_uninstall... (can't remember which exactly, it was way to late last night) and deleted it. Then it was able to uninstall inside the Hyper-V client machine.
  
  Great solutions!
  Kevin
  

  • Proposed as answer by goran v Thursday, July 1, 2010 8:54 AM

  Monday, February 8, 2010 4:18 PM
• 

  

  0

  Sign in to vote

  In WindowsXP ist the entries in the MSI-File: CA_IsRunningInsideVirtualmachine

  You can this entries remove. This works fine.

  James

  ---

  Markus Bont

  Wednesday, July 31, 2013 9:42 AM
• 

  

  0

  Sign in to vote

  Great solution!

  I had to use Windows Server 2003 R2 EE for a demonstration lab environment, got it from Microsoft Downloads, https://www.microsoft.com/en-us/download/details.aspx?id=19727 and it also had "Virtual Machine Additions" installed.

  With this method I could easily remove them and then install Hyper-V Integration Services. It worked flawlessly. 

  Thanks!

  Tuesday, November 7, 2017 11:18 AM