dwknoble's Posts

Since I've reverted to VMWare 15 (as opposed to my copious versions back to 5.5), I'm simply too busy at this point to reinstall 17, find the errors, then reinstall 15 so it works.  I can tell you that my processor is this: Name Windows 10 Pro x64, version 22H2 Product Name Windows 10 Pro Version 22H2 (OS Build 19045.3570) System Start Options NOEXECUTE=OPTIN HYPERVISORLAUNCHTYPE=OFF Kernel Version 10.0.19041.3570 KernelBase Version 10.0.19041.3570 Build Branch vb_release Build Lab 19041.vb_release.191206-1406 Build Lab Ex 19041.1.amd64fre.vb_release.191206-1406 PROCESSOR_IDENTIFIER Intel64 Family 6 Model 44 Stepping 2, GenuineIntel PROCESSOR_LEVEL 6 PROCESSOR_REVISION 2c02 This is from SIW.  The processor is listed in other programs is an i7-900.  It is a 6 core, 12 thread processor, in an HP Pavilion purchased in 2011.  (Yea, I've been hoping to get more current machine, but economics has delayed that.) VMWare does not work with this processor (XSAVE error), which surprised me, as every version I've had in the past works well. Thanks for your reply.

Be careful.  VMWare isn't explicit, but if your processor doesn't support XSAVE, V17 will not permit any virtual machine to power up.    Because of this inadequacy in their documentation (but perhaps it's buried somewhare>), I am now a *former* customer of VMWare.

I'm having the same problem.  My i7-900 processor was purchased in 2011, but does not support XSAVE.  I now have an expensive Vmware Workstation 17 which is absolutely useless to me.  No more VMware for me.  I am now a former customer.