John Howard - Senior Program Manager in the Hyper-V team at Microsoft

Senior Program Manager, Hyper-V team, Windows Core Operating System Division.

Hyper-V RC0 Release is available for download

Hyper-V RC0 Release is available for download

  • Comments 144
  • Likes

Update: 26th June 2008. Hyper-V RTM is now available. RC0 is pre-release software. 


Hot off the press - we have just made Release Candidate 0 (RC0) for Hyper-V available on the Microsoft Download Centre (Center).  (Be patient as if takes a little while to completely propagate.) There are a huge number of improvements in Hyper-V RC0 over Hyper-V Beta, far too many to enumerate. What you really want to know, though, is where to get it, and what to do with it once you have it. So without further ado....:

If your physical machine is already running Windows Server 2008 RTM x64 Edition, the link below is what you need to update the parent partition. By all means – start your download now, but please don’t apply it to your system until you’ve read the rest of this post.

Update for Windows Server 2008 x64 Edition (KB949219)

And while you’re downloading the above update, if you currently have virtual machines running Windows Server 2008 (x86) on Hyper-V beta, or plan have virtual machines running Windows Server 2008 (x86) on Hyper-V RC0,you’ll need this update too:

Update for Windows Server 2008 (KB949219)

Some of the things to look out for before applying the update to the parent partition if you have the Hyper-V Beta role enabled:

  • If you have any Windows Server 2008 virtual machines which are pre-RTM builds, these will need fully reinstalling.
  • If you have any virtual machines running on Hyper-V Beta which are in a saved state, make sure they are shut down cleanly now. 
  • If you have any virtual machines running on Hyper-V Beta which have snapshots, these are not compatible with Hyper-V RC0.  Deleting the snapshots will cause the changes to be merged back to the parent VHD, but this does take some time to complete (and due to a bug in Hyper-V beta, the merge does not always kick in). 
  • Make a note of your virtual machine settings (memory, which VHDs are being used, networks settings etc) 
  • Make a note of any networking configuration (eg IP address/DNS etc) you have applied inside the virtual machines as these will require re-applying after updating to Hyper-V RC0 
  • Make a note of which Virtual Network switches have been created.

Ideally, I would recommend you apply the update to the parent partition before updating any virtual machines. However, if you’ve gone ahead and done it the other way around, it’s not big deal. I’m going to assume you start with the parent partition though.


Apply Windows6.0-KB949219-x64 on the parent partition. A reboot will be required.


If the Hyper-V Beta role was previously enabled: Delete any virtual machine configurations if there are any; Re-create the Virtual Network switches


Create new virtual machines using the settings information you wrote down above.


Note this step applies whether you are using pre-existing VHDs from Hyper-V Beta, or are installing new virtual machines. You must have the Hyper-V RC0 components matching between the parent partition and the virtual machine. (If the component levels do not match, typical symptoms will be that you will not have mouse integration, synthetic networking and storage does not show up in virtual machines.)

a)    If the virtual machine image is Windows Server 2008

  • Apply Windows6.0-KB949219-x86 or Windows6.0-KB949219-x64 depending on the virtual machine architecture, and reboot as requested.

    There are several ways to achieve this. Personally, I recommend creating an ISO or physical CD image containing the updates. You may prefer to configure your virtual machine with a legacy network adapter prior to starting it so that you can download the update directly from inside the virtual machine. You may also prefer to mount the VHD locally on the parent partition and copy the update across.

