VMware ESXi and vSphere Cluster Management

What Are Shared Folders in VMware Workstation Player?

Learn how VMware Workstation Player shared folders connect host directories to guest VMs, including prerequisites, setup, access paths, security, compatibility, and troubleshooting.

A VMware Workstation Player shared folder is a directory selected on the host computer and exposed inside a guest virtual machine (VM). It lets the host and guest access the same files through VMware integration instead of configuring conventional network file sharing inside the guest.

The host system is the physical computer and operating system running VMware Workstation Player. The guest operating system is the operating system installed inside the VM. VMware Workstation Player connects these environments, while VMware Tools supplies guest integration components such as shared-folder support.

What a Shared Folder Does

When you configure a shared folder, you choose a host path and assign it a share name. The guest then accesses that directory through VMware's shared-folder integration. Files remain in the selected host directory; they are not automatically copied into the guest's virtual disk.

This differs from copying a complete directory into a virtual disk. A copied directory becomes an independent guest-side copy and can consume additional virtual disk space. A shared folder provides ongoing access to the host-side directory, so changes made through one environment can be visible from the other, subject to permissions and filesystem behavior.

How Shared Folders Work

1. The host operating system stores a local directory or reaches a directory on a network.
2. VMware Workstation Player is configured to expose that location to a selected VM.
3. VMware Tools provides the guest-side integration needed to make the share available.
4. The guest operating system presents the share through its own filesystem or file-browsing conventions.

A single host directory can be made available to one or more VMs when each VM is configured to use it. Each VM still depends on its own VMware Tools installation, guest permissions, and shared-folder settings.

Supported Share Locations

The source can be a local host path, such as a project directory or installer repository. A network directory reachable by the host may also be selected, provided the host can open it and has the required permissions.

For a network directory, VMware Workstation Player does not give the guest independent credentials or a separate direct connection to the remote server. The host's access is used through the configured host-side share. If the host loses network connectivity or authentication, the guest's shared-folder access can also stop working.

Requirements and Responsibilities

Benefits and Common Uses

• Reduce duplicate downloads: Download a large installer once on the host instead of downloading it separately in every VM.
• Share an installer repository: Expose one host-side repository to several test VMs. Each guest can run an installer from the share or copy it locally when local installation media is preferred.
• Exchange development files: Edit source code on the host and test it in a guest without repeatedly transferring project archives.
• Exchange operational data: Move logs, exports, scripts, reports, and test data between the host and guest.
• Support lab environments: Supply common tools and datasets to isolated development, testing, or training VMs.

Example: One Installer for Multiple Test VMs

1. Download the large installer to a dedicated software repository on the host.
2. Configure that repository as a shared folder for each test VM.
3. Run the installer from the shared location, or copy it into a guest when the installer needs local media.
4. Repeat the installation without downloading the same file through every guest.

This saves time, disk space, and network bandwidth. It does not eliminate the need to verify that the installer is appropriate for each guest.

Example: Host-Edited Source Code in a Linux Guest

1. Create a dedicated project directory on the host.
2. Expose it to the Linux VM with a recognizable share name.
3. Open the guest-visible shared-folder path and inspect the project.
4. Change a small file on the host and confirm the change from the guest, then test the reverse direction if write access is intended.

Build tools may depend on Linux-native ownership, permissions, file locking, symbolic links, or timestamp behavior. Test the workflow first; use a directory on the guest's native virtual disk when the tool does not behave correctly on a shared folder.

Example: Collecting Logs from a Windows Guest

1. Create a host directory specifically for VM log collection.
2. Share it with the Windows VM.
3. Copy a non-sensitive test log to the guest-visible location.
4. Confirm that the file appears in the host directory.

Use a restricted or read-only configuration when the guest only needs to consume files. If the guest must write logs, limit the share to the dedicated collection directory.

Example: A Host-Reachable Network Repository

1. Confirm that the host can open the network directory using valid host-side credentials.
2. Select that location as the source for a VM shared folder.
3. Test access with a non-sensitive file.
4. Account for host network availability and changing credentials.

Prerequisites

• VMware Tools: Install or update VMware Tools in the guest and confirm that its integration is functioning.
• VM configuration: Configure the VM to use shared folders. Some configuration workflows require the VM to be shut down before settings can be changed.
• Host permissions: The host user must be able to access the selected local or network directory.
• Guest permissions: The guest user must have permission to open the guest-visible location and perform the requested operation.
• Supported combination: Feature availability can vary with the guest OS, VMware Workstation Player edition, VMware release, and VMware Tools version.

High-Level Configuration Workflow

1. Install or update VMware Tools in the guest operating system.
2. Shut down the VM if the applicable settings workflow requires a powered-off VM.
3. Open the target VM's settings in VMware Workstation Player.
4. Locate the shared-folder configuration and enable shared folders for the VM.
5. Add one or more host directories. For each entry, choose a recognizable share name.
6. Select read-only access when the guest does not need to modify host files.
7. Choose persistent availability or session-only availability when those options are offered. A persistent share is retained for the VM instead of existing only during a temporary session.
8. Start the guest and open its operating-system-specific shared-folder location.
9. Verify the setup with a small test file. Test reading, writing, and deleting only when those actions are intended.

