D'Arcy from Winnipeg
Solution Architecture, Business & Entrepreneurship, Microsoft, and Adoption

Adventures in Windows 7 and Virtual PC

Thursday, October 1, 2009 11:32 AM

My work recently started rolling out Windows 7 as our production OS and I was lucky enough to get on as one of the early adopters! I got my laptop back at end of day yesterday freshly paved with Win 7.

Today I started my day by booting up and trying to fire up a VPC environment that I use for my dev work. To my dismay I was met with this message:


The problem is that I had just saved my vm’s state instead of doing a full shutdown. Apparently moving a hibernated vm to Win 7 is not a good idea. Luckily, I found a work around on the Giant Bass Stacks blog (dunno who the guy/gal is that runs it). Basically you just go to your Virtual Machines folder in Win 7 and create a new machine that uses your existing virtual hard drive. You won’t start the machine from its saved state but it will start up and be usable. As long as you saved your work before you saved state, you’ll be fine.

Remember that since you’re creating a new virtual machine to get this scenario to work you’ll need to set the ram, networking, and other settings required by your vm.

However, before I got to that point I encountered a different issue getting this to work. When I tried to create the new virtual machine in the Virtual Machines directory I received this message:


TXT stands for Trusted Execution Technology and I had to reboot into the BIOS and disable it. TXT is what’s used in the dialogue but may not be how your BIOS labels it. For my Dell E6400 It was under the virtualization node and then just Trusted Execution…no TXT listed anywhere.

So now everything is running smoothly and hopefully these two little hiccups are the end of my issues. So far so good!



No comments posted yet.

Post a comment