Windows In VMware Fusion ‘Cannot Access Shared Folders’

KB ID 0001627

Problem

Every so often I have a problem with the Windows 10 VM that I run on my mac in VMware Fusion, last time I needed to upgrade to Fusion 11.5, before that it was a registry fix. This time I could not access any files or folders on the parent mac.

Network Error
Windows cannot access \\vmware-host\Shared Folders\{Folder-Name}
You do not have permissions to access \\vmware-host\Shared Folders\{Folder-Name}. Contact your network administrator to request access.

Solution

Removing and re-adding the share in VMware Fusion didn’t fix the problem, in the end I had to grant VMware Fusion, ‘Full Disk’ access before the problem ceased.

System Preferences > Security & Privacy > Privacy > ‘Unlock’ > Full Disk Access > Tick ‘VMware Fusion.app”.

Related Articles, References, Credits, or External Links

NA

VMware – Ubuntu Screen Resolution Problem

KB ID 0000411 

Problem

I have a guest VM on my vSphere test rig that’s running Ubuntu 10.10. That I use for testing, for a while I could not get the screen resolution above 854×480 (For wide screen or 16:9 format).

 

Solution

Note I’m assuming you already have the VMware tools installed!

1. Shut down your guest machine, open the VMware VI client and go to the settings of the guest machine. go the the hardware tab and select video card. By default it will be set to auto detect, change it to a nice high resolution, and click OK.

Note: For VMware workstation the setting is under “Display” see below.

2. Power the guest VM back on again and now you should have a better range of resolutions.

 

Related Articles, References, Credits, or External Links

NA

Possible bug in VMware Client

KB ID 0000413

Problem

Unable to use multiple console sessions in Windows 7.

1. Seen on Windows 7 x64 Ultimate, with and without aero enabled, on two separate machines.

2. Happens if connected to VCenter OR directly to ESXi (build 4.1.0, 260247)

3. Does NOT happen with the same software from Server 2003. (Same systems, same vesion of the VI client).

4. Does NOT happen on Server 2008 R2 Standard x64 (Same systems, same version of the VI client).

5. Does NOT happen on Server 2008 R2 Standard x64 with Service Pack 1 (Same systems, same version of the VI client).

6. Does NOT happen on Server 2008 R2 Standard x64 aero Enabled with Service Pack 1 (Same systems, same version of the VI client).

7. Does NOT happen on Windows 7 Enterprise (Service Pack 1) x86 (Same systems, same version of the VI client).

Description

 

Related Articles, References, Credits, or External Links

NA

vSphere – Guest VM is shown as (Orphaned)

KB ID 0000414 

Problem

I’ve seen this happen a few times now, while looking at your Virtual infrastructure, one or more client machines is greyed out and shown as (Orphaned).

Solution

If you have many guests VM’s on one host with this problem, you can cure this by removing the parent host and re-adding it to the cluster, then right clicking it and select “Reconfigure for HA“.

Or you can do the following, on a machine by machine basis.

1. Right click the affected VM and select “Remove from Inventory” (nothing gets deleted don’t worry.)

2. Select one of your ESX hosts > Configuration > storage > Right click the storage that holds the virtual machine we are dealing with and select “Browse Datastore” > Locate the machines .vmx file > Right click > Add to inventory > Follow the instructions.

Related Articles, References, Credits, or External Links

For VMware View machines click here