> ## Documentation Index
> Fetch the complete documentation index at: https://docs.advinservers.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Server Stopping Every Hour

> Why a server shuts down or reboots roughly once an hour, and how to fix it.

## Overview

If your server is shutting down or rebooting on its own roughly every hour, the cause depends on which operating system you are running.

* **Windows:** this is almost always caused by the Windows Server Evaluation Edition license expiring. See [Windows](#windows) below.
* **Linux:** this is not expected behavior. See [Linux](#linux) below.

## Windows

Every Windows Server reinstall we provide uses the **Evaluation Edition**, which is only licensed to run for 180 days. See [Windows Server Support](/guides/windows) for details on eligibility and licensing.

Once those 180 days pass without a valid license being applied, Windows enters a state where it automatically initiates a shutdown every hour, along with a notification that the evaluation period has expired. This is expected behavior built into Windows itself, not a fault with your server.

### Confirming This Is the Cause

You can confirm the evaluation has expired by connecting to your server (before it shuts down again) and running the following in an elevated Command Prompt:

```
slmgr /dlv
```

This displays the licensing status. Look for a line indicating the license has expired, or that the machine is in "Notification" mode. You can also check `eventvwr.msc` under **Windows Logs > System** for `EventLog` source events around the time of each shutdown, which will reference the evaluation period ending.

It may also be visible in the bottom right corner, where it says "Windows License is expired."

![License Expired](https://advin-cdn.b-cdn.net/trial-license-3.jpg)

### Resolving It

You have a few options:

<AccordionGroup>
  <Accordion title="Apply a valid Windows Server license">
    If you have your own Windows Server license, you can apply it with:

    ```
    slmgr /ipk <your-license-key>
    slmgr /ato
    ```

    This stops the hourly shutdowns immediately, without needing to reinstall.
  </Accordion>

  <Accordion title="Rearm the evaluation period">
    If you do not have a license yet, you can temporarily extend the evaluation period by running the following in an elevated Command Prompt, then restarting the server:

    ```
    slmgr /rearm
    ```

    This grants another 180 days and stops the hourly shutdowns. It can only be done a limited number of times before Windows requires activation regardless, so this is a temporary workaround rather than a permanent fix, and it may not work on all versions of Windows.
  </Accordion>

  <Accordion title="Reinstall the server">
    Reinstalling Windows Server through the Reinstall tab of the [VPS panel](https://vps.advinservers.com) starts a fresh 180-day evaluation period. See [Server Reinstallation](/guides/reinstall) for how to do this. Remember to back up any data first, as reinstalling wipes the server.
  </Accordion>

  <Accordion title="Switch to Linux">
    If you do not need Windows specifically, reinstalling to a Linux distribution avoids licensing and evaluation limits entirely.
  </Accordion>
</AccordionGroup>

We do not provide Windows Server licenses and cannot extend the evaluation period for you, as this is a restriction set by Microsoft rather than by us.

## Linux

Linux distributions do not have any built-in evaluation period or licensing mechanism that would cause hourly shutdowns or reboots, so this is not expected behavior. This is usually caused by something on the server itself, such as a cron job, a misconfigured watchdog, a kernel panic, or a script left running by a previous action on the server.

If you cannot find the cause, please [open a ticket](https://clients.advinservers.com/contact.php) with:

* The output of the commands above, if available.
* The exact time (and timezone) restarts have occurred.
* Anything that changed on the server before this started happening.

Our team can also check the hypervisor logs on our end to see whether the shutdown is being triggered from inside the server or from the host.