VMware Player 17.5.1 on Linux often fails to load ISO files stored on external USB drives due to strict permissions, incorrect mount options, or virtual machine configuration errors. The most common cause is that the user account lacks read access to the filesystem hosting the ISO, or the VM settings point to a path that VMware cannot resolve across USB device boundaries. This guide provides a step-by-step solution to ensure your external drive is correctly mounted and accessible by the virtualization software.
Verify External Drive Mount Permissions
The primary reason VMware cannot see an ISO on a USB stick is permission denial. Modern Linux distributions often mount removable media with restrictive default permissions, such as nosuid or specific ownership models that exclude standard users from reading arbitrary files. Before touching VMware settings, you must confirm that your user account can actually read the file in question.
Open a terminal and navigate to the directory where your ISO is stored. Use the ls -l command to check the permissions. If the output shows that only root has read access, or if the group does not include your user, VMware will fail silently when trying to attach the disk image. You should ensure the file permissions allow at least read access for others or your specific user group. For example, you might need to adjust permissions using chmod or change the group ownership using chgrp. However, changing permissions on every bootable ISO is impractical; instead, focus on how the drive itself is mounted.
If the drive is auto-mounted by your desktop environment, it might be using a temporary mount point that changes or restricts access. A more robust approach is to manually mount the drive with explicit read permissions. Identify the device name using lsblk, then create a permanent mount point in /mnt or /media. When mounting, use the ro (read-only) flag to prevent accidental writes and ensure the uid and gid options match your current user ID. This guarantees that VMware, running under your user context, can traverse the directory and open the ISO file without encountering "Permission Denied" errors.
Check VMware Virtual Machine Configuration
Once file system permissions are verified, the next step is to ensure the virtual machine is configured to look at the correct location. VMware Player sometimes caches paths or struggles with symbolic links and complex nested directories common in external drive structures. Open your virtual machine settings and navigate to the CD/DVD drive section. Ensure that the option is set to "Use ISO image file" rather than "Use physical drive."
Click the browse button and manually locate the ISO file from the external drive. Avoid using shortcuts or recent history entries if they exist, as these may point to stale symlinks. It is crucial to use the absolute path to the file. For instance, if your drive is mounted at /media/usb_drive/installers/ubuntu.iso, enter this exact string. If VMware complains about the path, verify that the external drive is still connected and mounted at that exact location before powering on the VM.
Additionally, check the advanced settings of the CD/DVD controller. Ensure that the controller type is compatible with your guest operating system. While IDE controllers are universally compatible, SATA or NVMe controllers might offer better performance but require specific drivers in the guest OS. For general purpose ISO loading, especially for installation media, sticking to the default IDE or SATA controller provided by VMware is the safest bet to avoid compatibility issues during the boot process.
Validate ISO Integrity and Filesystem Compatibility
Sometimes the issue is not with VMware or permissions, but with the external drive's filesystem format. If your USB drive is formatted as NTFS or exFAT, some Linux kernels may mount these with limited functionality or require additional packages like ntfs-3g or exfat-utils to provide full read access. Verify that your system has the necessary drivers installed for the filesystem used by the USB stick.
Furthermore, ensure the ISO file itself is not corrupted. External drives are prone to disconnection errors during write operations, which can truncate or corrupt large files like ISO images. Run a checksum verification against the original source if possible. In VMware, you can also try attaching the ISO to a different virtual machine to isolate whether the problem is specific to one VM configuration or a broader system issue related to the USB storage.
If you frequently work with external bootable drives, consider creating a local copy of the ISO on your internal SSD for testing purposes. This eliminates USB latency and permission complexities entirely. However, for direct loading, ensuring the mount point is stable and readable is key. You can add a persistent entry to your /etc/fstab to ensure the drive mounts consistently with the correct permissions after every reboot, preventing transient permission issues. See our guide on Mounting External Drives with mount command in fstab not working: A Troubleshooting Guide for detailed instructions on setting up persistent mounts.
Frequently Asked Questions
Why does VMware say the ISO file is locked?
This usually happens if another process, such as a file manager preview or an antivirus scan, has the file open. Close all applications accessing the file and try again. If the issue persists, restart the VMware service or reboot your system to release any lingering file locks.
Can I use a network path instead of a USB drive?
Yes, VMware supports network shares, but they can be slower and more prone to timeout errors during boot. Ensure the network share is mounted locally via NFS or CIFS with appropriate read permissions before pointing VMware to it. This method is less reliable than local storage for heavy I/O operations like OS installation.
What if my USB drive disappears from the list?
This indicates a hardware or driver issue rather than a VMware problem. Check your system logs with dmesg to see if the kernel detected the device. Try a different USB port, preferably one directly on the motherboard rather than through a hub, to rule out power delivery issues.
Does VMware Player support UEFI boot from USB ISOs?
Yes, but you must enable UEFI firmware in the VM settings first. Go to VM Settings > Options > Advanced and select UEFI as the firmware type. Then, attach the ISO to the CD/DVD drive. Note that some older ISOs may not boot correctly in UEFI mode and might require Legacy BIOS mode.
How do I fix "Device Not Ready" errors in VMware?
This error often occurs if the ISO file is missing or the path has changed. Re-verify the path in the VM settings. If the drive is external, ensure it is plugged in before starting the VM. Sometimes toggling the "Connected" checkbox in the VM settings helps reset the virtual device state.