VMware Cloud Community
TwincaAdmin
Enthusiast
Enthusiast
Jump to solution

New Windows 10 pro 64Bit VM on Esxi 6.7 sequential reboots every 10 minutes

I've just created a new VM with Windows 10 Pro 64 bit. with 8 GB RAM on EXsi Host (vSphere 6.7).

But for every 10 minutes the VM Shout down and restart... Anyone have seen this before?

Best regards

JOM

Reply
0 Kudos
1 Solution

Accepted Solutions
TwincaAdmin
Enthusiast
Enthusiast
Jump to solution

I've installed A new VM And now it is working, so it seems like there was an error in the windows installation.

So creating a new Virtual Machine solved the issue.

View solution in original post

Reply
0 Kudos
7 Replies
a_p_
Leadership
Leadership
Jump to solution

I haven't seen this happening so far. Anyway, what may help to find out what may be causing this is to check the VM's vmware.log file, as well as the VM's Windows Event Logs for related entries.


André

Reply
0 Kudos
TwincaAdmin
Enthusiast
Enthusiast
Jump to solution

2020-04-28_17-53-26.png

Seem like it is losing power somehow...  Kernel-power  Issue in windows log

Reply
0 Kudos
TwincaAdmin
Enthusiast
Enthusiast
Jump to solution

How do get to that Log file, and where is it located?

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

That would be the first virtual power loss that I see ;-)))

The vmware.log is stored in the VM's folder, and can be downloaded from the ESXi UI using the datastore browser.

André

Reply
0 Kudos
TwincaAdmin
Enthusiast
Enthusiast
Jump to solution

God morning...

I'll check the vmware.log and let you know... I've been reading some places that it might be related to the licensing on Windows... can that be true... it is an OEM License... but it is brand new.

I've been using OEM Licenses for VM's before and it has never been a problem?

Reply
0 Kudos
TwincaAdmin
Enthusiast
Enthusiast
Jump to solution

I've attached the Files from the VM...

Reply
0 Kudos
TwincaAdmin
Enthusiast
Enthusiast
Jump to solution

I've installed A new VM And now it is working, so it seems like there was an error in the windows installation.

So creating a new Virtual Machine solved the issue.

Reply
0 Kudos