D365 FO VHD license expiry issue

(1) Share

Report

Posted on by MuthukumaranAX

2,901

Hi Experts

I have downloaded VHD file from LCS and configured in Hyper-V, but I can see that license is valid for 9 days.

Is it possible to extend this license for long duration (for an year or so)?

All responses (5)

Answers (2)

Hana Xue Microsoft Employee on at

Like (0)

Report

D365 FO VHD license expiry issue

Hi,

If the following answer is helpful, please mark it as verified to help other users of the forum.

Best Regards,

Hana
Verified answer

Hana Xue Microsoft Employee on at

Like (0)

Report

D365 FO VHD license expiry issue

Hi,
You can check out this blog https://serverdecode.com/extend-evaluation-period-windows-server/
, which describes it very clearly. On Windows Server 2022, 2019, and earlier versions, it is possible to extend the evaluation period beyond 180 days, however, you can only do this a few times because the command resets the evaluation period to 180 days and "Reset Set" count decreases by "1". If the reset count reaches "0" you will not be able to reset the license again.
Best Regards,
Hana
Verified answer

André Arnaud de Cal... 294,206 Super User 2025 Season 1 on at

Like (0)

Report

D365 FO VHD license expiry issue

Hi MuthukumaranAX,

Note that the Operating system, SQL server, and more come as evaluation licenses. As Anthony mentioned, you can extend the evaluation period several times, but it doesn't grant you a perpetual license. The extension period is for 120 or 180 days and you can extend it 2 or 3 times.
Suggested answer

Anthony Blake 2,359 Super User 2025 Season 1 on at

Like (0)

Report

D365 FO VHD license expiry issue

Alternative:

Use the brilliant d365fo.tools powershell library to rearm windows:

https://github.com/d365collaborative/d365fo.tools/blob/development/docs/Invoke-D365ReArmWindows.md

Invoke-D365ReArmWindows -Restart
Suggested answer

Anthony Blake 2,359 Super User 2025 Season 1 on at

Like (0)

Report
D365 FO VHD license expiry issue

In an admin command prompt, try running:

slmgr -rearm