I'm having trouble with my Windows 10 Technical preview instance and I was thinking if you could help me. All help is very much appreciated.

Host: HP BL460c (intel)

Esxi 5.5

Guest OS: Windows 10 Technical Preview Build 10061

VM version 10

2 CPU's, 8gb memory

When the Guest OS has been powered on AND nobody has used it for exactly 24 hours it crashes. So I revert it from a snapshot and after 24 hours it goes down. If I look at the events in vCenter I can see: "VMware ESX unrecoverable error: (vcpu-0) NOT_REACHED bora/devices/ahci/ahci_user.c:1521" I know it is not a supported Windows version but I was hoping someone might know what this error means and maybe point me to the right direction. All previous windows 10 builds have worked perfectly and from the Windows logs it seems just like someone suddenly pulled the power cord so no luck there.

Me too, i also got the same kind of error messages . But my situation was run the windows server 2016 technical review on vmware workstation 11 . It seems that the current vmware product not yet well supported this kind of version . Waiting the update version to fix this issues out .

We have a fix queued up for the next patch release to address this problem.

It turns out that the most recent builds of Windows 10 will sometimes issue S.M.A.R.T. commands to SATA devices even when the device reports that it does not support S.M.A.R.T., and the unexpected commands are confusing our SATA emulation and leading to the error you're seeing.

The fix will simply ignore the unexpected S.M.A.R.T. commands.

I can't say exactly when we'll have the update in your hands, but I'm hoping it will be reasonably soon. Sorry for the trouble you've all encountered!

This also fixed my Windows 10 problems. I was getting the error within 24 hours of running any Windows 10 VM under ESXi 6, even if I hadn't reverted from a snapshot. The VM simply wasn't running when I went back after a while to do something with it. You have to scan the event log to see that this error occurred, so if you simply see that your Windows 10 VM has shutdown for no obvious reason, this is probably the problem. At first I thought I had some sort of activation issue.