Change a Virtual Machine Working Directory in VMware Player

Learn how to change a VMware Player virtual machine's working directory while keeping its configuration, logs, and virtual disk files in their original locations.

What the VMware Player Working Directory Is

A VMware Player working directory is the folder used for selected temporary and active virtual-machine state files. These files can be created while the VM is running, suspended, using snapshots, or recording virtual disk changes.

By default, the working directory is normally the same folder that contains the virtual machine's main files. The setting is per virtual machine, so changing it for one VM does not automatically change it for other VMs.

The working directory is not the same as the VM's primary folder. The primary folder commonly contains the .vmx configuration file and virtual disk files. Changing the working directory changes where working-state files are created; it does not relocate the entire virtual machine.

Files Stored in the Working Directory

The exact files created depend on the VM's current activity and configuration. Common working-directory contents include the following:

File type	Extension or name pattern	Purpose	Storage consideration
Suspended-state file	`.vmss`	Stores the saved execution state needed to resume a suspended VM.	Can require substantial space, particularly for a VM with a large memory allocation.
Snapshot-state file	`.vmsn`	Stores state information associated with a snapshot.	Snapshot activity can increase storage use in the working directory.
Memory or paging file	`.vmem`	Stores virtual machine memory or paging data used by VMware.	Allow adequate free space for memory-related activity.
Redo log file	VMware redo-log files	Records virtual disk changes in configurations that use redo logging.	Heavy guest disk activity can make these files grow.

A suspended state is a saved VM execution state that allows the guest to resume later. A snapshot is a saved point-in-time state of a VM and, depending on the configuration, its disks. A redo log records virtual disk changes rather than replacing the original disk data immediately.

Why Change the Working Directory?

Use faster storage: Put active paging, suspended-state, snapshot, and redo-log activity on a faster local SSD while leaving the main VM files on another disk.
Increase available capacity: Use a volume with more free space so temporary state files do not fill the volume containing the VM's primary files.
Separate storage roles: Keep the VM configuration and virtual disk files on one disk while placing working files on another disk.
Manage storage growth: Snapshot and memory-related files can consume considerable space during particular operations.

Moving working files to faster storage may improve responsiveness when the workload is limited by host disk I/O. It is not a guaranteed improvement: guest workload, host memory, storage latency, available capacity, and other host activity also affect performance.

Example: Faster Runtime Storage

You can keep a VM's virtual disk and .vmx file on a large-capacity drive while setting its working directory to a fast local SSD. The SSD must still have enough free space for paging and state files.

Example: Protecting the Main Storage Volume

If the volume containing the VM's primary files is nearly full, select a separate high-capacity local volume for the working directory. Snapshot and suspended-state files can then use the second volume without moving the VM's main layout.

Before Changing the Location

Power off the VM completely. Shut down the guest operating system and confirm that VMware Player shows the VM as powered off. Do not change this setting while the VM is running or suspended.
Check the destination drive. Make sure it is connected, available, writable, and has adequate free space.
Choose a stable local path. The folder must remain accessible whenever the VM runs. Avoid removable or intermittently connected storage unless it is reliably available for every VM session.
Use a distinct folder. Create a clearly named folder for this VM instead of using an ambiguous shared temporary folder. A separate folder makes capacity checks and cleanup safer.
Understand what is being changed. This procedure changes the location for working-state files only. It does not move the VM's primary folder, virtual disks, configuration file, or log files.

Change the Working Directory in VMware Player

Use this VMware Player navigation path:

Select the virtual machine > Player > Manage > Virtual Machine Settings > Options > General > Working directory

Select the target virtual machine in the VMware Player library.
Open the Player menu.
Select Manage, then select Virtual Machine Settings.
Open the Options tab.
Select General.
Locate the Working directory field.
Use the browse control to select the intended destination folder.
Confirm the path and select OK to save the setting.

What Does Not Move

Changing the working directory is not the same as moving a virtual machine. The following items remain in their existing locations:

Item	Moved by changing the working directory?	Notes
Working-state files	Yes, newly created files use the selected working directory.	These include applicable `.vmss`, `.vmsn`, `.vmem`, and redo-log files.
`.vmx` configuration file	No	The VMware virtual machine configuration file remains in its existing location.
VMware log files	No	Log files remain in their existing location.
Virtual disk files	No	The files containing the guest operating system, applications, and guest data remain where they are.

Use a separate VM relocation procedure when the goal is to move the entire VM or its primary folder. Moving virtual disks is also a separate operation that requires its own planning.

For background on the files that make up a VM, see Virtual Machine Files. For a complete relocation, see Move a Virtual Machine.

Verify the New Working Directory

Start the virtual machine after selecting OK.
Verify that the guest operating system starts and operates normally.
When applicable, suspend the VM or create a snapshot to test whether working-state files can be created in the selected location.
Check the destination drive's free space after the test.
Do not remove or disconnect the target storage while the VM may need its working files.

Keep adequate capacity in the working directory. Memory-related files can be large, and snapshot or redo-log activity can grow during intensive guest use.

Troubleshooting

The Working Directory Setting Is Unavailable

Likely cause: The VM is still running or suspended.

Resolution: Shut down the guest and fully power off the VM. Reopen Virtual Machine Settings, then return to Options > General.

The VM Cannot Start or Create State Files

Likely cause: The selected folder is unavailable, the account lacks write permission, or the drive has been disconnected.

Resolution: Restore access to the selected location, verify that the folder is writable, reconnect the storage if appropriate, or select an available local folder.

The Destination Drive Runs Out of Space

Likely cause: The working directory does not have enough capacity for memory, snapshot, paging, or redo-log files.

Resolution: Free space, select a larger volume, or reduce activity that creates additional working-state data. Do not assume that the VM's virtual disk size is the only storage requirement.

The Main VM Files Are Not in the New Directory

Likely cause: The working-directory setting was confused with moving the virtual machine.

Resolution: This setting affects working-state files. The .vmx file, VMware logs, and virtual disks remain in their original locations unless they are moved separately.

Key Points

The working directory is a per-VM location for temporary and active state files.
Common contents include .vmss, .vmsn, .vmem, and redo-log files.
Power off the VM fully before changing the setting.
Choose a stable, writable local folder with enough free space.
The setting does not move the .vmx file, VMware logs, virtual disks, or the entire VM.
Verify normal startup and working-state creation after saving the new path.