Windows Server 2025 Evaluation Edition Prematurely Expiring (multiple instances, inside 30-days of 180-day trial)

Question

I just want to preface that this occurred on four-out-of-four (100% affected rate) instances of Windows Server 2025 Datacenter (evaluation edition), inside of 51-days, for what should have been a valid trial period of 180-days.

I activated at the 10-day mark, offline, to consume the single rearm count but they still expired well before the 180-day eval boundary.

first instance:

second instance:

Anybody else experiencing this? Is there a known fix?

Answer 1

Hello Mario4Hire,

What you are describing is a licensing and activation anomaly with the Windows Server 2025 Datacenter Evaluation Edition. By design, the evaluation media is supposed to grant 180 days from installation before expiration, with one permitted rearm (slmgr /rearm) that resets the evaluation period. The error you are seeing, where the system expires around the 50‑day mark despite being activated offline, indicates that the evaluation SKU is not honoring the full 180‑day boundary.

This is not expected behavior. The evaluation edition is hardcoded to time out after 180 days, and the rearm should extend it properly. If all four of your instances expired prematurely, this points to a bug in the evaluation build rather than a misconfiguration on your side. Microsoft has acknowledged similar issues in past evaluation releases (for example, Server 2019 evaluation builds had early expiration problems until patched).

There is no supported registry or configuration change that can override the evaluation timer. The only reliable options are either to redeploy with fresh evaluation media or to move to licensed media (Datacenter or Standard with a valid key). If you want to confirm the exact expiration date, run:

slmgr /dlv

and check the “Time remaining” field. If it shows less than expected, that confirms the evaluation timer is misreporting.

At this point, the best practice is to wait for Microsoft to release updated evaluation ISOs or servicing updates that correct the premature expiration. Since this is a licensing subsystem issue, there is no fix you can apply manually without moving to a full licensed edition.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Domic Vo.