Extracting files from the Virtual PC 2004 installer

  • Comments 10

A number of people have asked me how to get the Virtual Machine Additions from Virtual PC 2004, without having to install Virtual PC 2004.  To do this you will need to download the Virtual PC 2004 installer (from: http://www.microsoft.com/downloads/details.aspx?familyid=6d58729d-dfa8-40bf-afaf-20bcb7f01cd1), unzip it, and run the following command:

msiexec /a "Microsoft Virtual PC 2004 MSDN.msi"

This will ask you to provide a directory in which to store the Virtual PC files.  Once this is completed you can find the Virtual Machine Additions under "\Program Files\Microsoft Virtual PC\Virtual Machine Additions\VMAdditions.iso" in the directory that you specified.

Note: This will even work on 64 bit host operating systems, where you cannot install Virtual PC 2004 at all.


Leave a Comment
  • Please add 2 and 3 and type the answer here:
  • Post
  • why would you want to get the vmadditions from VPC 2004? I thought the most desirable vmadditions were those that come with the newest beta of Virtual Server (Vista & Linux support etc.)

    What am I missing here?  

  • Hi Tobias -

    Yes, if you can use the latest version you should.  However, Virtual PC 2007 does not include additions for DOS, Windows 95 or Windows NT.



  • Hi Ben,

    I have a question in which I believe I probably know the answer to already, but feel its worth asking to clarify, just-in-case.

    In regards to the redistribution agreement for Virtual Server, do I understand correctly that extracting the files from the MSI (similar to the process you've pointed out in this post), and then distributing any of the utilities by themselves would violate the terms of this agreement?  In particular, I am interested in the VHDMount utility, though I doubt much it differs from one utility to the next (in terms of whether or not this would be a violation of the redistribution agreement.)

    On an unrelated note, yet while I have a thread open, could you point me to any sort of documentation, or a greater understanding as to how I might script together the ability to reroute requests to localhost:port to a particular virtualized_instance:port using the built-in network utilities provided by VPC and/or VServer?  While it would be simple enough to develop a simple localized proxy server to handle this, if it can easily be handled by VPC/VS, then it seems a waste of time to develop a separate utility.

    At the moment, I use this same general functionality as part of a self contained download > unzip > double-click batchfile > virtualized instance via QEMU, redirecting various localhost port requests to the virtualized instance (e.g. http://localhost will serve directly from the guest machine), but for what I assume is an obvious reason, QEMU is simply a testing tool (as well as a simple/quick way to get a virtualized instance up and running without the need for pre-existing virtualization software to be installed), not something I plan to implement as a long term solution for the nuXleus project.

    Thanks in advance for any help/guidance/direction you can provide, and even more importantly, keep up the great blogging!  *BIG FAN* ;) :D

  • Oops > Forgot to add the link to the post regarding the nuXleus project.  Not that it's all that important to the question at hand, but it will at very least provide some context as to what I am referring to.


  • I clicked on the above link and unless I am blind I don't see the Virtual PC 2004 installer any help would be appreciated.

  • M. David Peterson -

    You would need to distribute the entire MSI and conduct a custom installation.

    ronsgto -

    I have updated the link.



  • Why could they not leave the 95 addins in 07? it would be nice, So we do not have to hunt around, I like playing around with older computer systems and stuff like nt 3 just wont run in vpc

  • I get the earror "Program blocked for compability issues"

    I am using Win 7 64 bit, and Windows Virtual PC

  • Hi Ben, I have a question. I am using Windows XP Professional,and when i go to the command prompt and type in: msiexec /a "Microsoft Virtual PC 2004 MSDN.msi" and it says it could not be opened in a dialog box.Can you help me?

  • Um.... the command isn't working.  Are we supposed to stick it somewhere specific?  Details, people!  *face palm*

Page 1 of 1 (10 items)

Extracting files from the Virtual PC 2004 installer