Windows Server Shuts Down Every Hour? Check the License

The server isn't shutting down every hour because of a bug. It does exactly what its license tells it to.

“The printers no longer work.” That is how the report began at a small industrial company. The SuperSupport agent at the workstation determined that the printer was not the problem, but that the print server was unreachable. The server was restarted – and after about an hour it shut itself down again.

The cause: The Hyper-V host was not licensed and therefore shut down automatically – and with it all virtual machines, including the print server. The print server itself also had no valid license. Once both servers were licensed, everything ran again.

Here is how to recognize the pattern and fix it.

Why does a Windows Server shut down every hour?

Usually because an evaluation version has expired. Windows Server can be tested for 180 days as an evaluation version. If it is not converted to a full version afterward, the Windows License Monitoring Service (wlms.exe) shuts the server down automatically about every hour.

This often happens like this:

• A server was installed “for testing” with an evaluation ISO – and then stayed in production.
• A template for new VMs is based on an evaluation version.
• When moving to new hardware, the license was not taken along.

A server that is not activated but has a normal version, on the other hand, does not shut down hourly – it shows notices and restricts personalization. The hourly shutdown is typical of the evaluation.

How do I recognize the problem?

By the pattern and in the event log.

• Pattern: After starting, the server runs for about an hour, then shuts down without warning.
• Event Viewer › Windows Logs › System: Event 1074, source User32, triggered by C:\Windows\system32\wlms\wlms.exe, with a note about the expired license.
• On the desktop, the notice “Windows license is expired” appears at sign-in.

With PowerShell:

Get-WinEvent -FilterHashtable @{LogName='System'; Id=1074} -MaxEvents 10 |
  Select-Object TimeCreated, Message | Format-List

Step 1: Check the edition and license status

In a Command Prompt as administrator:

DISM /online /Get-CurrentEdition
slmgr /dlv

• If Current Edition says something like ServerStandardEval or ServerDatacenterEval, it is an evaluation version.
• slmgr /dlv shows the license status and, for an evaluation, the remaining time.

Which editions are suitable as a target is shown by:

DISM /online /Get-TargetEditions

Step 2: Convert the evaluation to a full version

Without reinstalling – with a valid product key:

DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula

A restart is needed afterward, possibly twice. Then use slmgr /dlv to check whether the server is shown as licensed.

Important:

14 days free

IT support that fixes itself.

SuperSupport fixes IT problems right on the device, before they turn into tickets. Try it free for 14 days.

Start free trial

• This takes a while – best run it right after a restart so that the server doesn't shut down in the middle of the conversion.
• On domain controllers, the conversion does not work directly. A different route is needed there, such as setting up a new DC with a full version.
• For volume licenses, the matching key can be found in the Microsoft 365 admin center or the licensing portal.

Step 3: Don't forget the virtual servers

Every Windows Server VM needs its own valid license. In the real-world case, not only the host but also the print server was unlicensed – after fixing the host, that would have been the next problem.

• Windows Server Standard licenses two Windows Server VMs per fully licensed host.
• Windows Server Datacenter licenses an unlimited number of VMs on the host.
• The VMs can be activated through AVMA (Automatic Virtual Machine Activation) via the host if the host uses Datacenter, or with their own key.

Go through all VMs once:

Get-VM | Where-Object State -eq 'Running' | Select-Object Name
# in each VM:
cscript C:\Windows\System32\slmgr.vbs /dli

Why did all the printers fail at once?

Because the print server was a VM on the host that shut down. When the Hyper-V host shuts down, all virtual machines are ended too. For users, it looks as if printers, drives and programs all have a problem at the same time – yet the cause is in one place.

That is why, whenever “nothing works”, it is always worth asking: What do the affected services have in common? Often it is the same host, the same switch or the same power supply.

If only individual printers are affected, the cause is more likely on the client: see Printer not printing: fix the print queue.

How do I prevent this in the future?

• Don't use evaluation ISOs for production servers – or plan the conversion right after installation.
• Check the license status of all servers regularly, for example with a script or the RMM.
• Keep a license overview: which host, which edition, how many VMs, which key.
• Set up monitoring for unexpected restarts (events 1074 and 6008) – then the pattern is noticed before users call.

How does SuperSupport help with outages like this?

In the case described, the SuperSupport agent at the workstation determined that it was not the printer but the print server that was unreachable – and the report went to IT with the right lead from the start. Servers and licenses are still handled by IT or the MSP. What this looks like for internal IT teams and MSPs is described on the respective pages.

Frequently asked questions

Why does my Windows Server shut down every hour?

The most common reason is an expired evaluation version of Windows Server. After the trial period ends, the license monitoring service shuts the server down automatically about every hour. The event log shows an entry with ID 1074, triggered by wlms.exe.

How do I check whether my server is an evaluation version?

In a Command Prompt as administrator, run DISM /online /Get-CurrentEdition. If it says something like “ServerStandardEval” or “ServerDatacenterEval”, it is an evaluation version. slmgr /dlv additionally shows the license status and the remaining time.

Can I activate an evaluation version without reinstalling?

Yes. With DISM /online /Set-Edition and a valid product key, the evaluation can be converted to a full version. A restart is needed afterward. On domain controllers, this does not work directly.

Why are all the VMs gone along with the host?

When the Hyper-V host shuts down, all virtual machines on it are ended too – print server, file server, applications. That is why many services seem to fail at the same time even though there is only one license problem.

Do the virtual servers need a license too?

Yes. Every Windows Server VM needs a valid license. Windows Server Standard covers two VMs per fully licensed host, Datacenter an unlimited number. The VMs are then activated through AVMA or with their own key.

14 days free

IT support that fixes itself.

SuperSupport fixes IT problems right on the device, before they turn into tickets. Try it free for 14 days.

Start free trial