VMware ESXi and vSphere Cluster Management

Change a Virtual Machine Working Directory in VMware Player

Learn how to change VMware Player's working directory, which VM files move, which remain, and how to plan, verify, and troubleshoot the change.

VMware Player can use a separate host folder as a virtual machine's working directory. This folder stores selected runtime and state-related files without moving the virtual machine's configuration file, logs, or virtual disks.

This can help when the original storage volume is nearly full, when a faster drive is available, or when you want to separate temporary virtual machine I/O from permanent VM files.

What the VMware Player working directory means

The working directory is a folder on the host computer that VMware Player uses for applicable runtime, suspended-state, snapshot-state, memory, paging, and redo-related files. It is separate from the folder that contains the VM's main configuration and virtual disk files.

For example, a virtual machine might keep its permanent files on a large capacity drive while using a fast SSD for working-directory activity. This may improve responsiveness when the workload generates substantial temporary or memory-related I/O. The result depends on the speed of both devices and the VM's actual I/O pattern.

Important terms

Working directory: The host folder used for selected temporary and state-related VM files.
.vmx: The virtual machine configuration file. Changing the working directory does not move it.
Virtual disk: The file or files containing the guest operating system, applications, and data. These files are not automatically relocated.
Suspended state: A paused VM condition saved to disk so the VM can resume later.
Snapshot: A point-in-time VM state mechanism that can involve state, memory, and disk-change files.
Redo log: A file used to record virtual disk changes during applicable VM configurations or operations.

Which files are associated with the working directory?

The exact files created depend on the VM's current state and enabled features. A listed extension may not exist at all times.

Item	Typical extension or type	Affected by working-directory change	Notes
Suspended-state file	`.vmss`	Typically yes	Stores saved suspended VM state.
Snapshot-state file	`.vmsn`	Typically yes	Stores snapshot state or related metadata.
Memory or paging-related file	`.vmem`	Typically yes	Can be associated with VM memory or paging behavior.
Redo log	VM disk-change or redo-related file	Where applicable	Tracks virtual disk changes during applicable operations.
VM configuration file	`.vmx`	No	Remains in the original VM configuration folder.
VMware log files	Log files such as `.log`	No	Remain with the VM configuration location.
Virtual disk files	Virtual disk files such as `.vmdk`	No	Changing this setting does not move permanent guest storage.

What the setting does not move

Changing the working directory is not a complete virtual machine move. It does not relocate the .vmx configuration file, VMware log files, or virtual disk files. Those files remain in their existing locations unless you use a separate move, clone, export, or virtual-disk management procedure.

This distinction matters when planning storage. A VM may have its configuration, logs, and virtual disks in one folder while its suspended-state, snapshot-state, memory-related, and applicable redo files are created in another folder.

Plan the destination folder

Choose the destination before changing the setting. The folder must remain accessible at the same host path whenever VMware Player needs to run the VM or create state files.

Consideration	Why it matters	Recommended check
Available capacity	Suspension, snapshots, memory-related files, and temporary disk activity can consume substantial space.	Check free space and leave a safety margin based on VM memory, snapshots, and workload.
Storage performance	Faster storage can help with high-churn temporary or paging-related activity.	Prefer a fast, reliable local SSD when performance is the goal.
Host permissions	VMware Player must create, modify, and delete files there.	Confirm that the account running VMware Player has the required permissions.
Path stability	A changed folder path prevents later VM operations from finding the working files.	Use a stable local path that will not be routinely renamed or remounted.
Drive availability	A disconnected drive can prevent startup, suspension, or snapshot operations.	Avoid removable or intermittently connected storage unless its availability is controlled.
Backup and retention policy	State and snapshot files may affect recovery procedures and storage usage.	Confirm how the new location is backed up and how snapshots are managed.

Avoid permission-restricted, unreliable, or network-backed locations unless you understand their availability, locking, performance, and permission behavior. A local folder is usually the simplest choice.

Power off the VM before changing the setting

The guest must be completely shut down, and VMware Player must show the VM as powered off. Powered off is different from suspended: a suspended VM has saved execution state that VMware may still need to access.

Do not redirect the working directory while the VM is running or suspended. Active runtime files can be open or internally coordinated, and changing their location at that time can cause errors, incomplete state data, or loss of the expected resume or snapshot behavior.

