> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/knowledge-base/virtual-machines/reasons-a-windows-vm-restarted-unexpectedly.md).

# Reasons a Windows VM Restarted Unexpectedly

How to diagnose why a Windows VM restarted unexpectedly by reviewing VergeOS log messages including kill, poweroff, shutdown, and reset events.

If you have a Windows VM that has recently restarted unexpectedly, the first place to begin is to review the logs from the VM dashboard.\
You can reach the log viewer by navigating from the **Main Menu > Machines > Virtual Machines >** the name of the VM you are investigating **> Logs.**

From the Log view, search through (or filter the results) under the Message section. Several status messages will indicate why the VM stopped running. The following are the most common and a brief explanation of each:

* **Message: VM action 'kill' sent**\
  This indicates that a VergeOS user issued a Kill Power command from the VergeOS interface. The log will indicate the user under the Source column.\
  In this scenario, consult with the system user to determine the reason for issuing this command.
* **Message: VM action 'poweroff' sent**\
  This indicates that a VergeOS user issued a graceful Power Off command from the VergeOS interface. This command successfully interacted with the Guest OS ACPI to gracefully stop the VM. The log will indicate the user under the Source column.\
  In this scenario, consult with the system user to determine the reason for issuing this command.
* **Message: VM has shutdown**\
  This indicates that the shutdown command was issued from inside the guest operating system directly.\
  In this scenario, consult with the guest operating system logs to determine the reason for the shutdown command.
* **Message: VM has reset**\
  This indicates that the restart command was issued from inside the guest operating system directly.\
  In this scenario, consult with the guest operating system logs to determine the reason for the reset command.

{% hint style="info" %}
**Best Practice**

A guest VM running Windows that experiences unexpected restarts is often found to be caused by the Microsoft Windows Update Services being configured to automatically apply updates that require a restart.\
To investigate this further, consult with Knowledge-Base articles about the particular version of the Windows OS.\
One of the best places to start investigating at a Windows Guest level is using **Windows Event Viewer** and reviewing the **Windows Update logs** for more information.
{% endhint %}

***

{% hint style="info" %}
**Document Information**

* Last Updated: 2024-08-29
* vergeOS Version: 4.12.6
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verge.io/knowledge-base/virtual-machines/reasons-a-windows-vm-restarted-unexpectedly.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.