On Windows 10 Pro:

Messages are ".. required administrative rights . . ." but I am an admin. Tried running setup .exe "as an administrator" but gives same error trying to install services.

Hello,

Not sure whether I should come here or to the linux amdgpu developers for this one?

With both the current simcity and simcity 4 games there is an issue where the lighting is not correct after having switched from the AMD drivers to the AMDGPU open source drivers on my linux host where the Win7 Pro VM resides. The screenshots attached probably provide a better explanation than I can write for this one. I had not issues with the previous versions of the ati-drivers versions 15.12, 15.9, etc.

My host is running kernel 4.9.33 and Workstation 12.5.7.

Can i get PowerCLI Script for More than 10 Days Power off VM list in the VCenter... pls Assist

I'm trying to set up NAT networking in my VMware Fusion 8.5.6 Pro environment using a hard-coded IP address in the DHCP settings along with port forwarding in the NAT configuration settings.  In general, I am attempting to follow the process described at https://medium.com/@tuweizhong/how-to-setup-port-forward-at-vmware-fusion-8-for-os-x-742ad6ca1344 which seemed to provide the best documentation on how to set this up.

I first tried creating a new, custom network configuration (which showed up as vmnet3), but I abandoned that and just tried getting the existing vmnet8 NAT adapter to work.

I first edited (via sudo nano) my vmnet8 dhcpd.conf file (located in /Library/Preferences/VMware Fusion/vmnet8) to add a fixed IP address.  I made sure the address was outside the reserved IP range within the "DO NOT CHANGE" section of the dhcpd.conf file.

# Configuration file for ISC 2.0 vmnet-dhcpd operating on vmnet8.
#
# This file was automatically generated by the VMware configuration program.
# See Instructions below if you want to modify it.
#
# We set domain-name-servers to make some DHCP clients happy
# (dhclient as configured in SuSE, TurboLinux, etc.).
# We also supply a domain name to make pump (Red Hat 6.x) happy.
#




###### VMNET DHCP Configuration. Start of "DO NOT MODIFY SECTION" #####
# Modification Instructions: This section of the configuration file contains
# information generated by the configuration program. Do not modify this
# section.
# You are free to modify everything else. Also, this section must start
# on a new line
# This file will get backed up with a different name in the same directory
# if this section is edited and you try to configure DHCP again.


# Written at: 04/26/2017 11:39:58
allow unknown-clients;
default-lease-time 1800;                # default is 30 minutes
max-lease-time 7200;                    # default is 2 hours


subnet 192.168.110.0 netmask 255.255.255.0 {
  range 192.168.110.128 192.168.110.254;  option broadcast-address 192.168.110.255;  option domain-name-servers 192.168.110.2;  option domain-name localdomain;  default-lease-time 1800;                # default is 30 minutes  max-lease-time 7200;                    # default is 2 hours  option netbios-name-servers 192.168.110.2;  option routers 192.168.110.2;
}
host vmnet8 {  hardware ethernet 00:50:56:C0:00:08;  fixed-address 192.168.110.1;  option domain-name-servers 0.0.0.0;  option domain-name "";  option routers 0.0.0.0;
}
####### VMNET DHCP Configuration. End of "DO NOT MODIFY SECTION" #######
host R9NoBIM {
hardware ethernet 00:50:56:3E:44:20;
fixed-address 192.168.110.50;
}

