Hyper-V RC0 Release is available for download

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.

    Comments (144)

    1. Anonymous says:

      YES, RC0 of the Microsoft virtualization solution Hyper-V is available for download. John Howard has

    2. Anonymous says:

      Those of you tracking the progress with great enthusiasm (as I am) of the new Hyper-V virtualization

    3. @Chupacabra – yes, the non-domain joined scenario is a little more complex to set up. I’m working on getting a post up hopefully in the next week which covers this in more detail.



    4. Anonymous says:

      Prodje Launch Event, izadje Windows Server 2008 a ja ne napisah ni slovo o tome! U nastavku ispravljam

    5. Anonymous says:

      She was a woman in her sixties who had big blonde hair and would sing“ Good Ship Lollipop” and these sort of naughty songs, like“ I’ m Your Mailman” – I’ ll lift your knockers and ring your bell and you’ ll think I am swell, I’ m your mailman! I can come

    6. Anonymous says:

      Some of you may have noticed that the RC0 release of Hyper-V ( KB49219 ) hit Windows Update yesterday.

    7. Anonymous says:

      A few minutes ago, in Clive’s session at the UK server launch event, our UK product manager announced

    8. Ashridah – to follow up on the issue you are reporting, can you possibly email me directly using the email link at the very top of this page. I’d like to understand your configuration a little more to see whether I can repro it here. What would be interesting to know is whether it’s an IPSec or authorisation issue from the VM to your corp ISA server – I’m assuming your VM is domain joined and you are logged onto the VM using domain credentials. Do you have IPSec deployed in your environment? Could it be the Windows firewall in the VM blocking traffic? IIRC, the ISA firewall client performs a DNS query for a WPAD entry, but the settings can also be configured as a DHCP scope option. It’s been a while since I looked at that, so could be wrong. Regardless, any info you can provide would be useful.



    9. Rene – In hindsight, that should not have been published when they are still in the works. I will follow up with the appropriate folks who own that page. I assure you though that they will be available soon.



    10. Robert/JH – please email me for a workaround. The link is at the top of my blog.



    11. Steve – I believe you are hitting what we now know to be a known bug in RC0 and has been hit by a few people now. Can you try shutting down you VM, adding a legacy NIC a try Windows update again? (Temporarily disable the synthetic NIC in ncpa.cpl in the VM).



    12. Pete

      You need to install the Integration Services inside the virtual machines themselves. For everything except 2008, use actions/insert integration services setup disk in Virtual Machine Connection. For 2008, run the MSU inside the virtual machine itself.

      Yes, absolutely, multiple VMs can share NICs. We have a "virtual" network switch and you connect the NICs in the VM configuration to switch ports on the virtual switch by selecting the appropriate switch in the NIC settings. If you have multiple external network switches, you can load balance. Note that each external network switch requires a seperate physical NIC.

      I’m not sure about the pre-built question. There are some demo VHDs around on microsoft.com, but most I believe are built for Virtual Server (not that that matters a great deal as you can still use them in Hyper-V). I tend to use a base image I install myself once, and sysprep it to have multiple instances as needed.



    13. Aitor – meant to say, no you should not need to remove the Hyper-V role. But the version check I mentioned above is the critical bit.



    14. Anonymous says:

      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.

    15. Anonymous says:

      Details and download bits can be found here. Just some additional details. If you have existing Windows

    16. Anonymous says:

      One of the problems when you ship a beta product with a released product is that people will use it

    17. Can you confirm your parent partition is running Windows Server 2008 x64 *RTM*? Easiest way to verify is examine the registry key under HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionBuildLabEx. RTM is 6001.18000.amd64fre.longhorn_rtm.080118-1840. If the 18000 bit is 17119 (for example), you are not on the final version of Windows Server 2008.



    18. Hi Johannes – I’m not sure exactly what drivers you will have installed in the VM now – the ISO does not contain the 2K8 version of the drivers. As I put above in the main blog post, for 2K8 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.



    19. ashridah says:

      Hm. The plot thickens. I installed the ISA proxy client we use here, and It wasn’t able to detect the appropriate proxy server automatically.

      Entering the address into the ISA proxy configuration results in a usable test, however, and working connectivity.

      It seems that this could be down to some broadcast traffic being blocked somehow (I’m not too familiar with how the isa client finds a proxy server, so i’m not sure), but that might also explain why internet explorer couldn’t automatically detect the settings either. (IIRC, that’s usually passed through via DHCP, if memory serves, but again, I could be wrong)

    20. @ashridah. Correct. If you only have one NIC, you must have an external virtual switch to allow the parent partition communitation. What operating system is running in the child partition (architecture, OS, service pack), and is it configured with a "legacy" network adapter or just "network adapter" (the latter being the synthetic version). Have you installed the Integration Services inside the child partition (or in the case of Windows Server 2008, installed the QFE)? Unless you need VLANs, I would turn them off while troubleshooting. Last couple of questions – how many virtual network switches have you got defined at the moment – you should only need one, and is it possible that both parent and child partitions are configured with the same MAC or IP address (long shot, but could explain why both lose connectivity).



    21. @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.



    22. Anonymous says:

      The Vista SP1 Management Tools for Hyper-V RC0 are now available for download. These include Hyper-V

    23. Anonymous says:

      With the recent release of Hyper-V the big question is "Am I using the latest version?". 

    24. Anonymous says:

      YES, RC0 of the Microsoft virtualization solution Hyper-V is available for download. John Howard has

    25. Justin – We are aware of autoplay not always kicking in, but running setup.exe manually is the right answer for that. For the error itself, how is your virtual machine configured (number of processors)? 18000 is Vista SP1 though.



    26. Johannes – have you installed the MSU package inside the virtual machine? You need to run the MSU rather than setup.exe from the Integration Services disk as this is a 2K8 virtual machine. You can confirm through view installed updates in the control panel. Can you also confirm what is shown in the normal view of the COntrol Panel Programs and Features, and the build number of both the physical and virtual machine (the registry key to find this is higher up in the comments).



    27. Anonymous says:

      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?

    28. Dasaradha – RC0 is pre-release. Follow the RTM link at the top of the article or on the right side of my blog for KB950050.



    29. @JohnR – this happens when you have not run the RC0 MSU (x64 version in your case) update inside the child partition itself (see instructions above), but I’m not aware of any other circumstances. Please confirm if you have done that already.



    30. @Other Richard 😉 Excellent. Thanks for getting back to me. I was just trying to track down one of those machines here for an in-house verification, but I’ll call off the search. Have fun with RC0.



    31. Alamb200 – you are probably hitting the issue described http://blogs.technet.com/jhoward/archive/2008/03/31/hyper-v-installation-freezes-at-54-or-uninstallation-freezes-at-75.aspx. Is this a Proliant Server with the PSP pre (IIRC) 8.11 version installed?



    32. @Rene – as I mentioned above: "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."



    33. Anonymous says:

      Earlier on the Windows Virtualization Team Blog it showed that there was now support for the MMC snapin (for remote control and management) in the RC.  As soon as I posted a question on the blog (which has not been approved yet) the screen shot disappeared, and so did any mention of the functionality.

      What gives?

    34. Alamb200 – can you try booting into safe mode (safe mode with networking) and see if you are able to run netcfg -u VMS_PP to remove the virtual switch. If that works, a further reboot should complete the uninstall. If that doesn’t work, can you email me the cbs.log file from somewhere under the windows directory using the email option at the top of this page.



    35. 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.



    36. ashridah says:

      Okay, so I’m still having trouble getting the virtual networking settings back the way they were when I was testing the beta.

      Unfortunately, my test system only has one NIC. I’m setting up my virtual switch as an external one, and once that’s setup, the parent partition doesn’t have trouble getting out to the internet… until I start a guest partition up against the same virtual switch.

      When I do that, both the guest, and the parent both lose connectivity.

      Should I be creating more than one virtual switch or something? (Serves me right for not reading this page *before* I upgraded this test system, I guess 🙂 )

      I’ve tried using a few combinations of the "virtual LAN identification" settings to no avail so far.

    37. Mark – where in the interface are you seeing this. There is a bug we know about where help/about will show build 17101 even when on RC0. The best way to tell is to either look at the properties of one of the drivers such as windowssystem32driversvid.sys – RC0 is build 18004, or to start a VM running and the splash screen should say "Release Candidate 0" in the bottom left corner.

      Are you sure there wasn’t an error installation of the MSU and the update didn’t roll back? Does 949219 show in view installed updates under the control panel applet for programs and features?



    38. @MrJazze – there is some more information about how to get the RC0 bits integrated into the base 2008 media on Mikes blog http://blogs.msdn.com/mikekol/archive/2008/03/27/hyper-v-installation-tricks-part-3-integrated-installation-and-the-beauty-of-the-win6-servicing-stack.aspx.



    39. Richard – can you confirm, maybe I misread – are you seeing these errors in the parent partition or a child partition (ie Physical or Virtual machine).

      Can you also confirm which processor model you have fitted to this machine, how much physical memory there is, and how much memory is allocated to the virtual machine (if that is where you are seeing the device manager errors).



    40. ashridah says:

      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. 🙂

    41. 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.



    42. @Matt  That’s unusual. Can you verify you have configured the VM for a single processor and if not, shut down, re configure and restart to try again. If this does not work, can you email me (link at top of page) %windir%vmguestsetup.log and a copy of the output from msinfo32 so I can see what’s failing.



    43. Ed – are you sure you don’t already have KB949219 installed under-the-covers through Windows Update? I’ve seen a few instances of that where people don’t realise the update is already present. Unfortunately, the error you see isn’t the most descriptive – it comes from the packaging mechanism rather than Hyper-V itself. If you don’t have the update, please email me the cbs.log file – email link is at the top.



    44. @Richard re the readme (not sure if same Richard as previous comment). No that should be fine.



    45. Patrickd – First can you confirm under control panel/view installed updates which KB updates are already applied. If 949219 is not in the list, can you email me cbs.log from windowslogscbs please (Zipped 😉 )



    46. @Mark – please email me using the link at the top.



    47. Stibra

      For the 2008 x86 virtual machine first, can you confirm if KB949219 is already listed as installed? It may have come down through Windows Update already.

      For the Vista machine, can you verify this is running the final released version of Vista SP1, and the virtual machine is configured with a single processor. The Integration Services installer require both these.



    48. Pete – I couldn’t come up with an easy answer to be honest, and haven’t had a chance to try anything out. Is there really no possibility of having multiple IPs available? What about unbinding TCP/IP from the virtual NIC created when you created an external virtual network switch to allow one VM at a time to get the IP address? Alternately, create a new private virtual network switch as well as above, and run a NAT router (eg RRAS) one side on the external network switch, the other on the private switch. Then run additional VMs on the private switch NATting through the RRAS box. ICS may be an easier solution than a server VM running RRAS. However, neither solve the problem where you also want the root partition to have Internet access as well.  THat’s where I’m a little stumped and would need to find time to work through a configuration – I don’t think there is an easy answer though.



    49. WeiC – do you have KB950050 installed on both the parent partition and the 2008 virtual machines?



    50. @mcnobrain. Interesting. It could be related, but the previous problem was very much related to HP servers. Can you email me direct – I’d like you to run a few commands and send me a log file if possible. The link is at the top.



    51. @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.



    52. SD – On the parent partition, you probably ended up taking 949219 from Windows Update. Can you verify that it is present under Programs and Features/View Installed Updates in the control panel.

      I’m not sure what the error 80070001 is – it is coming from the updater technology most likely, rather than the Hyper-V package itself. Can you take a look at http://support.microsoft.com/kb/947821 to see if that helps resolve the issue. It would also be helpful if you could email me (link at top) cbs.log from windowslogscbs from the virtual machine. That will give a better idea as to why the update is failing.



    53. @phester. What I think is happening here is that you are exposing a bug in Windows Explorer – we have seen this before. 18004 is the RC0 driver. Can you confirm this really is an x64 VM, not x86 (specifically x86 and possibly brought across from Virtual Server).

      If not, can you provide a little more information on the order in which you installed the bits. Did you have the Beta Hyper-V role enabled before updating the parent partition? Once you applied the QFE in the parent partition, did you the apply the QFE in the VM before forcing drivers in device manager? It may be easier to drop me an email using the link at the top of this post.



    54. @Pete – No, Hyper-V does not include a virtual router. However, Windows Server 2008 does. I’ll have a noodle about how this could be done in a relatively simple way.



    55. Anonymous says:

      Windows 2008 RTM geinstalleerd en Hyper-V beta geinstalleerd. Direct de RC0 update gedaan ( http://www

    56. Shawn – as far as I’m aware, this is not possible unless you have at least one active account you can authenticate against who is a member of the local administrators group. Then from a standard user account, you can use "runas /user:<an-admin-account> cmd", enter the admin accounts password to get to an "Administrator: cmd" command prompt where you can run the install from.

      Alternately, if you use "net localgroup administrators your-admin-account /add" (_from_ the administrators account), that will give your account everything it needs to be able to perform that administration.



    57. @kkaae. Can you confirm that you are running Windows Server 2008 RTM release on the parent partition. That can be confirmed in the registry under HKLMSoftwareMicrosoftWindows NTCurrentVersionBuildLabEx. That should start 6001.18000.

      If it does, can you email me windowslogscbscbs.log. The email link is at the top. It would be helpful to know which language version of Windows Server 2008 and edition (std,ent,datacenter…) you have installed.



    58. ashridah says:

      Heh, no, I know the difference between the Ad-Hoc automatic IP assignment windows does and the DHCP addresses they hand out here at work. It’s definitely not a 169.x.x.x address, and the details does have listings for the IP address of the DHCP server, etc.

      Arghl. And it turns out that connectivity *is* working, it’s just not getting out past our firewall. Odd, since a proxy client is usually only required for stuff that isn’t web-based. Things like windows update usually work.

      Internal sites are working however, but it looks like this isn’t strictly a hyper-V problem, but something else.

      Thanks for replying tho. I am clearly not awake enough this morning 🙂

    59. ashridah says:

      The child partition i’m currently testing with is a Win2003 server R2 enterprise system. (The vista rtm guest I had wasn’t too impressed with the network card, and now has no usable network interface, so I assume it needs that QFE the same way win2008 does, and/or SP1 installed, I’ll deal with that later)

      I’ve reinstalled the integration services on the child partition, and it seems to have reinstalled the network driver, since it’s currently reading as:

      Microsoft VMBus Network Adapter #2

      It’s weird, however. The child partition does seem to get an IP address using DHCP when it boots up, but any further communications fail, including any attempts to renew the IP address by hitting the ‘repair’ button.

      It looks like the parent partition does actually still have connectivity at this point, however, I’m not sure why it wasn’t working before (Perhaps I had tried to rebind the physical NIC back to ipv4 and that was messing things up)

      The parent and child network settings are set to use Dynamic MAC addresses, and I doubt that it’s managing to co-incide with a MAC address that’s already in use, and the network uses DHCP, so I should get a unique IP address no matter what, as far as I can tell.

    60. Anonymous says:

      Hi, I had the same problem as Steve S Re: Windows Update not working properly in any of my guests on RC0. Replacing the Synthetic NIC with the Legacy NIC worked great on Win2003. This also fixed another problem for me. When connecting to the child via a Remote Desktop Session, as soon as Internet Explorer was opened, the session locked up. This occured with both IE6 and IE7. I had no trouble with IE connecting to the child from the hyper-v manager. No other applications or tools would cause the lockup. Since running with the Legacy NIC, there have been no lockups.  

      Thanks, Paul

    61. Walker – this post is nearly 2 and a half years old and refers to a release candidate (ie pre-release update) for the first version of Hyper-V. As such it has long since been made unavailable. You should look for Windows Server 2008 R2 or Microsoft Hyper-V Server 2008 R2 instead now.


    62. @Loïc  Thanks for the feedback. We are looking at possibilities. While it sounds so simple, the reality is that is isn’t. I assure you, we do have this on our list though.



    63. JeffV. It it possible 949219 has already been installed through Windows Update? Can you take a look in Control Panel/Programs and Features/View Installed Updates? I’d be interested in taking a look at the cbs.log file if the update is not already there (email link at top).



    64. Pete – sorry, I’m kind of stuck suggesting anything else at this point. I’m somewhat surprised that your network admins are quite that restrictive – I’ve heard that maybe only once before. It may be worth asking some of the folks on the Technet Discussion forum at http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=583&SiteID=17 where there are many other people including MVPs who may have a better workaround.



    65. Pete – not sure I follow your question. Think of each VM as you would a physical machine – it needs a MAC address and an IP address. You’re just sharing a physical resource (the physical NIC) across multiple virtual machines plus the physical machine itself. Fuller documentation will be available as we get closer to RTM. For now though, there is very little available unfortunately.

      For XP, yes, SP3 is required. It is currently in RC, I believe (I haven’t been tracking the final release date), through http://connect.microsoft.com.



    66. @Robert – did you verify the merge of the snapshot tree from Beta completed before the update? We know this takes a long time to complete (and I mention above that there is a bug in beta in this area).

      We are aware of the VMAdditions issue – there is documentation coming (if not already – I think there is, but I don’t get involved too much on that side) that you should have the latest version of the additions installed in the VM when it is runing under Virtual Server before bring the VHD across to Hyper-V (to allow the uninstall to proceed in Hyper-V). Our stronger recommendation is to bring the VHD across without the additions installed. (FWIW, This is a bug in older versions of the additions.) Thank you for the feedback though – it’s valuable to know that the messaging here has not been made strongly enough.



    67. @Frank – yes, this does work. What problem are you facing?



    68. Ashridad. For the Vista partition, you need to be running x86 with SP1 and install the integration services using the method described in my post. It’s only Windows Server 2008 partitions which you install the MSU QFE packages in.

      What is the IP address the child partition gets (don’t actually publish that here, but specifically, is it a 169.x.x.x address, or something in the same subnet as the parent partition). If it’s not a 169.x.x.x address, can you ping the parent partition from the child, or the other way around?

      If it is 169.x.x.x, verify in the settings for the virtual machine one the NIC that it is connected to the external network switch.



    69. 949219 is pre RTM, you should follow the link to RTM at the top of this post (KB950050). However, you usually get this error if: The update is already applied or it is an incorrect SKU (eg a ‘Without Hyper-V SKU" or x86.



    70. Steve – yes, apologies, I hit send without thinking. There is no 64-bit emulated NIC driver available for Windows 2003, only x86. There isn’t a workaround apart from applying updates manually – it is a known bug in the synthetic NIC driver causing the problem.



    71. 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.



    72. Aitor Ibarra says:


      When I try to apply the update (Windows6.0-KB949219-x64.msu) to the parent partition, I get an error "This update does not apply to your system". Should I try removing the Hyper-V role before applying the update?



    73. Aitor Ibarra says:

      Thanks John – that appears to be it – I’m on 6001.17119 – I thought this box was on RTM.

    74. Minin says:

      Sorry: on _this_ moment work _all_ URLs

    75. Minin says:

      Sorry: at _this_ moment works all URLs

    76. ashridah says:


      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)

    77. Mark Dean says:

      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…

    78. Richard says:

      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.



    79. Justin Ho says:

      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?

    80. Loïc Delambre says:

      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

    81. phester says:

      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?

    82. phester says:

      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.

    83. Robert says:

      Ugh – Maybe I don’t understand snapshots very well but when I followed the directions and started back up again, my machines were back to 3/11/2008 (the last time I had done a snapshot I believe) even though they had been all the time between – anything installed since then was gone.  Perhaps a warning Microsoft? (Unless it was a bug in the Beta anyway)

      Me thinks there is going to be some more unhappy campers out there.

      I also had a heck of a time installing the new VM Additions on one particular Win 2003 Server – the uninstall of the old VM Additions wouldn’t uninstall so I was in a catch-22.  Had to hack my way out of it.

    84. Richard says:

      Hi John,

      I did not have the latest BIOS so I upgraded the system. After a hard reboot I created a virtual machine and still have no luck. I the Devic Manager the I see the following:

      Microsoft VMBus Video Device

      Status – This device cannot start. (Code 10)

      Microsoft VMBus HID Miniport

      Status – This device cannot start (Code 10)

      Microsoft VMBus Network Adapter

      Status – This device cannot start (Code 10)



    85. Richard says:

      Hi John – I’m seeing these in the Virtual Machine. It installs fine, but I can’t access the network or integration services.

      The Optiplex 755 has 4 GB ram, is a quad core Q6600 and 2.4GHz. I allocate 1536 MB (1.5 GB) to the virtual machine. It is running BIOS A08.

      I hope this helps.


    86. Richard says:

      Hi John,

      I missed the readme.

      But I had Win 2003 R2 x32 VM’s running when I installed the RC0 on my server.  After the reboot, they were in a saved state and also had a couple snapshots.  I just deleted them (which took some time as the merge must have been happening) and recreated them.  They all seem fine.  Is there anything I should look for since I didn’t take the correct steps in removing the VM’s?


    87. Richard A says:

      Thanks John and I’m not the same Richard.  I’m glad it’s OK, but maybe you can explain why the readme says the saved states and snapshots need to be deleted prior to deleting the VM’s.  Help me to better understand what’s happening there.

      You can email me at <removed for privacy> if you’d rather.



      [Update: Removed email address for privacy and followed up offline]

    88. Richard says:

      Hi John – found out my problem. Though I had RTM of 2008 on my parent and child partitions, only the parent was upgraded to Hyper-V RC0. I upgraded the child to Hyper-V RC0 and everything works!

      Thanks for your assistance,


    89. Jim Liu says:

      We upgraded one of our parent machines to RC0. The parent and its VMs are all in 2008 RTM x64. The whole procedure went pretty much smoothly. Here’s the detail for those need reference:

      Applying KB949219 on the parent. Took about 3 mins to complete. Reboot twice (a bit weird).

      Old Virtual Network is removed automatically. Installing a new one took around 5 mins to complete. After we assign a static IP to it, the default network is missing and need to be reassigned.

      Created new VMs according to the specs in Beta and use old VHDs.

      Applying KB949219 on the VM. It took a while (around 10 mins) to start the installation. A device installation error occured before the update starts.  (on the second VM it took less than 2 mins and no device error though). Once the upgrade starts and reboot (once) everything’s back to normal. Except we have reassign a static IP, and since it’s the same as it’s in Beta, we need to reboot the VM. The VM hang during reboot and we need to reset it. After it boot again, everything’s working fine.

      One thing to note is that the first VM is running Exchange 2007. Prolly the cause of those glitches?

    90. rene says:


      Where can I find the Hyper-V MMC Manager for Vista SP1? According to http://www.microsoft.com/windowsserver2008/en/us/hyperv-features.aspx these should be available now with RC0.

      "Customers can now install Hyper-V MMC on Vista SP1 for remote management of Hyper-V systems"


    91. Matt says:

      This may be a newbie question.  If so, I’m very sorry…

      I have an XP x86 w/ SP3 VM running on Hyper-V RC0; however, my VMGuest.iso states it does not support XP.  HOWEVER, Microsoft’s own docs states:

      "Hyper-V RC now includes support for… Windows XP SP3 (x86 only)… Integration Components for these additional Guest OSes have been included in RC"

      Why then can I not install the Int. Components on my XP SP3 VM!?



    92. rene says:

      Thanks John.

      I don’t get why the RC notes state that they are available then. Little bit confusing to me.

      Will this Hyper-V manager be part of RSAT? Or is it a seperate install?

    93. johnr says:

      I just installed RC0 and am having the same issue as Richard:

      Microsoft VMBus Video Device

      Status – This device cannot start. (Code 10)

      Microsoft VMBus HID Miniport

      Status – This device cannot start (Code 10)

      Microsoft VMBus Network Adapter

      Status – This device cannot start (Code 10)

      Windows 2008 x64 Standard Edition – first  VM has above errors.  Thanks in advance for your help!

    94. johnr says:

      That was definitely it jhoward, thanks very much!!

    95. JH says:

      Just applied RC0 on an HP DL380G5 Server and get stuck!! HELP!

      I removed all clients, applied KB949219 x64 – every thing looks good. Then reboot – the server get stuck at

      Configuring updates: Stage 3 of 3 – 54% complete. Do not turn off your computer.

      What to do now exept from reinstall?


    96. Robert says:

      I’ve installed KB949219 (x64) on a fresh machine with added Hyper-V role. The hardware is a Proliant DL380G5. After rebooting, the installation hangs at "Configuring updates: Stage 3 of 3 – 54% complete". I’m already waiting for over 2 hours now. It seems I’m not the only one with this problem (maybe DL380G5 related?):  http://forums.techarena.in/showthread.php?p=3616041.

      How to get the parent partition up and running again? Please help.

    97. Chupacabra says:

      Has anyone gotten the Hyper-V MMC to connect from Vista to Server 2008?  All I get is "You do not have the required permission to complete this task.  Contact the administrator of the authorization policy for the computer "XXXXXX""

      I have verified the authorization policy on the Hyper-V server to see that it includes the Administrators group.  I added my own local account, but it made no difference.  I’ve shut off the firewall on both the server and my Vista SP1 workstation.  

      My server and Vista workstation are both in Workstation mode, and are not joined to a domain.  Is this making it impossible to use the MMC console?   I have tried from both an x64 and x86 Vista SP1 workstation with no joy.

      Any suggestions on how to get the MMC console to work from Vista would be greatly appreciated.  Thanks!

    98. Mark says:

      Same issue here, also with on a HP DL380G5 Server:

      Just applied RC0 on an HP DL380G5 Server and get stuck!

      The server get stuck at:

      Configuring updates: Stage 3 of 3 – 54% complete. Do not turn off your computer.

      What is the solution besides starting from scratch?

    99. KKaae says:

      I am trying to install the x64 KB949219 update to my parent partition, but i fails with a ‘code 80073712’.

      I originally had the locale related installation issues, so I selected ‘US’ and left it with that. I have also tried to remove th role before adding the update. But still gets the same error.

      Any clues of what might be wrong?


    100. Frank Nilsen says:

      Anyone tried to update from beta to RC0 on a Windows Server CORE (rtm) ???

    101. KKaae says:


      Thanks for your assistance.

      I have send you the cbs.log as am using the RTM version.

      I look very much forward to receive some feedback from you.


    102. mcnobrain says:

      I get the same Problem installing the KB949219

      The system hangs 54%

      I got a Dell Poweredge 860. So its not only a Problem with HP-servers



    103. Steve Sinchak says:

      I am having issues with Windows Update not working properly in any of my guests on RC0.  I have tried multiple installs of server 2003 R2 32-bit and 64-bit.  

      Anyone else having issues with Windows Update?

    104. Steve Sinchak says:

      Yep, using a legacy network adapter fixed it. Something with the synthetic nic seems to be causing the issue. Let me know if you want me to do any more testing. Thanks for your help.

    105. Steve Sinchak says:

      I spoke too soon. It works great on the 32-bit guests but the legacy nic does not work on my 64-bit 2003 R2 servers since there does not appear to be a 64-bit network driver available even after installing the integration services.

    106. patrickd says:


      I also have the same issue:  "When I try to apply the update (Windows6.0-KB949219-x64.msu) to the parent partition, I get an error "This update does not apply to your system". "

      This is the version that I have installed: 6001.18000.amd64fre.longhorn_rtm.080118-1840

      I have two nics installed, both are visible and working on the host OS (also win2k8).

      Any suggestions?



    107. justin says:


      I am having problems installing the integration services on Vista Ultimate with SP1 32-Bit. I’ve upgraded the Hyper-V to RC0. I just freshly installed a trial version of Vista SP1 I got from the Microsoft Heroes launch. The version numbers are below.

      Buildlab: 6001.longhorn_rtm.080118-1840

      BuildlabEx: 6001.18000.x86fre.longhorn_rtm.080118-1840

      The autorun doesn’t seem to kick in when the integration services CD is inserted. If you navigate to the x86 folder manually and click on setup.exe it gives you an error Unsupported Guest Operating System and lists Vista UP 32-Bit SP1.

      Does anyone have any ideas? As far as I am aware this is the RTM version of Vista.



    108. patrickd says:

      Hi John,

      The issue has been resolved. I burned the update onto a cd and installed it on a host. Works a lot better now, thanks!


    109. MrJazze says:

      I have a question which I am very surprised has not been addressed. I understand RC0 must be installed on parent and child partitions, certain versions of guest OS support integration service; but how does one install KB949219 onto NEW vm when you cannot get keyboard/mouse access without FIRST having KB949219 installed first?

    110. Johannes says:

      Hi John,

      I am facing the same problem like phester (Thsi device cannot start (code 10)) but didn’t manage to fix it. I have a brand new win2k8 installation the hyper-v role was activated after installing the latest version of it (http://www.microsoft.com/downloads/details.aspx?FamilyId=DDD94DDA-9D31-4E6D-88A0-1939DE3E9898&displaylang=en).
      The virtual maschine is a win2k8 x64 server. A screen print of the device manager could be found in my blog:


      Any help would be appreciated!


    111. Johannes says:


      the Version of the vm as well as the host is "6001.longhorn_rtm.080118-1840". If I look on the Integration service disk I could just find a msu package under the x86 tree… (the search function confirmed this ;-)).

      However I found a way to get it working (sreen print see my blog). If you update the drivers manualy by pointing the driver setup to the service disk it work for the HID and NIC but not for the VGA (it always says the latest version is already installed). If you than start sysprep the VGA turns his mind as well and start working…



    112. pete says:

      I have updated to RC0 without error and have an issue with the virtual machines seeing the virtual network adapter.  Can someone offer a little insight into how this is expected to work?  The OS just does not display any networking hardware after install (XP / WS2003) in device manager.  Everything else appears to work and the VM is bound to the virtual NIC.  In the case of the parent OS the network is working fine.  Is it possible for multiple virtual machines to share a single nic?  What is the best way to configure this (VM’s used for testing apps against various OS’s not taking projection loads).  

      Another question, are their prebuilt OS images like VM where has or do we need to go through the actual install for each OS?

    113. pete says:

      Thanks John, I got a WS2003 VM to successfully connect through the parent nic however it was obtaining its own IP (or attempting to).  Is it possible to use the single NIC for all VMs through the virtual switch such that any access is through the parent NIC and no per VM configuration is required (it looks like the VM it has a different MAC address and wants its own IP).  What is the best resource for this type of information (networking in hyper-v docs, articles etc.)?

      Also, for XP. You indicate SP3 is required, is this released yet?

    114. JeffV says:

      I am doing a fresh install that does not have any VMs yet. I got the error message when I try to apply the update (Windows6.0-KB949219-x64.msu) to the server, I get an error "This update does not apply to your system."

      This is the version that I have installed: 6001.18000.amd64fre.longhorn_rtm.080118-1840

      I have two nics installed, both are visible and working on the host OS (also win2k8).

      I added the Hyper-V role, rebooted, downloaded the update to the desktop and double clicked it to run.  I got the error message right away.

    115. pete says:

      Okay, so to confirm, there is no way to have multiple VMs share a single connection (the host connection)?

      You indicate you utilize a virtual switch, I suppose I was expecting a virtual router as well which would assign non routable IPs to the VMs and utilize the single connection of the host PC.

      What type of setup do you recommend to test many VMs in an office environment where a developer is only allocated a single IP?

    116. Jeff25 says:

      I have a fresh install of 6001.18000.amd64fre.longhorn_rtm.080118-1840

      and I get the error message

      "This update does not apply to your system." when I try to execute the update on the server.  I do not have any VMs set up yet so this should be easy.  What steps should I follow to avoid this error?

    117. pete says:

      Is their any option for a "virtual router" that would enable sharing a single host IP with multiple VMs? What do you recommend for this case?  I have a single IP provided by network admin and need to configure multiple VMs for testing purposes they must have access to the internet but external systems need not access them.  Thanks for any recommendations you have for this case.

    118. Stibra says:


      I can not install service integration on Windows 2008 32-bit and Vista 32-bit … always error code 1. Tried to install 32-bit patch KB949219 on Windows 2008, but it cannot be install with message that this update is not for that system

      On 64-bit Windows 2008 KB949219 patch works fine and integration works (network, mouse, etc).

      Any idea?


    119. pete says:

      Okay, please let me know what you come up with.  I suspect this would be fairly common for developers.

    120. nukeitmike says:

      For the "virtual router" question that Pete asked, If you could create a connection on a private virtual switch to the parent partition and have the parent partition share its external network connection, wouldn’t that solve the problem?

      Alternatively, if the machine has enough resources for multiple machines, one guest machine could connect to the external network and have a second virtual nic connected to the private network.  This would require 2 IP addresses though (one for parent and one for externally connected guest).

      ramble ramble ramble…

    121. Ed Blankenship says:

      John, I also happen to be getting the same "The update does not apply to your system." when I run the 64-bit version of the update on my 64-bit system.

      I looked at the BuildLabEx registry key and it looks like I do have the RTM version:  6001.18000.amd64fre.longhorn_rtm.080118-1840

      Any ideas?


      Ed B.

    122. Mark Havens says:

      I just installed the 2008 Enterprise x64 RTM version, and the latest KB (KB949219 x64) to (supposedly) upgrade the Hyper-V to RC0, but the interface still says it’s the beta version. How can I confirm that I’m running RC0 of hyper-V? It appears to be running fine. This is a new load of the OS and that’s all that’s on there.

    123. pete says:

      Hello John, I really need some solution for this deployment case (single IP / network resourced allocated by network admin) needing to have multiple VMs access this for test purposes.  Please let me know any ideas you have or other resources you can recommend to help me resolve this.  Thanks!

    124. pete says:

      The IP allocation is MAC address specific so unbinding tcpip likely does not solve it without a really annoying manual step each time.  I throught there would be a clean software solution but may just look at sticking a cheap router in between for now as a bit of a hack.  If you get the time to suggest a config, it would be great because as I mentioned I suspect this is a common dev config.  Something that would enable VMs to automagically share the host connection without themselves needing network resources would be ideal (remotely it would appear as if all requests came from the host).

    125. shawn says:

      Anyone tried to update from beta to RC0 on a Windows Server CORE (rtm) ??

      Here is the issue: I have disabled the Administrator account (typically a good practice) — the problem is that my personal admin account needs elevated permissions in the command prompt. I have no idea how to do that. It really frustrates me because my account has every group that the build in domain administrator account has (I did a copy).

      So I can’t install in the integration packages.


    126. SD says:


      I have installed Windows 2008 Server Standard edt. RTM.

      REGISTRY INFO – 6001.18000.amd64fre.longhorn_rtm.080118-1840 on both HOST and GUEST.

      When I trixd to install the KB94921 it says Installed encountered an error : 0x80070001Incorrect function. on guest.

      On host it says you dont need this package.

      Any advice.?

    127. SD says:

      949219 is installed on the HOST however I still can’t get mouse on the guest.

      Both HOST and GUSET are latest download.

      IHyper V says RC) on the splash screen.

      On guest I cant install 949219.

      So, no mouse, no NIC as yet…. 🙁

    128. pete says:

      I wanted to touch base and see if you had anything else to offer regarding sharing a hosts network resource between multiple VMs.  Thanks.

    129. rusty says:

      Hi, I finally got around to updating my install of Hyper-V from beta to RC0.  I thought I had the RTM of Server 2008, but got the ‘update does not apply’ so it was a simple matter of installing the latest Server 2008. I removed the Integration services from the VMs and copied my VHD’s to a USB drive.  From this point I found that my VHD of SBS2003 and XP would still not recognize the Hyper V NIC so I went back to the legacy NIC.  As I am still finding issues with XP SP3 I have not tested the Integration Services on XP working fine with SBS2003.  But the big issues is I had last created the VM from VS2005 to Hyper V at the end of February and now after creating the new VM of my SBS and XP instances I found that all the data from March and April were gone. Strange as I have had accessed the data on the SBS VM every day since the February change from VS to Hyper V.

      My question is how does Hyper V update the VHD instance? Does it storage the data somewhere else and if I am going to do an upgrade like this in the future do I need to ‘merge’ the new information into the VHD?

      I thought I had a handle on the Virtual Server but this experience has made be question my VM knowledge.

    130. Server says:

      i get this error message  "This update does not apply to your system" by updte KB949219. who can help?

    131. Dasaradha Ramu says:

      None of the link or URLs to KB949219 is working..

      could you please provide me a working URL to get the KB.

    132. alamb200 says:


      I have been reading the comment with great interest because we have a similar issue to a few people above. We have an IBM server with Windows 2008 and Exchange 2007 on it, the server is a DC which I know it is not recommended but we are only a small company and have to make do.

      We installed Hyper V on it to do some testing and have since tried to remove it but it will not go which is not a massive issue. What is though is when we reboot the server it sits at a screen saying Configuring Updates 3 of 3 71% do not restart the computer and it sits there for 5 hours or so before starting properley.

      Can you help?



    133. alamb200 says:

      No this one is an IBM X3650 server

    134. alamb200 says:

      I have looked at the other post you gave me and followed their instruction on how to remove the virtual adapters and this has removed them for me .

      I am doing a reboot tonight to make sure they do not reappear and if all is okay I will scedule another reboot for tomorrow morning to see if thei improves the boot up time.

      Thanks for your help so far I will let you know what happens..


    135. alamb200 says:

      Hi John,

      As an update I had to reboot into Safe Mode for the changes to be adopted but the server then started a lot quicker then before.

      As a final test I have re-enabled the Exchange services and will try another reboot hopefully tomorrow to see if it is still quick.



    136. alamb200 says:

      Ignoring the last comment completely, I have rebooted the server this morning and it took less then 15 minutes so I am suddenly a very happy bunny.

      Thanks for your help,


    137. WeiC says:


      I have also ran into Microsoft VMBus Network Adapter Status – This device cannot start (Code 10) error while trying to setup a virtual network.  

      Parent partition is Win 2008 enterprise x64.  Child partitions are  Win 2008 enterprise x86, x64, and server core.  I installed the hyper-v role and added the virtual machines BEFORE I applied the hyper-v update (KB950050).   Could this be the cause of my problems?  

      Running on HP DL380G5 w/ 2 Broadcom NICs.

      Any help would be greatly appreciated.  Thanks!

    138. WeiC says:

      Installing the KB on the virtual machines fixed the problem.

      Thank you.

    139. Walker5 says:

      DL links appear to be broken. For shame.

    140. Walker5 says:

      DL links appear to be broken. For shame.

    Skip to main content