b)    If the virtual machine image is Windows Server 2003 SP2 (x86/x64), Windows Vista SP1 x86, Windows XP x86 SP3 (SP3 is currently in RC)

  • Start the virtual machine
  • Double click the virtual machine in Hyper-V Manager to open Virtual Machine Connection
  • On the Action Menu, select Insert Integration Services Setup Disk
    • Autoplay should start installing the Integration Services.
    • If autoplay does not start, run setup from the CD/DVD drive in the virtual machine.
  • Reboot as requested.
  • Re-apply any custom networking configuration inside the virtual machine that you wrote down before the update.
  • Finally, some further links for you. I strongly recommend you refer to these as well as my summary instructions above.

    As always, please send your feedback my way. I’d love to hear how you get on.

    • RoyJS - the Vista management tools will be available soon. I can't provide a date yet, but they are ready and in the works - they just need to come out the other side.



    • Good.. Because that is one of the big things I was looking forward too in the RC. I got half way through the upgrade and all mention of them disapeared.

    • Hey,

      Just installed this on my test machine here at work.

      Had a weird issue that I didn't expect:

      the parent partition's ipv4 binding on the external network card decided to turn itself off. Took a few minutes before i realized that the reason the guest partitions couldn't get out to the intranet is that the parent couldn't either.

      Anyone else run into this, or is my system just being a little weird? (Anything's possible, it's not officially supported hardware, it's a dell optiplex 740 with enough bios upgrades to get VT happening)

    • Aha, now i see. By design. The virtual network interface takes over, but I'd forgotten to tick the box that makes the parent use the virtual network interface for traffic. Should have paid closer attention to the network settings before installing. :)

    • @ashiridah. Yup, that is by design (unbinding protocols from the physical NIC and a virtual NIC in it's place).We recommend you have at least two NICs in the physical machine so that one is available for the parent partition.



    • It will be at least a month before I'll be able to re-evaluate Hyper-V. In my first pass, I noticed that there was no real isolation between the root partition and VMs. I was able to drive starve the root partiton and VMs of both CPU cycles and memory causing all VMs to become unusable and then suspended.

      Does anyone know if that has changed with the RTM? I'm also wondering if they'll ever allow for over-committing of RAM. It sucks to have 8GB of RAM on a test system and only be able to run 7 VMs of 1GB of RAM each-unless I'm missing something...

    • Mark - there have been many changes between Beta and RC0. I cannot commit to what further changes there will be between RC0 and RTM though, hopefully for obvious reasons. There have been many performance improvements in RC0 over Beta, and some significant work on IO fairness, so you should see significantly different results in RC0. Over-commit will not be present in RTM though.



    • Hyper-V beta on 2008 Standard RTM has worked fine for me on an OptiPlex 755.

      On the OptiPlex 755 I just did a fresh install of 2008 Standard RTM (have verified it), then installed the Hyper-V RC0. Now the VMBus is not working properly. An error 10 shows in the event log and the integration services aren't able to install. The device manager is showing the VMBus Video, USB Hid, and Network adapter is not working correctly. I can't figure this out.



    • Richard - do you have the latest BIOS installed on this machine, NX/XD enabled in the BIOS and VT enabled in the BIOS. If you change the BIOS settings, you must hard power cycle the machine (as in a "soft" reboot is insufficient). Let me know if that works.



    • Installed RC0 and I'm getting errors with network switch config.  I removed Hyper-V role, rebooted, then reinstalled Hyper-V, but all the Virtual Switches are left over in Network Adapters and I can't remove them.

      Reinstallation of Hyper-V role gives error "0x80041001" while configuring the networks.

      Any suggestions?

    • Installed RC0 and I'm getting errors with network switch config.  I removed Hyper-V role, rebooted, then reinstalled Hyper-V, but all the Virtual Switches are left over in Network Adapters and I can't remove them.

      Reinstallation of Hyper-V role gives error "0x80041001" while configuring the networks.

      Any suggestions?

    • Hi all,

      It is difficult to upgrade a Windows Server 2008 guest machine. By default, you don't have the network and you have to copy the upgrade package on a CD (or an iso file) or add a legacy network card.

      Why the upgrade package is not included in the Integration Services setup disk?

      Thanks in advance

    • Great stuff, but I'm having a problem getting the network adapters working. On the guest VMs (win2008ent64), the virtual nics appear in Device Manager, but nics fail with 'This device cannot start. (Code 10)". Have tried several times to add/remove switches, add/remove virtual nics, remove virt nics and ask windows to find new hardware to no avail. Legacy Network adapters work. Running latest versions and SPs of everything. What am I missing?

    • Re last post. Removed VMBus network device and checked 'Delete driver'. Scanned for new hardware, virtual nic found, older driver used, now they work.

      Driver that was initially installed and not working: netsvc60.sys, date:11/17/2007, ver: Driver that now does work: netsvc60.sys, date:6/21/2006, ver:6.0.6001.18004. Very strange situation, newer driver doesnt work, old one does.

    • @Justin - can you drop me an email (link up the top of the page). I'd like to get some more information about your configuration.



    Your comment has been posted.   Close
    Thank you, your comment requires moderation so it may take a while to appear.   Close
    Leave a Comment