I suggest to upgrade to the latest player version and try again.-----
Please do not forget to assign reward points, if you find an answer useful.
Downloading and installing the latest player (download) might be a good idea.
However it will not fix the issue you are reporting here.
The same issue is reported at the VMware Fusion forum and while the product is different, the problem is the same.
TL;DR is that you'll have to wait on a fix from either Microsoft or VMware.
It is however not a problem to install and run Windows 10 under VMware, it is the reserve program that complains.
The free upgrade will also be available via different means after Windows 10 has been released.
Wil| Author of Vimalin. The VMware Fusion Backup app for virtual machines |
| More info at http://www.vimalin.com |
| Twitter @wilva |
| Wiki at http://www.vi-toolkit.com |
| http://www.vimalin.com/why-is-time-machine-not-a-good-backup-for-virtual-machines/ |
1 person found this helpful
It may (or may not) be a problem to run Windows 10 as a VMWare guest, however since the early releases of fbl_impressive builds roughly half fail to upgrade and fall over with a complaint about driver installation. As they are 'simple' installs from a driver standpoint, this suggests that a common point of failure is VMWare graphics.
Irrespective of the Windows 10 upgrade process we really do need to see some improvement in VMWare graphics pass-through support. I had hoped that we would have been seeing some VMWare betas by now, but it looks as though VMWare have their priorities a bit askew.
Thanks for the responses.
Downloading the latest version was the first thing I did. It did not help.
I've seen that before that a compatibility test says the VMWare display driver is not compatible, but VMWare still runs without any apparent problems.
As an end user can't do much now.
Agreed that when the final release of Window 10 is out and maybe after a few fixes for some initial bugs would be a better time to try the install if now better drivers a provided by then.
Just wanted to get prepared.
Removing the files will cause new ones to be created prior to the upgrade. Editing the telemetry file to simulate a success may work. We will only know once the update is out.
I was able to simulate a successful compatibility check by editing the following file:
Replacing the contents with:
"JsonSuccessfullyWritten" : true,
"JsonVersion" : 3,
"JsonCreationTime" : "130824843821388157",
"CompatSectionCount" : 0,
Basically, I changed the "CompatSectionCount" to 0,and removed the contents of "CompatSections".
This is what you get:
This was done on W7 running in Fusion. The only compatibility failure I had was the VMware SVGA 3D driver.
This change in Appriser.JSON obviously "solves" the compatibility report issue, but it does not allow the installation of/upgrade to Windows 10.
I have Windows 7 Home Premium running on Fusion 7.1.2 and also run Windows 10 TP on a separate VM today without any problems.
Any other good ideas?
Best regards, Ari