Troubleshooting Write Permission Issues for USB 3.2 Devices on VMware Fusion

2 device attached through VMware Fusion is readable but not writable. Check host permissions, VM USB ownership, filesystem state, and guest mount behavior.

Quick Read

Symptom: 2 device attached through VMware Fusion is readable but not writable. Check host permissions, VM USB ownership, filesystem state, and guest mount behavior.
Check first: Confirm whether macOS, VMware Fusion, or the guest OS currently owns the USB device before changing permissions.
Risk: Review before running

Symptoms

Users are unable to write to USB 3.2 devices connected to virtual machines in VMware Fusion.

Environment

VMware Fusion running on macOS with USB 3.2 devices connected.

Most Likely Causes

The issue may arise due to incorrect USB device settings in VMware Fusion, insufficient permissions on the host macOS, or conflicts with other software managing USB devices.

What to Check First

Confirm whether macOS, VMware Fusion, or the guest OS currently owns the USB device before changing permissions.
Record the device filesystem, current mount mode, and whether the device is writable directly from macOS outside the VM.
Check whether the guest OS can write to another USB device, which separates VMware USB pass-through problems from device-specific filesystem or media issues.

Fix Steps

Verify USB Device Connection
Ensure that the USB 3.2 device is properly connected to the host machine and recognized by macOS.
Example pattern only. Adjust for your environment before running.
```
Open 'System Information' on macOS.
Navigate to 'USB' under the 'Hardware' section.
Check if the USB 3.2 device appears in the list.
```
Check VMware Fusion USB Settings
Confirm that the USB device is connected to the correct virtual machine and that the settings allow write access.
Example pattern only. Adjust for your environment before running.
```
Open VMware Fusion.
Select the virtual machine in question.
Go to 'Virtual Machine' > 'USB & Bluetooth' > 'USB Device' and ensure the USB 3.2 device is selected.
```
Adjust macOS Security & Privacy Settings
Modify the security settings to ensure VMware Fusion has the necessary permissions to access USB devices.
Example pattern only. Adjust for your environment before running.
```
Open 'System Preferences' on macOS.
Select 'Security & Privacy'.
Go to the 'Privacy' tab and select 'Full Disk Access'.
Click the lock icon to make changes and add 'VMware Fusion' to the list.
```
Check Virtual Machine Configuration
Ensure that the virtual machine is configured to allow USB device access.
Example pattern only. Adjust for your environment before running.
```
With the virtual machine powered off, go to 'Virtual Machine' > 'Settings'.
Select 'USB & Bluetooth' and ensure 'Enable USB 3.0' is checked.
```
Test with Different USB Ports
Try connecting the USB 3.2 device to different USB ports on the host machine to rule out port-specific issues.
Example pattern only. Adjust for your environment before running.
```
Disconnect the USB device.
Reconnect it to a different USB port on the host machine.
Reopen VMware Fusion and check the USB device connection.
```
Update VMware Fusion
Ensure that you are using the latest version of VMware Fusion, as updates may contain fixes for USB issues.
Example pattern only. Adjust for your environment before running.
```
Open VMware Fusion.
Go to 'VMware Fusion' > 'Check for Updates'.
Follow the prompts to install any available updates.
```

Validation

The USB device is attached to the intended VM and no longer mounted by macOS at the same time.
The guest OS can create, modify, and delete a small test file on the USB device without remounting read-only.
After disconnecting and reconnecting the device, the same VM still receives write access.

Logs to Check

macOS System Information and Console entries for USB attach, detach, and permission prompts.
VMware Fusion device connection prompts and VM USB/Bluetooth settings.
Guest OS disk, mount, or filesystem logs if the device appears but stays read-only inside the VM.

Rollback and Escalation

Remove temporary VMware Fusion privacy permissions if they do not change USB behavior.
Reconnect the USB device to macOS instead of the guest if the VM cannot safely write to it.
Back up device contents before changing filesystem format, ownership, or repair settings.

Escalate When

Escalate if the device is writable on macOS but every guest OS mounts it read-only through VMware Fusion.
Escalate before reformatting or repairing a USB device that contains the only copy of important data.

Edge Cases

If the USB device is still not writable, check if the device is formatted in a compatible file system (e.g., exFAT or FAT32).
If using third-party USB management software, disable it temporarily to see if it resolves the issue.

Notes from the Field

USB write problems often come from ownership handoff. Make sure the device is connected to either macOS or the VM, not bouncing between both.
Filesystem compatibility matters: a device that mounts read-only in one guest may be fine in another guest with different filesystem support.