locked
Virtual XP machine, NEW install, will not boot RRS feed

  • Question

  • I keep getting this error message every time I try to start the Windows virtual PC after I created a new virtual machine for windows XP. I am going to try to make a new, new virtual XP but I am not hopeful of the results.

    This is the error message after the bios starts booting:

    Reboot and Select proper Boot device or Insert Boot Media in selected Boot device_

    Saturday, October 27, 2012 12:50 AM

Answers

  • I've just reflected on this, and now I think I understand - I should have nominated the CD drive as the boot device if I'm using a dynamically expanding hard drive and pointed the drive at an XP ISO image.  But where would I get that from?  No need to answer my question, I'm all fixed now, I should not have tried to create a new machine from'Create virtual machine' in 'Windows Virtual PC', I should have chosen 'Windows XP Mode'.

    • Proposed as answer by Vincent Wang-MCSC Monday, November 5, 2012 8:28 AM
    • Marked as answer by Leo Huang Monday, November 5, 2012 8:28 AM
    Monday, October 29, 2012 9:44 PM

All replies

  •   What are you using as the XP install media? If it is a physical CD, have you put it in the CD drive of the host? If it is an iso file, have you allocated it to the virtual CD drive of the vm?

      The message simply means that the installer cannot find the installation files.


    Bill

    Saturday, October 27, 2012 11:43 PM
  • Are you using an ISO file or the physical CD?

    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”

    Sunday, October 28, 2012 4:53 AM
  • Check to see if you have KB2592687 update installed.  It is causing havoc with Windows virtual PC. Google for articles about it to see if it may be causing your problems.  I also couldn't get a newly created machine to boot today, and I can't get existing machines to connect to \\tsclient\C.  I'm about to uninstall KB2592687 to see if it fixes the problem.
    Monday, October 29, 2012 6:52 AM
  • Further to above, I uninstalled KB2592687 and it fixed the problem of not connecting to \\tsclinet\C for existing virtual machines.  But I still cannot successfully start a newly created machine.  With the Microsoft PXE boot agent BIOS screen visible, it spends a long time trying to find an address from the DHCP server before giving up and then changing to a screen advising me to insert the boot media into the boot device.  I think the boot media error message is misleading in this case.  Update 2574819 to provide support for DTLS was installed at the same time as the KB2592687 RDP update, maybe it should also be uninstalled.
    Monday, October 29, 2012 7:28 AM
  • What is your network interface settings set to for the first adapter? - It should be Bridged to the local host adapter. Also check in the BIOS of your VPC once it boots to ensure the boot order is correct.

    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”

    Monday, October 29, 2012 2:53 PM
  • Steve, in relation to my problem, I have 2 network adapters and both are listed in bridged mode, wireless and wired. I have tried it also with just wired in bridge mode.  Both adapters are active on the host machine and working properly.

    I've never thought of looking at the BIOS of one of these machines - very tricky. Anyway the BIOS shows the first boot device as the hard drive, so that's  not the problem.

    So I changed the hard disk from a dynamically expanding one, which is the default, to a differencing one based on the VHD in the 'C:\Program Files\Windows XP Mode' folder and now the new machine boots up.

    I don't know why this fixes the problem, if you know, an explanation might help the OP.

    Monday, October 29, 2012 9:21 PM
  • I've just reflected on this, and now I think I understand - I should have nominated the CD drive as the boot device if I'm using a dynamically expanding hard drive and pointed the drive at an XP ISO image.  But where would I get that from?  No need to answer my question, I'm all fixed now, I should not have tried to create a new machine from'Create virtual machine' in 'Windows Virtual PC', I should have chosen 'Windows XP Mode'.

    • Proposed as answer by Vincent Wang-MCSC Monday, November 5, 2012 8:28 AM
    • Marked as answer by Leo Huang Monday, November 5, 2012 8:28 AM
    Monday, October 29, 2012 9:44 PM