My Hyper-V 2012 Virtual Machine Creation Data is being reset to 01/01/1601 on reboot

Hello, I'm running Hyper-V 2012 on a server running Windows Server 2012 R2. However, when I create a new VM, it's creation date defaults to 01/01/1601 whenever the physical host is restarted. Please could you assist me in ensuring that the correct creation date is again showing.

Much appreciated.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

VB ITSSpecialist ConsultantCommented:
This is apparently a known bug at the moment which has been acknowledged by a senior member of Microsoft's Hyper-V team. Please see John Howard's response here:

The fix is to restart the Hyper-V Virtual Machine Management service but I don't think this will fix the problem permanently. It looks like we'll need to wait for an update from Microsoft to address this bug.
alltogetherAuthor Commented:
Thanks for your prompt response.

However, restarting the "Hyper-V Virtual Machine Management Service" didn't resolve the problem and running the "net stop vmms" command from the CMD Prompt gave me an error message of the "The service name is invalid"

Any further assistance you can give me is much appreciated.

Kind regards.
VB ITSSpecialist ConsultantCommented:
running the "net stop vmms" command from the CMD Prompt gave me an error message of the "The service name is invalid"
That's strange. Running that command on my 2012 R2 server with the Hyper-V role installed restarted the Hyper-V Virtual Machine Management Service for me.
vmms.pngDid you refresh you view in the Hyper-V Management Console after you restarted the service?

Whatever the case, it's been acknowledged by Microsoft as a known bug. I believe the issue will reappear whenever the Hyper-V host gets restarted anyway so the above is just a temporary workaround.

One thing I did notice on my end was that the Created timestamp was corrected for all Running VMs when I restarted the service. Any VMs which were not running still had their Created timestamps set to 01/01/1601.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
alltogetherAuthor Commented:
Hello, my apologies, I needed to run the command under "Command Prompt (Admin)".

I also needed to ensure that the VM was running.

Thanks very much for your wonderful help and support. I'll look out for the future Microsoft patch..

Kind regards.
VB ITSSpecialist ConsultantCommented:
Ah yes, good ol' UAC at it's best. Glad I could help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.