Change the working directory in VMware Player

Shut down the guest operating system normally.
Confirm that the VM is fully powered off rather than suspended.
In the VMware Player library, select the target virtual machine.
Open the Player management menu.
Select Manage, then open Virtual Machine Settings.
Open the Options tab.
Select the General category.
Locate the Working directory field.
Use the browse control to select an existing host folder with sufficient free space and write access.
Confirm or save the setting.
If necessary, reopen the VM settings and return to Options > General to verify that the intended path is displayed.

The configuration path is:

Select VM in library > Player > Manage > Virtual Machine Settings > Options > General > Working directory

Enter or select a valid host folder path. The setting redirects applicable working files; it does not move the VM's permanent files.

Validate the change

Start the VM after saving the new setting.
Use a relevant feature, such as normal runtime activity, suspension, or snapshot creation, that causes working-directory files to be needed.
Verify that VMware Player completes the operation without a path, permission, or capacity error.
Inspect the selected folder, where appropriate, for files such as .vmss, .vmsn, .vmem, or applicable redo-related files.
Confirm that the original VM folder still contains the .vmx file and VMware log files.
Check free space and disk activity on both the working-directory volume and the volume containing the VM's virtual disks.

Do not expect every working-directory extension to appear during every test. File creation depends on whether the VM is suspended, whether snapshots are used, and which VMware features are active.

Performance and capacity considerations

Moving working-directory activity to another drive can reduce contention when the original drive is busy serving virtual disk I/O. A faster drive may also improve operations involving temporary, memory-related, or paging-related VM activity.

Benefits are not guaranteed. They depend on host hardware, storage latency, available bandwidth, the guest workload, and whether the original and destination drives are competing for the same physical resources. Separating folders on two partitions of one physical disk may provide little benefit.

Capacity is equally important. Suspension and snapshot operations can require large amounts of space, especially for VMs with substantial allocated memory or high disk-change activity. If the destination volume fills, VMware operations such as suspension, snapshot creation, or runtime activity may fail.

Example: A VM can keep its .vmx file and virtual disks on a large-capacity hard drive while using a fast SSD as its working directory. This arrangement is intended to improve responsiveness for working-directory activity without performing a full VM relocation. The SSD must still have enough free space for suspension, snapshots, memory-related files, and temporary activity.

Operational cautions

Keep the destination path available whenever the VM is used.
If a drive letter, mount point, or folder name changes, restore the original path or update the Working directory setting while the VM is powered off.
Do not manually delete active .vmss, .vmsn, .vmem, or redo-related files. Use VMware Player's normal shutdown, suspend, snapshot, and management operations.
Changing the working directory is not a replacement for moving, cloning, exporting, or relocating a complete VM.
Consider whether the new location is included in backups and whether snapshot retention procedures account for files stored there.

Troubleshooting

The Working directory field cannot be edited or saved

Ensure the VM is fully powered off, not running or suspended.
Choose an existing, valid host folder.
Verify that the VMware Player account can create, modify, and delete files in that folder.
Save the setting again and reopen the settings dialog to verify the path.

The VM reports insufficient disk space

Check free space on the configured working-directory volume.
Remember that VM memory size, snapshot activity, and workload can increase requirements.
Free space or select a larger working directory while the VM is powered off.
Review and remove unneeded snapshots through appropriate VM management procedures.

The working directory is unavailable after a drive change

Check whether a drive letter, mount point, or folder path changed.
Reconnect an external drive or restore the expected path if possible.
With the VM powered off, update the Working directory setting to a stable, available location.
Confirm read/write access before starting the VM.

The virtual disk or configuration file did not move

This is expected. The working-directory setting affects selected runtime and state-related files only. Use the appropriate VM move, clone, export, or virtual-disk workflow when permanent VM files must be relocated.

Summary

To change a VMware Player working directory, power off the VM, open its settings from the Player library, go to Options > General, select a suitable folder in the Working directory field, and save the setting. The change redirects applicable .vmss, .vmsn, .vmem, and redo-related activity, while the .vmx file, logs, and virtual disks remain in their original locations.

For the full procedure, see Change the working directory of a virtual machine.