Windows 8 “XP Mode” – Part 1: Hyper-V

In this series, I’ll discuss how you can replace Windows XP Mode from Windows 7 with Client Hyper-V and RemoteApp in Windows 8.

Kyle Beckman By Kyle Beckman - Mon, October 15, 2012 - 6 comments

Kyle Beckman works as a systems administrator in Higher Education in the Southeast United States. He is an MCSE and specializes in Group Policy, Windows Server, and client support.

Articles in this series

Windows 8 XP Mode

If you’re like me, you’ve still got those lingering applications that still don’t work on newer releases of Windows. With Windows 7, you could install XP Mode for those one-off instances of applications. If you had lots of users needing apps with compatibility issues on Windows 7, you could dip into MED-V or VDI to provide those applications to end users.

Microsoft has announced that they will not support MED-V past Windows 7. Microsoft hasn’t said much about XP Mode on Windows 8, but considering the phase out of MED-V along with the inclusion of Client Hyper-V in Windows 8, it is probably safe to assume that XP Mode is gone as well.

So where does that leave you when you still need to bring up an old application or an older version of Internet Explorer alongside Windows 8 seamlessly like in XP Mode in Windows 7? VDI is always an option, but may be overkill if you need occasional access to a legacy application or only have a handful of users needing the application. The good news is that if you liked XP Mode, doing the same thing in Windows 8 is actually pretty easy with Client Hyper-V.

To begin, you’ll need a computer running Windows 8 (Professional or higher) with 4 GB of RAM and a 64-bit SLAT capable processor. Install the Hyper-V roleand reboot.

Unlike XP Mode, there’s a little more work to set things up with client Hyper-V. Out of the box, Client Hyper-V won’t have any virtual machines configured. After bringing up the Hyper-V Manager, you’ll need to click on New > Virtual Machine to create a new VM.

Windows 8 XP Mode - New Hyper-V Virtual Machine

Windows 8 XP Mode – New Hyper-V Virtual Machine

This will bring up the New Virtual Machine Wizard. If you’ve used Hyper-V in Windows Server, this will likely look very familiar. If not, it is very similar to other virtualization products on the market that you may be familiar with. In the first screen of the wizard, you’ll want to pick a name for your VM.

Windows 8 XP Mode  - Virtual Machine name

Windows 8 XP Mode – Virtual Machine name

In the following screens, decide how much memory to assign, select which virtual switch you want to connect to, configure the virtual hard disk, and point Hyper-V to installation media for Windows XP Professional. Click Finish on the last screen.

Windows 8 XP Mode - Startup memory

XP Mode on Windows 8 – Startup memory

 Back in the Hyper-V Manager, highlight your new virtual machine and click the Connect button.

Windows 8 XP Mode - Connect to Virtual Machine

XP Mode on Windows 8 – Connect to Virtual Machine

When your VM opens, click the green Start button to turn on your new VM and install Windows XP.

Windows 8 XP Mode - Turn on Virtual MachineWindows 8 XP Mode - Install Windows XP

Windows 8 XP Mode – Install Windows XP

 Install Windows XP as you normally would. Once it is installed, the first thing you’ll want to do is install the Integration Services. To do this, click Action > Insert Integration Services Setup Disk. In a typical install of Windows XP, autorun will run the installer automatically and prompt you to reboot.

Windows 8 XP Mode

Windows 8 XP Mode – Integration Services

In my next post I will describe how to set up Windows XP in Windows 8 Hyper-V.

Series Navigation - Windows 8 “XP Mode” – Part 2: Windows XP

-1+1 - Rate this post
Loading ... Loading ...
Your question wasn't answered? Ask in the new 4sysops forum!

6 Comments- Leave a Reply

  1. ChristopherO says:

    One potential issue with this method – Win7 Pro came with a free XP in a VM license. I haven’t heard if Windows 8 will have the same?

  2. Kyle Beckman says:

    For Volume License customers, Windows Virtual Desktop Access (VDA) Rights should cover this scenario. For non-VL customers, you may have to purchase a Windows XP Pro or Ultimate license. I would consult with a Microsoft licensing representative before deploying this in a production environment to ensure that you are licensed properly.

  3. Steve G says:

    The one question I have – that remains unanswered – is if I’ll be able to open an existing XP virtual disk after an upgrade to W8. I have an existing virtual disk with stuff on it that would take quite a lot of time to replicate. If I /were/ able to open it with Hyper-v, would XP require activation? I have opened the XP disk with v-box in Linux and it does want to be activated, which turns out to be impossible (I’ve spent hours trying) and I did have to replicate it once already.

  4. Patrick Corcoran says:

    Thanks for the tips. I installed the XP VM and inserted and installed the Integration Services Setup Disk and installed it. However, I cannot see the host drives in the VM, nor do I have an internet connection in the VM at this point. How do I get the Update 961742 from either the net or the host drive into the VM?

    Thanks.

  5. Kyle Beckman says:

    Unlike XP Mode, you won’t be able to see the host drives unless you map them as network drives using the administrative shares (\\hostpcname\c$, \\hostpcname\d$, etc.). If you shut down the VM, you can mount the VHD file as a drive in Windows 8 very easily by double-clicking on it. That would allow you to save the file there. However, it sounds like your networking isn’t fully configured in Hyper-V. You’ll need to have a Virtual Switch configured (most likely as an External network) in Hyper-V and have your VM’s network adapter configured to use that switch.

  6. If the end of XP Mode will make the people to stop to use old IE versions, the XP Mode is gone for a good reason. For good.

    If you are a developer, is time to upgrade your enviroment.

===Leave a Comment===

Login

Lost your password?