http://blogs.msdn.com/b/virtual_pc_guy/archive/2007/11/29/troubleshooting-corrupt-vm-configuration-files-with-virtual-server.aspxIf you have an installation of Virtual Server that has been working correctly - but now you are finding that: The Administrative website loads, but does not display any virtual machines. The Administrative website loads, but displays an error messageen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/virtual_pc_guy/archive/2007/11/29/troubleshooting-corrupt-vm-configuration-files-with-virtual-server.aspx#6624586Sat, 01 Dec 2007 09:34:34 GMT91d46819-8472-40ad-a661-2c78acb4018c:6624586Xepol<p>This might also be related to how Virtual Server checks to see if the virtual state file exists (by creating a directory of the same name. &nbsp;If it can create the directory, it doesn't exist. &nbsp;Unfortunately, it doesn't delete the directory, so when it goes to create the .vsv file of the same name, it obviously fails and virtual server goes slightly mental until you force it down, find the directories and delete them. &nbsp;Then, for some bizarre reason, it doesn't recreate the folders and will properly recreate the .vsv files when it restarts)</p> <p>Just wish they would just check if the file exist the way most people do... ( <a rel="nofollow" target="_new" href="http://blogs.msdn.com/oldnewthing/archive/2007/11/09/6001644.aspx">http://blogs.msdn.com/oldnewthing/archive/2007/11/09/6001644.aspx</a> )</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=6624586" width="1" height="1">