My VM name is R9NoBIM.  Per the instructions on the first URL above, I set the host to the name of my VM.  (Is this what it should be?  I also tried using vmnet8 as the host here, thinking that this section would override the "DO NOT MODIFY" section above, but that didn't work, either.)

I quit, then restarted Fusion.

I then edited my nat.conf file to add the port, 8001 (http) that I wished to have forwarded, using the IP address I designated in the dhcpd.conf file above:

# VMware NAT configuration file


[host]


# NAT gateway address
ip = 192.168.110.2
netmask = 255.255.255.0


# VMnet device if not specified on command line
device = vmnet8


# Allow PORT/EPRT FTP commands (they need incoming TCP stream ...)
activeFTP = 1


# Allows the source to have any OUI.  Turn this on if you change the OUI
# in the MAC address of your virtual machines.
allowAnyOUI = 1


# Controls if (TCP) connections should be reset when the adapter they are
# bound to goes down
resetConnectionOnLinkDown = 1


# Controls if (TCP) connection should be reset when guest packet's destination
# is NAT's IP address
resetConnectionOnDestLocalHost = 1


# Controls if enable nat ipv6
natIp6Enable = 0


# Controls if enable nat ipv6
natIp6Prefix = fd15:4ba5:5a2b:1008::/64


[tcp]


# Value of timeout in TCP TIME_WAIT state, in seconds
timeWaitTimeout = 30


[udp]


# Timeout in seconds. Dynamically-created UDP mappings will purged if
# idle for this duration of time 0 = no timeout, default = 60; real
# value might be up to 100% longer
timeout = 60


[netbios]
# Timeout for NBNS queries.
nbnsTimeout = 2


# Number of retries for each NBNS query.
nbnsRetries = 3


# Timeout for NBDS queries.
nbdsTimeout = 3


[incomingtcp]


# Use these with care - anyone can enter into your VM through these...
# The format and example are as follows:
#<external port number> = <VM's IP address>:<VM's port number>
#8080 = 172.16.3.128:80
8001 = 192.168.110.50:8001


[incomingudp]


# UDP port forwarding example
#6000 = 172.16.3.0:6001

After this I stopped, then restarted my networking by running the following commands in Terminal:

sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start

I confirmed that the networking file within the /Library/Preferences/VMware\ Fusion directory reflected the NAT entry:

VERSION=1,0
answer VNET_1_DHCP yes
answer VNET_1_DHCP_CFG_HASH 946E9174153882B15F5D274344959525D511212F
answer VNET_1_HOSTONLY_NETMASK 255.255.255.0
answer VNET_1_HOSTONLY_SUBNET 192.168.37.0
answer VNET_1_VIRTUAL_ADAPTER yes
answer VNET_8_DHCP yes
answer VNET_8_DHCP_CFG_HASH F171831A724DDD8020D6584939B78429F35D4E1D
answer VNET_8_HOSTONLY_NETMASK 255.255.255.0
answer VNET_8_HOSTONLY_SUBNET 192.168.110.0
answer VNET_8_NAT yes
answer VNET_8_VIRTUAL_ADAPTER yes
add_nat_portfwd 8 tcp 8001 192.168.110.50 8001
add_bridge_mapping en0 2

I've tried various configurations, using different adapters, etc., but I came back to the simplest approach of modifying the vmnet8, default NAT adapter.  After making my first attempt, and ever since then, the Networking settings for both the general Fusion Preferences > Networking, as well as the Network Settings pane for my VM are all grayed out, not allowing me to change them.  I've seen this posted elsewhere (as in  Network Settings options greyed out in Fusion Pro 7.1.0 ), but I haven't been able to get the ability to change the settings via the GUI to be restored, even after following a variety of tips that seemed to work for others.

Here is the general Fusion Network Settings pane. Even though I've unlocked the settings at the bottom, the settings pane remains grayed out:

Here is the Network Settings pane for my specific VM, also completely grayed out an uneducable:

I am able to change the network adapter via the Virtual Machine > Network Adapter menu, but when I select NAT, the VM client (Windows 2012) just reports that the Media State of the adapter is "Media disconnected".

I found a post that recommended checking the vnetlib log for errors.  Here is the section at the end of the log that gets written after restarting the vmware networking:

##multiple lines consisting of the following two lines##
Apr 26 11:37:03 VNLAdapterStatus - ioctl: SIOCGIFFLAGS failed, error: Device not configured
Apr 26 11:37:04 VNLAdapterStatus - ioctl: SIOCGIFFLAGS failed, error: Device not configured
Apr 26 11:37:04 VNL_EnableNetworkAdapter - Successfully enabled hostonly adapter on vnet: vmnet1
Apr 26 11:37:04 VNL_StartService - Started "DHCP" service for vnet: vmnet1
Apr 26 11:37:04 VNLNetCfgLookupNATPortFwd - List of NAT forwarded ports is empty
Apr 26 11:37:04 VNLNATReadPortForward - Failed to read TCP port forward config info.
Apr 26 11:37:04 VNL_StartService - Started "NAT" service for vnet: vmnet8
Apr 26 11:37:04 VNLAdapterStatus - ioctl: SIOCGIFFLAGS failed, error: Device not configured
Apr 26 11:37:04 VNL_EnableNetworkAdInternet Software Consortium DHCP Server 2.0
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.


Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html


Configured subnet: 192.168.110.0
Setting vmnet-dhcp IP address: 192.168.110.254
Opened: `J,Qˇ
Recving on     VNet/vmnet8/192.168.110.0
Sending on     VNet/vmnet8/192.168.110.0
apter - Successfully enabled hostonly adapter on vnet: vmnet8
Apr 26 11:37:04 VNL_StartService - Started "DHCP" service for vnet: vmnet8
Apr 26 11:37:04 VNL_Unload - Vnetlib unloaded.

The Bridged networking adapter works without any problem.  But in the setup I'm needing to establish I need to use NAT with an IP address that doesn't change, so I can rely on my port forwarding rules to work.

Any help on this would be greatly appreciated!

Bonjour,

J'ai une VM msdos 6 avec des outils de développement du siècle dernier pour une besoin spécial.

Ces outils compilent du code qui est ensuite transféré dans des équipements par liaison sérielle RS232.

Depuis au moins 2005 cette VM fonctionnait avec les versions gratuites du player et les ports séries n'ont

jamais fait de problèmes, qu'ils soient intégrés à la carte mère ou via USB (convertisseur type FTDI).

J'ai ensuite acheté WS pro 12 que j'ai utilisé sur un PC portable sous Windows 7 pro 64 et cette VM a

toujours aussi bien fonctionné sous cet OS.

J'ai rajouté un disque dur dans ce portable et j'ai fait un dual boot avec Linux FC25 pour migrer progressivement;

puis j'ai installé la version Linux de WS 12. Mes autres VMs fonctionnent normalement sous FC25 à l'exception de

celle avec msdos 6 et ce fichu port sériel.

Dès qu'un accès au port série est lancé par l'outil de développement, VMware crash complètement et se ferme

avec un message peu rassurant:

>VMware Player unrecoverable error: (vcpu-0)
>NOT_IMPLEMENTED bora/devices/serial/serialDevicePosix.c:1287
>A log file is available in "/home/me/VmwarePcs/MSDOS6/vmware.log". 
>You can request support.

Bien entendu la période de support incluse est passée sans que j'ai pu en profiter.

C'est pourtant bien un bug ou vice de programmation du logiciel dans sa version Linux, vu qu'avec exactement

le même matériel et une version de même niveau/plus ancienne sous windows, ça fonctionne.

Quelq'un a t-il déjà rencontré ce défaut du logiciel et réussi à la résoudre ?

J'ai installé la dernière màj 12.5.7 mais ça ne change rien au problème.

Le port série semble quand même fonctionner partiellement: Sur l'équipement connecté au port sériel il y a des

leds témoins d'activité, si j'envoie quelques caractères avec la ligne de commandes sous dos, on voit bien qu'il

y a du traffic..

L'outil de développement ne sait pas se connecter aux équipements par autre chose qu'un port série, il n'y a que

ce support de disponible.

L'idée de devoir me résigner à garder un dual boot et acheter du W10, juste pour pouvoir y lancer une (1) VM

avec dos dedans, me file déjà la nausée.

Hi,

Had to re-install everything from scratch as my Mac came back from a hardware repair. Fusion cannot see my Bootcamp Windows 10 N partition, erased and installed bootcamp three times and still no luck. Info on my setup:

Fusion Pro version: 8.5.6 (tried 8.5.5 and 8.5.3 with same results). 8.5.3 is what I had before my Macbook crashed and it worked with no issues with the same setup.

Macbook: Early 2015, 13" 2.7, 16GB RAM

Host OS: Sierra, fully updated

Bootcamp OS: Windows 10 Pro N, March 2017 version

Cleaned up all VMWare folders in / and ~ each time.

Any help is appreciated. Let me know if I can grab any logs.

how to install window 10 on fusion when you have already just install sierra?

any tips much appreciated.

I am a Mac mini user, System on top Os X 10.12 Sierra; Can I install Mac OS X 10.6.8 Snow Leopard via VMware?

I've been struggling to recover a missing local vfms 5 datastore, the LUN is visible but refreshing and or rescanning the Datastore just does not appear.

I am unable to mount in CLI either.

The HP SmartArray P400i controller shows the disks as ok although the boot information shows

1720 - S.M.A.R.T. Hard Drive(s) Detect Imminent Failure Port 2I: Box 1: Bay 4 - suggesting a SAS disk issue is imminent.

Is there anything I can do to recover a vm from this missing Datastore?

PartedUtil shows

# partedUtil getptbl /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0

gpt

71380 255 63 1146734896

1 2048 1146734591 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

/vmfs/volumes # esxcli storage core device list |grep -A27 ^mpx.vmhba1:C0:T0:L0

mpx.vmhba1:C0:T0:L0

   Display Name: Local VMware Disk (mpx.vmhba1:C0:T0:L0)

   Has Settable Display Name: false

   Size: 559929

   Device Type: Direct-Access

   Multipath Plugin: NMP

   Devfs Path: /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0

   Vendor: VMware

   Model: Block device

   Revision: 1.0

   SCSI Level: 2

   Is Pseudo: false

   Status: on

   Is RDM Capable: false

   Is Local: true

   Is Removable: false

   Is SSD: false

   Is Offline: false

   Is Perennially Reserved: false

   Queue Full Sample Size: 0

   Queue Full Threshold: 0

   Thin Provisioning Status: unknown

   Attached Filters:

   VAAI Status: unsupported

   Other UIDs: vml.0000000000766d686261313a303a30

   Is Local SAS Device: false

   Is Boot USB Device: false

   No of outstanding IOs with competing worlds: 32

offset="128 2048"; for dev in `esxcfg-scsidevs -l | grep "Console Device:" | awk {'print $3'}`; do disk=$dev; echo $disk; partedUtil getptbl $disk; { for i in `echo $offset`; do echo "Checking offset found at $i:"; hexdump -n4 -s $((0x100000+(512*$i))) $disk; hexdump -n4 -s $((0x1300000+(512*$i))) $disk; hexdump -C -n 128 -s $((0x130001d + (512*$i))) $disk; done; } | grep -B 1 -A 5 d00d; echo "---------------------"; done

Result -

---------------------

/vmfs/devices/disks/mpx.vmhba1:C0:T0:L0

gpt

71380 255 63 1146734896

1 2048 1146734591 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

Checking offset found at 2048:

0200000 d00d c001

0200004

1400000 f15e 2fab

1400004

0140001d  4c 43 4c 5f 52 41 49 44  30 00 00 00 00 00 00 00  |LCL_RAID0.......|

0140002d  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|

vmkernel.log output -

2017-06-07T17:40:21.582Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2017-06-07T17:40:21.582Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e8087c140) 0x28, CmdSN 0x2c5 from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

2017-06-07T17:40:24.695Z cpu2:32825)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

2017-06-07T17:40:24.695Z cpu2:32787)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x28 (0x412e80859ac0, 33801) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL

2017-06-07T17:40:24.695Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2017-06-07T17:40:24.695Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e80859ac0) 0x28, CmdSN 0x2c7 from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

2017-06-07T17:40:27.807Z cpu2:32783)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

2017-06-07T17:40:27.807Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2017-06-07T17:40:27.807Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e80859200) 0x28, CmdSN 0x2c9 from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

2017-06-07T17:40:30.920Z cpu2:32825)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

2017-06-07T17:40:30.920Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2017-06-07T17:40:30.920Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e80858a80) 0x28, CmdSN 0x2cb from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

2017-06-07T17:40:34.032Z cpu2:32779)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

2017-06-07T17:40:34.032Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2017-06-07T17:40:34.032Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e80858300) 0x28, CmdSN 0x2cd from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

2017-06-07T17:40:37.144Z cpu2:32793)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

2017-06-07T17:40:37.145Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2017-06-07T17:40:37.145Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e808569c0) 0x28, CmdSN 0x2db from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

2017-06-07T17:40:40.255Z cpu2:32843)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

2017-06-07T17:40:40.255Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2017-06-07T17:40:40.255Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e80856240) 0x28, CmdSN 0x2dd from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

2017-06-07T17:40:43.367Z cpu2:32779)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

2017-06-07T17:40:43.367Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2017-06-07T17:40:43.367Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e80855ac0) 0x28, CmdSN 0x2df from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

2017-06-07T17:40:46.479Z cpu2:32779)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

2017-06-07T17:40:46.480Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2017-06-07T17:40:46.480Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e80855340) 0x28, CmdSN 0x2e1 from world 33801 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

2017-06-07T17:40:46.480Z cpu3:33801)Fil3: 15338: Max timeout retries exceeded for caller Fil3_FileIO (status 'Timeout')

2017-06-07T17:40:48.804Z cpu1:33801)Config: 346: "SIOControlFlag2" = 0, Old Value: 0, (Status: 0x0)

2017-06-07T17:40:52.761Z cpu1:34271)WARNING: UserEpoll: 542: UNSUPPORTED events 0x40

2017-06-07T17:40:53.563Z cpu2:34271)WARNING: LinuxSocket: 1854: UNKNOWN/UNSUPPORTED socketcall op (whichCall=0x12, args@0xffd12d8c)

2017-06-07T17:40:54.445Z cpu3:33801)Config: 346: "VMOverheadGrowthLimit" = -1, Old Value: -1, (Status: 0x0)

2017-06-07T17:40:57.728Z cpu2:33989)Hardware: 3124: Assuming TPM is not present because trusted boot is not supported.

2017-06-07T17:41:00.176Z cpu2:34050)<4>cciss: cmd 0x4109904559c0 has CHECK CONDITION  byte 2 = 0x3

2017-06-07T17:41:00.177Z cpu2:32787)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x28 (0x412e8086a4c0, 33986) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x3 D:0x0 P:0x0 Possible sense data: 0x5 0x20 0x0. Act:EVAL

2017-06-07T17:41:00.177Z cpu2:32787)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2017-06-07T17:41:00.177Z cpu2:32787)ScsiDeviceIO: 2337: Cmd(0x412e8086a4c0) 0x28, CmdSN 0x38e from world 33986 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x5 0x20 0x0.

2017-06-07T17:41:00.247Z cpu2:34933)Boot Successful

2017-06-07T17:41:01.007Z cpu3:33804)Config: 346: "SIOControlFlag2" = 1, Old Value: 0, (Status: 0x0)

2017-06-07T17:41:01.736Z cpu1:34988)MemSched: vm 34988: 8263: extended swap to 8192 pgs

Hello,

I have Workstation 11 and it's been running Windows 10 x64 Pro up through version 1607 as a guest system flawlessly (Host is Win 8.1 x64 Pro MCE).

Unfortunately, when the "Creators Update" installs itself I'm seeing the screen go black in the guest OS around the time the installation finishes (first login?).

I've restored snapshots and re-run the installation a number of times, and the one thing that keeps the black screen failure from happening is to uninstall the VMware Tools SVGA driver before running the installation.

This might even be an acceptable workaround save for the fact that I can only set the screen size with the default Windows 10 driver to a maximum of 1162 x 864 pixels in size.  I'd really prefer the 1920 x 1200 I was using before with the VMware SVGA driver.

Can anyone suggest something I could try?

I realize I'm running an outdated version of VMware Workstation.  Even so, is it possible VMware could be convinced update VMware Tools for version 11 to avert this failure?  Assuming it's a basic incompatibility, I doubt I'm the only one who will be seeing this problem.

Thanks.

-Noel

When I performed an upgrade from 8.5.6 to 8.5.7, I was asked for my password. Upon providing this, the system began to exhibit odd crashes and errors several minutes later. I found that chmod was running and changed all of my entire file system permissions to root:wheel. I was able to reset these through much work, but it appears that VMWare Fusion is having some very serious problems with this upgrade.

Full disclosure, I updated my VMware to latest 12.5 and my USB stopped working. After a bit, I needed to manually uninstall VMware 12.5. I re-install and get two issues:  1. "Failed to install USB INF file" and 2. "Setup failed to install VMCI driver automatically. This driver will have to be installed Manually".  After continuing install the product installs and I can open my VM's. However , still cannot connect my USB devices (i.e. external hard drive and fingerprint readers).

Any suggestions on how I can fix these two issues or where I can get support (No longer have "free" support) ?

Thank You

Trying to get BATTLE FIELD 4 to run and getting 'Your compute does not meet the minimum requirements for playing this game.  VMWare SVGA 3D GPU does not support DIrectX 10.0 which is required.'

This is on a WinPro8.1 VM, Sierra Host iMac 11,2, Fusion Pro 8.5.8

Display Card: ATI Radeon HD 4670 256 MB

DXDiag Reports: DirectX 11 and under display, all three DirectX Features are enabled.

Any ideas what (if anything) I can do?

I'm trying to boot my physical Windows 10 drive on my Mac Pro from Fusion. The Windows install is an EFI install, and it has the entire disk to itself.

Fusion correctly set up the VM as an EFI VM. But when I boot it, it complains it can't find a startup disk, and then drops me to the EFI shell. Disk boots fine if I boot the machine to it. Just VMWare has trouble.

I tried running this:

GitHub - mikew/vmware-fusion-bootcamp: Of VMWare Fusion and Boot Camp partitions

And it comes back with:

"Could not find EFI partition"

Hi,

I have VMWare Workstation 12 version 12.5.7 build 5813279 installed on my computer running Windows 10 PRO x64. When I run VMWare Workstaion my other apps running start crashing and after some time the host generates a BSOD with message MEMORY_MANAGEMENT. I have already tried to disable USB arbitration and video acceleration as suggested on another threads here in the community. Appreciate any help on this.

Thanks!

Andre

An ESXi 5.5 host has a vib installed which i can see in the output of the esxcli software vib list command that I need to try installing on a 6.0 host.  I no longer have the original zip file that was used to install the vib.  What options are there for extracting it from the old host for installation on the new host?  Thanks

Could any one please help as one of esxi host(5.0) host  is showing hung on nfs client loaded successfully.

Could any one please help as one of esxi host(5.0) host  is showing hung on nfs client loaded successfully.