Windows server 2019 eval - 180day license turned to grace period after reinstall

Ian M 20 Reputation points


I just recently started re-learning windows server administration to get back into IT-work after a couple years in another field.

After doing some unrelated clean up on my disk, and helping a friend install a fresh OS on another SSD, i accidentaly deleted my original .ISO for windows server 2019 eval x64. I re-downloaded the ISO, created a new VM in Azure HYPERV, configured the vswitch for some lab work with AD, DNS and DHCP and so on.

Now my slmgr /dll all shows me i am unlicensed and am on my grace period - 10 days. Is there any way to fix this, or do i need to create a new email and install a new ISO connected to a dummy email account?

name: ServerDataCenterEval edition"

Description: Windows(R) Operating system, TIMEBASED_EVAL chanel

Partial product key: H6F8M

Time Remaining: 14360 minute(s) (10 day(s))


Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,321 questions
0 comments No comments
{count} votes

Accepted answer
  1. Dave Patrick 426K Reputation points MVP

    The virtual machine will need to at least temporarily connect to internet for activation. Once the activation completes then you can disconnect from internet for the remainder of the 180 day evaluation.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
  1. Dave Patrick 426K Reputation points MVP

    The ISO evaluation is meant for an on-premise evaluation. The evaluation needs to contact microsoft activations servers to complete the eval activation otherwise it reverts to un-activated in 10 days. Also note that Azure has its own evaluation model.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    1 person found this answer helpful.

  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more