VMware Fusion 8.5.X – Windows 10 – Shared Folders AWOL

2017/02/22

Updated: 20170228

The problem occurred again. This time, an uninstall and reinstall of VMware Tools didn’t fix the issue.

The fix was to:

  • Open the VMware Fusion Sharing preferences and leave “Enable Shared Folders” ticked but untick all the “Mirrored Folders”.
  • When prompted, log off and log back on.
  • Open the VMware Fusion Sharing preferences and select the folders you want under ‘Mirrored Folders’.
  • You will again be prompted to log off. Log off and then log back on.

The mirrored folders should be accessible again.

Originally:

VMware Fusion has a nifty feature called ‘Shared Folders’ thats lets you access data on the underlying Mac OSX host from within the guest OS. Fusion must be configured to enable it and VMware Tools must be running inside the guest for it to work.

Recently, mine stopped working. I hadnt disabled the feature in Fusion and nothing lept to mind about other changes I could have made that caused the problem.

Today I had some spare cycles to dig into the cause of the problem and find the fix. See the source below from Nov 2015.

TL;DR: Windows Update nerfs a registry value which VMware Tools uses. The fix was simple, uninstall VMware Tools, reboot, install VMware Tools, reboot.

 

Source: Shared Folders – Windows 10 upgrade from 15.11. | VMware Communities

Advertisements

Windows Update Standalone Installer Error

2016/11/30

I had to install PowerShell 3.0 on my Windows 7 SP1 VMware Fusion 8.5 VM earlier today and grabbed the installer from https://www.microsoft.com/en-us/download/details.aspx?id=34595. The download was done from Chrome on my Mac and saved to my Mac’s Downloads folder.

I have Shared Folders running in Fusion so I have direct access to the Downloads folder from Windows via the Z:\ drive presented to Windows.

When I ran the .msu file from z:\downloads I would receive an error which said:

Installer encountered an error: 0x80070003
The system cannot find the path specified.

screen-shot-2016-11-30-at-2-08-51-pm

The fix is to copy the .msu file to a VMDK based disk in the VM and run it again.