Force remove MS Virtual Machine Addittions after moved to hardware

Posted on 2009-02-21
Last Modified: 2012-05-06
Hi I have a 2003 server which started its life in a ms virtual server environment, it was migrated out to hardware and now cannot remove the MS virtual server addittions, this means it wont reboot completely without a hard reset. I know that I need to edit the virtual server addittions MSI to disable the 'Inside a MS Virtual Machine Check' I have seen discussion on someone who has solved this and I think I am close. any chance someone can give a little more detail on how to disable the VM check. I have tried editing the msi file with orca and set sequence to 0 and 9999 and completely removed the lines referring to CheckForRunningInsideAVirtualMachine
but still no luck, anyone had success removing this outside of ms virtual server?
Appreciate any help... i know that I can remove it my migrating back to virtual server and removing it that way, but the image is huuge and this will take an eternity.
Question by:slicktech007
    LVL 82

    Accepted Solution

    Just had look at it (it's been two years since I did this myself).
    If I remember correctly, it was sufficient to drop two rows in the table "InstallExecuteSequence":
    * CA_CheckForRunningInsideAVirtualMachine
    * Error_CheckForRunningInsideAVirtualMachine
    Save it as VMUninstall, start it by running
    msiexec /x "VMUninstall.msi"

    If this doesn't work, I think (it's slowly coming back) there was another catch. Look into %Systemroot%\Installer, and check the properties (not the names) of the msi files there. One is probably for the VMAdditions. Add a "-backup" to the name, copy your changed msi file in this folder, and rename it to the name the VM msi file in this folder had. Then try again.

    Author Closing Comment

    Bingo! Thanks oBdA. I found after testing this on a coule of machines that the second part (replacing and renaming the appropriate .msi in c:\windows\installer) is only needed if you have tried to uninstall this before from the standard .msi. must get cached in that installer folder. anyway after removing those 2 lines in the .msi and replacing the file as described, the uninstaller went through without a hitch!  Thanks very much ;-)

    Featured Post

    Highfive + Dolby Voice = No More Audio Complaints!

    Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

    Join & Write a Comment

    Guide: Build a Hyper-V Cluster Introduction We all know that Hyper-V is a cost effective solution (see, and now we want to take advantage of it, right?  Unfortunately, hardware fails, leading to dow…
    Nowadays, Virtual Machines are used equally by small and large scale organizations. However the issue is that VMDK files are also prone to corruption. So, in this article we are looking at how to recover VMDK files from hard disk of host operating s…
    Need more eyes on your posted question? Go ahead and follow the quick steps in this video to learn how to Request Attention to your question. *Log into your Experts Exchange account *Find the question you want to Request Attention for *Go to the e…
    how to add IIS SMTP to handle application/Scanner relays into office 365.

    733 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now