Creation date of VM is way off.


  • I know I'm old, but not this old.  Creation date showing 12/31/1600.  Any thoughts on how this happened and how to fix it?

    • Moved by Garth JonesMVP Tuesday, March 21, 2017 6:58 PM Not a CM12 Q
    Tuesday, March 21, 2017 4:21 PM

All replies

  • You should post this to a Hyper-V forum instead of a System Center Configuration Manager forum.

    Jason | | @jasonsandys

    Tuesday, March 21, 2017 5:13 PM
  • It's a display bug. There is no "created" information, and they chose to handle that as "0". Since the time is 0, it is showing you the start of the NT time epoch, which is January 1st, 1601 (but adjusted for your time zone).

    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    If you found a bug or want the product to work differently, share your feedback.
    <-- If this post was helpful, please click the up arrow or propose as answer.

    Tuesday, March 21, 2017 6:28 PM
  • PowerShell MVP Jeff Hicks has an article on how to update it:

    Eric Siron
    Altaro Hyper-V Blog
    I am an independent contributor, not an Altaro employee. I accept all responsibility for the content of my posts. You accept all responsibility for any actions that you take based on the content of my posts.

    Wednesday, March 22, 2017 3:10 AM
  • Hi,
    Are there any updates on the issue?
    You could mark the reply as answer if it is helpful.
    Best Regards,

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Thursday, March 30, 2017 2:20 AM