Guest computer state is not saved when you shut down the host computer on Virtual Server 2005

This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
If you shut down a computer that is hosting a Microsoft Virtual Server 2005 guest computer, the guest computer state is not saved. For example, the guest computer state is not saved when you shut down the host computer locally, remotely, or by a restart after you apply a software update.
RESOLUTION
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this issue, modify both a Virtual Server 2005 property, and a Windows registry value, on the host computer.

Modify the Action when Virtual Server stops property in Virtual Server 2005

To do this, follow these steps:
  1. Start the Virtual Server Administration Web site.
  2. Under Virtual Machine, point to Configure, and then click the virtual machine that you want to work with.
  3. Under YourVirtualMachineName” Configuration, click General properties.
  4. In the Action when Virtual Server stops box, click Save state, and then click OK.

    Alternatively, you can click Shut down guest OS. However, this option requires that you install the Virtual Machine Additions and keep them up to date.For additional information about how to install the Virtual Machine Additions in a guest computer in a Virtual Server 2005 environment, visit the following Microsoft Web site:Important Microsoft Windows NT 4.0 virtual machines do not support the Shut down guest OS option. Therefore, you must use the Save state option.
  5. Quit the Virtual Server Administration Web site.

Modify the WaitToKillServiceTimeout registry entry on the host computer

To do this, follow these steps:
  1. Start Registry Editor.
  2. Locate, and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
  3. Right-click WaitToKillServiceTimeout, click Modify, type 90000, and then click OK.

    Important If you use the Shut down guest OS option, right-click WaitToKillServiceTimeout, click Modify, type 240000, and then click OK.

    Note If the WaitToKillServiceTimeout entry or value does not exist, you must create it. To do this, follow these steps:
    1. Right-click Control, point to New, click String Value, type WaitToKillServiceTimeout, and then press ENTER.
    2. Right-click WaitToKillServiceTimeout, click Modify, type 90000, and then click OK.
  4. Restart the host computer.
Properties

Article ID: 888745 - Last Review: 12/09/2015 01:52:16 - Revision: 1.3

Microsoft Virtual Server 2005 Standard Edition

  • kbnosurvey kbarchive kbtshoot kbprb KB888745
Feedback
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)