Accessing a Share Inside the Guest

Windows Guests

Use File Explorer to browse the VMware shared-folder network location or its mapped representation. The configured share name should appear there. The exact display and drive-letter mapping depend on the VMware Tools version and guest configuration.

If write access is intended, create or copy a small test file and confirm that it appears in the host directory. If the share is read-only, a failed write is expected.

Linux Guests

Linux guests commonly expose VMware shared folders through a VMware shared-folder mount location, often under a path such as /mnt/hgfs. The exact path can vary by distribution, VMware Tools implementation, and configuration.

ls /mnt/hgfs
ls /mnt/hgfs/<share-name>

If the expected location is absent, inspect the guest's file manager and verify that VMware Tools is installed and running. Use a simple directory listing and a small test file operation appropriate to the guest user's permissions.

Solaris Guests

Solaris access conventions can differ from Windows and Linux. Verify the guest-visible location and required commands against the guest integration documentation for the installed VMware Tools version.

Version-Specific Guest Compatibility

The following is a historically listed compatibility summary, not a guarantee for every current release. VMware Tools availability and guest support can change between VMware product versions. Consult the documentation for the VMware Workstation Player release installed in your environment.

Shared Folders Versus Copy and Paste

Clipboard sharing is a separate host-guest integration feature. It transfers selected copied content through the clipboard; it does not expose a reusable directory.

Enabling clipboard sharing does not enable shared folders, and enabling shared folders does not automatically enable clipboard sharing. Treat them as separate features with separate security decisions.

Security and Operational Considerations

• Give the guest access only to directories it needs. Avoid sharing a broad home directory or an entire host volume.
• Use a read-only share when the guest only needs to view or copy files.
• Do not place passwords, private keys, credentials, or other sensitive material in broadly shared directories.
• Assume that malware or misconfigured software in a guest can affect files reachable through a writable share.
• Use a dedicated exchange directory for installers, logs, or test data rather than exposing unrelated personal or administrative files.
• Review whether files copied from an untrusted guest should be scanned or inspected before being used on the host.

Limitations and Expectations

• Shared folders depend on VMware Tools and are not a replacement for a fully configured network file service.
• Feature availability and behavior can differ by guest OS, VMware Workstation Player edition, product release, and VMware Tools implementation.
• A host network directory shared with a guest does not automatically provide the guest with independent network access to that remote location.
• Filesystem semantics may not match the guest's native filesystem, especially for ownership, permissions, timestamps, locking, and symbolic links.
• Applications that require strict native filesystem behavior may work better with files stored on the guest's virtual disk.

Troubleshooting Shared Folders

The Shared-Folder Option Is Unavailable or Disabled

Possible causes include an unsupported guest or VMware Workstation Player version, a VM power state that prevents configuration changes, or missing or unrecognized VMware Tools.

• Verify the VMware product and guest compatibility.
• Confirm the VM power state required for changing settings.
• Install, repair, or update VMware Tools.

The Guest Cannot See the Configured Folder

VMware Tools may be missing, stopped, or outdated. The share may not be enabled for this VM, may be session-only, or the guest may be looking in the wrong operating-system-specific location.

• Confirm the share entry and enablement in VM settings.
• Restart the guest after configuration changes if needed.
• Check the Windows VMware shared-folder location or the Linux mount location.
• Check the VMware Tools service or process status.

The Guest Can Read but Not Write

The share may be read-only, the host user may lack write permission, or guest-side permissions may restrict the current user.

• Review the share's read-only setting.
• Test host-side write access to the source directory.
• Inspect guest permissions and relevant group membership.

A Shared Network Directory Stops Working

The host may have lost connectivity, host credentials may have expired or changed, or the remote server may be unavailable.

• Open the source directory directly from the host.
• Restore host network connectivity and authentication.
• Verify that the remote file service is online.

Linux Files Have Unexpected Permissions or Timestamps

A shared-folder implementation may not behave exactly like a native Linux filesystem, and host filesystem semantics may differ from guest expectations.

• Test a simple file before using the share for a build workload.
• Use a native guest-disk location when tools require Linux-native ownership, permissions, locking, or symbolic-link behavior.
• Review the mount behavior and guest integration documentation for the installed VMware Tools version.

Summary

VMware Workstation Player shared folders expose selected host directories inside guest VMs through VMware Tools. They are useful for installers, source code, logs, scripts, and test data because they avoid repeated downloads and manual transfers. Configure only the directories needed, prefer read-only access where possible, verify host and guest permissions, and remember that support and guest-visible paths vary by VMware release and operating system.

For a related overview, see What Are Shared Folders.