Virtual PC Console window doesn’t show up when launching
At Avanade, we tend to develop all of our projects in controlled virtual environments for obvious reasons. I am a big fan of VMWare products, notably VMWare Workstation, but at work we use Microsoft Virtual PC 2007. Something annoying happened with Virtual PC this week. For some obscure reason, the Virtual PC Console simply didn’t show up or disappeared from the screen every time I clicked on it via the taskbar. At first, I thought the application crashed, but Process Explorer showed me otherwise, as I could clearly see that the Virtual PC process was running. The problem seems to be that the screen position of the Virtual PC Console window was modified in the configuration file used by it. I don’t know why that happened, but I do know how to fix it.
Here are the steps to follow if the Virtual PC Console window doesn’t show up or tends to disappear every time you click on it via the taskbar:
- Make sure none of the virtual machines are currently running. If they are, save their sessions or shut them down. Also, kill the Virtual PC process if it’s still running. Have no mercy.
- If you’re using Windows XP, go to the Documents and Settings\$USER$\Application Data\Microsoft\Virtual PC folder. If you’re using Windows Vista, go to the Users\$USER$\AppData\Roaming\Microsoft\Virtual PC folder. Both of these root directories should be located in your system drive (C:\ for most users).
- Edit the Options.xml file with your favorite text editor (Notepad++ of course!)
- Search for the <window> element because it holds the location information for the console window (in my case, the <window> element was located at the end of the file). Refer to Figure 1 for an example of what the <window> element looks like.
- Take a look at the values for both the <left_position> and <top_position> elements. These values (4294935296) seem way out of proportion for our current monitors and screen resolutions don’t you think? Change the value of these elements to something more realistic, such as 100. Take a look at Figure 2 to see what I mean by that.
- Save the file and launch Virtual PC again. This time you should see the Console window in the top and left part of the screen.
Figure 1. We can clearly see that the values for the left (<left_position>) and top (<top_position>) don’t make sense.

Figure 2. We simply changed the values for the left and top position to something more realistic.

Similar posts you might be interested in reading:
- "Copying a file too large for the destination file system"…Yeah, right!
- Another jewel from Sysinternals: Desktops, a multiple virtual desktops manager
- Part II: Setting Up Our Build Server With TeamCity
- Using the “Source Control – Team Foundation” toolbar to perform common TFS operations on the current document within Visual Studio
- Avoid calling a virtual or abstract method from a constructor in C#…especially in VB!
- ReSharper 3.1 Released and Getting Better Than Ever!
- Microsoft releases .NET 3.5 SP1, SQL Server 2008 RTM and Entity Framework/Data Services






RobinB:
This is exactly the problem I was experiencing, with the same ridiculous screen position values in the options.xml. Thanks for the solution!
January 26, 2009, 7:22 amjohnC:
Excellent – Worked as soon as I made the above change.
February 19, 2009, 12:24 pmRobin:
Thank you very much!
February 26, 2009, 12:29 pmAlan_P:
Thanks, I spent two hours trying to resolve the same problem this morning until I found your great solution. The only minor issue I had was that I needed to kill the Virtual PC process (or reboot) before I was able to save the changes to the Options.xml file because the process had the file open.
March 11, 2009, 10:07 ampay:
That was my problem to.
November 6, 2009, 2:57 pmTnx 4 sharing.
Björn:
Saved me many hours of problems.
Thanks!
November 30, 2009, 4:57 am