VSV - corruption


  1. Posts : 3
    Windows 7 32 bit
       #1

    VSV - corruption


    Hi all,

    I think I have gotten myself into a predicament and I am hopeful someone can come to my rescue..

    Before my PC crashed I created several Virtual PC's and associated VSV files for their saved state. In those states I had a number of applications open and configured but not saved..I left the applications open.. I left these Virtual environments in a hibernated state so that when I returned back to these environments it would be exactly the same as I had left it with those applications still open and with the configuration details intact...


    I did make a copy of the VSV , VHD, VMC, VMCX and VMC-VPCBACKUP files from my USERS\..\Virtual directory.


    I can access the Hard Drives if I mount them but that is not my prime concern, I would like to have my Virtual environments come out of a hibernated state and I can work on what I was doing as exactly how I left it.

    I keep getting an error message :

    "Cannot start the virtual machine; The hibernated state for this machine is corrupted. You can discard the hibernated state and start the virtual machine. You will lose any unsaved data.."

    I think the outcomes above given to me is not what I want. I do not want to discard the hibernated state and lose any unsaved data..

    I have put a lot development time into the applications within these environments and I desperately need to regain access to the point where I left this development work. It took me months....

    I really look forward in getting help and this despair..


    Chris
      My Computer


  2. Posts : 17,545
    Windows 10 Pro x64 EN-GB
       #2

    Hi Dreamweaver, welcome to the Seven Forums.

    This is going to be one of those posts that needs to be started with "Please do not shoot the messenger" .

    I am afraid there's not much you can do. A corrupted VSV file is pretty much impossible to repair, the only way to get a Virtual PC vm to work when this happens is to delete the VSV file which forces the vm to do a clean boot. I fought and lost the battle with an XP Mode vsv file just a few weeks ago when I was stupid enough to first hibernate XP Mode and immediately thereafter shutdown the host, before the XP Mode had managed to save the VSV. Googling around only told me there was nothing I could do.

    Your post does not make it clear what you have done after the crash. If you still have the crashed Windows installation with all your virtual machines intact, you could try to repair install it which is as an in-place upgrade install using the same Windows version and edition. This keeps all your settings, programs and files and might fix the issue why your computer crashed, allowing you at least access your virtual machines and shutdown them properly.

    Repair Install

    Kari
      My Computer


  3. Posts : 4,566
    Windows 10 Pro
       #3

    Now this is a stretch as I use vmware player:

    But whenever I have a problem with a virtual machine I messed up, or had to much fun with viruses etc; I use the previous versions feature on the vm file to restore it back to a good state. You could try right clicking the folder the vm is stored in, and choose restore previous versions. Then go back a day or two and choose to restore the folder.

    See if that helps.....it works in vmware player but I have no tested it with windows virtual pc. It should still work imo though.


    Then again I might not even be close with this suggestion, so forgive me if I am way out there.
      My Computer


  4. Posts : 17,545
    Windows 10 Pro x64 EN-GB
       #4

    andrew129260 said:
    Now this is a stretch as I use vmware player:

    But whenever I have a problem with a virtual machine I messed up, or had to much fun with viruses etc; I use the previous versions feature on the vm file to restore it back to a good state. You could try right clicking the folder the vm is stored in, and choose restore previous versions. Then go back a day or two and choose to restore the folder.

    See if that helps.....it works in vmware player but I have no tested it with windows virtual pc. It should still work imo though.


    Then again I might not even be close with this suggestion, so forgive me if I am way out there.
    The vsv file on a Virtual PC vm is like the hiberfil.sys file on a physical Windows machine, it contains the data needed by the machine to wake up from hibernation.

    In OP's case this hibernation data contained by the specific vsv file cannot be read because the file is corrupted. Deleting the file allows the vm to boot normally (clean, new boot instead of waking up from hibernation) because when Virtual PC does not find a vsv file it acts as if cleanly booted. Any restore actions at that point would be totally useless as the vm itself works, only the hibernation data cannot be read.
      My Computer


  5. Posts : 4,566
    Windows 10 Pro
       #5

    Kari said:
    andrew129260 said:
    Now this is a stretch as I use vmware player:

    But whenever I have a problem with a virtual machine I messed up, or had to much fun with viruses etc; I use the previous versions feature on the vm file to restore it back to a good state. You could try right clicking the folder the vm is stored in, and choose restore previous versions. Then go back a day or two and choose to restore the folder.

    See if that helps.....it works in vmware player but I have no tested it with windows virtual pc. It should still work imo though.


    Then again I might not even be close with this suggestion, so forgive me if I am way out there.
    The vsv file on a Virtual PC vm is like the hiberfil.sys file on a physical Windows machine, it contains the data needed by the machine to wake up from hibernation.

    In OP's case this hibernation data contained by the specific vsv file cannot be read because the file is corrupted. Deleting the file allows the vm to boot normally (clean, new boot instead of waking up from hibernation) because when Virtual PC does not find a vsv file it acts as if cleanly booted. Any restore actions at that point would be totally useless as the vm itself works, only the hibernation data cannot be read.
    Ah ok, gotcha thanks.
      My Computer


  6. Posts : 3
    Windows 7 32 bit
    Thread Starter
       #6

    VSV Corruption Pt2


    Hi All,

    Let me start off saying thanks to all of those who replied. Great advice but not specific to solving my problem. What I would like to add is more information around the situation:

    Firstly as I mentioned I created Saved States of Virtual PC's.... My Laptop sort of died but I managed to copy VMC, VMCX, VHD, VSV files to a USB key.

    Secondly I copied those files to another laptop expecting to run my virtual machines out of their hibernated state. Of course that did not work as per the error messages posted in the original thread.

    Thirdly what I have discovered is this:. I had managed to boot the original Laptop with the Virtual PC and XP MODE and I can access my Virtual PC's as I had left them in their hibernated state... no error messages.. all good..

    Unfortunately the original laptop has Hard drive issues and I have another replacement laptop which is not the same model as the original. The original is a Lenovo and the replacement is a DELL.

    So the Question is how do I enable and run my Virtual PC's out of their hibernated states as I had left them on the OLD laptop ???

    I know the saved states are not corrupted as I can open them on the original Laptop but the problem of course is opening them in another laptop environment. I am sure there are some systems files that I need to copy over as well and would like to hear back from someone who might know more about how the Virtual Pc environment is configured and how I can go about opening these files normally without the error message about the saved states being corrupted.

    Thanks and Regards
    Last edited by dreamweaver; 24 Jun 2014 at 19:56. Reason: Left out last paragraph; spelling and logic
      My Computer


  7. Posts : 17,545
    Windows 10 Pro x64 EN-GB
       #7

    When for instance exporting a Virtual PC vm to another computer, it should be shut down instead of hibernated exactly for that reason: exporting it in hibernation state usually fails. If the VSV file gives you the corrupted error message, it should be deleted and vm restarted.

    dreamweaver said:
    I had managed to boot the original Laptop with the Virtual PC and XP MODE and I can access my Virtual PC's as I had left them in their hibernated state... no error messages.. all good..
    In that case I repeat what I said in my earlier post:
    Kari said:
    Your post does not make it clear what you have done after the crash. If you still have the crashed Windows installation with all your virtual machines intact, you could try to repair install it which is as an in-place upgrade install using the same Windows version and edition. This keeps all your settings, programs and files and might fix the issue why your computer crashed, allowing you at least access your virtual machines and shutdown them properly.
      My Computer


  8. Posts : 3
    Windows 7 32 bit
    Thread Starter
       #8

    kari said:
    when for instance exporting a virtual pc vm to another computer, it should be shut down instead of hibernated exactly for that reason: Exporting it in hibernation state usually fails. If the vsv file gives you the corrupted error message, it should be deleted and vm restarted.
    Hi Kari,

    I am purposely leaving the Virtual PC in a hibernated state and for some unexplained reason the application I am using will not allow settings to be saved. Therefore what I am trying to achieve is whilst I work out how to save and recall those configurations I have made in this application I need to leave the application open and exit the Virtual PC in a hibernated state and not a FULL EXIT/ shutdown otherwise I loose those configuration settings I have created for this application.

    Just to recap.... The VSV file works 100 % on the old laptop... (Lenovo) no problems and no error messages... However the dilemma is when copying the "VSV, VMC, VMCX & VHD" files to the new hardware configuration laptop ( DELL) is where I experience the problem of getting an error message when trying to come out of a hibernated state of the VIRTUAL PC.

    What I need to ascertain is what other "system" or configuration files I should need to copy over to the new environment to ensure that I do not encounter the "vsv corruption" error message. I know in fact that this file is not corrupted as I can access on the old laptop (Lenovo).

    My objective is NOT to shutdown the VIRTUAL PC for the reasons given above and gain access to the hibernated state of that Virtual PC in the new environment ( DELL) laptop.

    I hope I have made things a little clearer and look forward to your response.


    Regards
      My Computer


  9. Posts : 17,545
    Windows 10 Pro x64 EN-GB
       #9

    I am not able to help you to achieve what you want to. As far as I know, you cannot migrate the saved state. The new XP Mode will have different SID and so on, it will not accept a VSV file from another setup, marking it corrupt.

    All XP Mode file locations if you want to check you've got everything (extract from Virtual XP Machine - Copy

       Information
    By default, XP Mode virtual machine consists of five files when installed and run first time, plus two additional files if XP Mode is hibernated or the Undo Disk feature is enabled. The file names, extensions and default locations are:

    • Windows XP Mode base.vhd
      • XP Mode base disk
      • default location C:\Program Files\Windows XP Mode
    • Windows XP Mode.vhd
      • Virtual Machine virtual hard drive image
      • default location C:\Users\Your_Username\AppData\Local\Microsoft\Windows Virtual PC\Virtual Machines
    • Windows XP Mode.vmcx
      • Virtual Machine description and registration settings
      • default location C:\Users\Your_Username\Virtual Machines
    • Windows XP Mode.vmc
      • Virtual Machine settings file
      • default location C:\Users\Your_Username\AppData\Local\Microsoft\Windows Virtual PC\Virtual Machines
    • Windows XP Mode.vmc.vpcbackup
      • Virtual Machine settings backup
      • default location C:\Users\Your_Username\AppData\Local\Microsoft\Windows Virtual PC\Virtual Machines

      Additional files, only exist when certain criteria is met:
    • Windows XP Mode.vsv
      • Virtual Machine saved state file (hibernation data)
      • default location C:\Users\Your_Username\AppData\Local\Microsoft\Windows Virtual PC\Virtual Machines
      • This file exists only when XP Mode is hibernated or is running. It is deleted automatically every time XP Mode is shut down
    • VirtualPCUndo_Windows XP Mode_X_Y_ZZZZZZZZZZZZZZ.vud
      • Virtual machine Undo-disk (X, Y & Z in the file name are replaced with digits)
      • default location C:\Users\Your_Username\AppData\Local\Microsoft\Windows Virtual PC\Virtual Machines
      • This file exists only if so called Undo Disk is enabled in XP Mode settings


    Kari
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 08:56.
Find Us