none
Creation date of VM is way off.

Answers

  • Hi,

    there's a known bug. While the VM is running, hit the stop service button (or net stop vmms from the command line) and restart it (or net start vmms from the command line).

    Please check the following articles:
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/d2679da3-dd59-424c-b8b7-03ce6325c8b8/hyperv-2012-r2-virtual-machine-creation-date-resets-to-01011601-after-host-reboot?forum=winserverhyperv

    https://www.experts-exchange.com/questions/28548028/My-Hyper-V-2012-Virtual-Machine-Creation-Data-is-being-reset-to-01-01-1601-on-reboot.html

    Regards,
    -Tomi

    Tomi Pietilä

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Blog
    Twitter
    LinkedIn

    Tuesday, March 21, 2017 8:05 PM

All replies

  • Hi,

    there's a known bug. While the VM is running, hit the stop service button (or net stop vmms from the command line) and restart it (or net start vmms from the command line).

    Please check the following articles:
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/d2679da3-dd59-424c-b8b7-03ce6325c8b8/hyperv-2012-r2-virtual-machine-creation-date-resets-to-01011601-after-host-reboot?forum=winserverhyperv

    https://www.experts-exchange.com/questions/28548028/My-Hyper-V-2012-Virtual-Machine-Creation-Data-is-being-reset-to-01-01-1601-on-reboot.html

    Regards,
    -Tomi

    Tomi Pietilä

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Blog
    Twitter
    LinkedIn

    Tuesday, March 21, 2017 8:05 PM
  • Thanks for the response.  I'm old, just not 417 years old...

    This provided the correct link.  To fill in the gaps.

    All VMs having that issue need to be in "Running" state

    Cmd prompt in admin mode.

    Run "net stop <g class="gr_ gr_101 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="101" id="101">vmms</g>"    Wait for service to stop successfully.

    Run "net start <g class="gr_ gr_148 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="148" id="148">vmms</g>"   Once the service <g class="gr_ gr_24 gr-alert gr_gramm gr_run_anim Grammar multiReplace" data-gr-id="24" id="24">is restarted</g> all VMs that were in "Running" state will be reset to the correct creation date.

    MS has known about this for over 2 years?!?  Come on Guys... Fix it already!!!

    If you shut down the VM and reboot the host, it'll go right back to the 17th century...

    Tuesday, March 21, 2017 9:11 PM
  • <g class="gr_ gr_58 gr-alert gr_gramm gr_run_anim Punctuation only-ins replaceWithoutSep" data-gr-id="58" id="58">Ok</g> something very strange went on with that reply.  Let's try again.

    All VMs having that issue need to be in "Running" state

    Cmd prompt in admin mode.

    Run "net stop <g class="gr_ gr_102 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="102" id="102">vmms</g>"    Wait for service to stop successfully.

    Run "net start <g class="gr_ gr_143 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="143" id="143">vmms</g>"   Once the service resumes all VMs that were in "Running" state will be reset to the correct creation date.

    MS has known about this for over 2 years?!?  Come on Guys... Fix it already!!!

    If you shut down the VM and reboot the host, it'll go right back to the 17th century...

    Tuesday, March 21, 2017 9:14 PM
  • Try this in a different browser.  I don't know what is going on with all of that extraneous text.

    All VMs have to be in Running State.

    Cmd prompt in admin mode.

    Run  net stop vmms  and wait until the service is stopped.

    Run  net start vmms   and wait until the service begins again.

    Once the service resumes all VMs that were in the running state will be reset to the correct creation date.

    MS has known about this for over 2 years?!?  Come on Guys... Fix it already!!!

    If you shut down the VM and reboot the host, it'll go right back to the 17th century...

    Tuesday, March 21, 2017 9:19 PM