OPERATIONAL DEFECT DATABASE
...
...
The USB device does not appear in the list of USB devices.The USB device connects to the virtual machine, then disconnects.The USB device stops working in a virtual machine.The USB device behaves erratically in a virtual machine.The USB device connects to the virtual machine, but is not detected by Windows or a third-party application.Your receive one of these error: Unable to connect the USB device "" to the virtual machine (error code 13) The device "device name" was unable to connect to its ideal host controller
This article provides the general steps to troubleshoot USB devices in Fusion virtual machines. The listed steps are appropriate for all cases, and the articles in the Additional Information section provide resolutions for specific cases.For general instructions for connecting a USB device to a Fusion virtual machine, see Working with printers, disks, and other devices in VMware Fusion (1014523).
Each step below provides instructions and a link to a document, for performing the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and to identify the proper resolution. They are also ordered in the most appropriate sequence to minimize data loss. After completing each step, try connecting/using the device again. Work through each troubleshooting step in order, and do not skip a step. Note: Fusion 4.1 resolves many USB connection issues. If you are running Fusion 4.0, upgrade to the latest version of Fusion. For more information on upgrading Fusion, see Uninstalling, reinstalling, and upgrading VMware Fusion (1014529). To troubleshoot issues with a USB device: If you have upgraded to OS X Lion (10.7), ensure that the permissions on your root directory are correct. For more information, see USB devices fail after upgrading to Mac OS X Lion (10.7) (2004687). If you are using Fusion 4, and see error code 4, repair the USB arbitrator service. For more information, see Attaching a USB device to a virtual machine in Fusion 4.x fails with an error code 4 (2007368). Ensure that your device is supported and connected properly. Follow the instructions in Apple Knowledge Base article HT1151. Note: The preceding link was correct as of November 19, 2014. If you find the link is broken, provide feedback and a VMware employee will update the link. If the device is plugged into a hub, unplug it from the hub and plug it directly into the Mac. Note: If the step does not resolve the issue, but a later step does, try using the hub again. Unplug all USB devices from your Mac, including any keyboards or mouse, and plug the device into the Mac again. Note: If the step does not resolve the issue, but a later step does, try plugging the other devices into the Mac again. The issue may persist if the problematic device is not the first USB device plugged in to the Mac. Turn off the device using the on/off switch. Shutdown your Mac. Turn on the device again, if possible. Turn your Mac back on. Note: Ensure to shut your Mac down and turn it on again even if your device does not have a power switch. Re-install VMware Tools in the virtual machine. For more information, see Overview of VMware Tools for VMware Fusion (1022048). Ensure that the necessary drivers are installed in Windows. For more information, see A connected USB storage device is not displayed in a Windows virtual machine (1004584). Remove and re-add the USB Controller from the virtual machine. For more information, see the Fusion Help topics Remove the USB Controller and Add the USB Controller. Determine whether the USB device needs extra configuration. For more information, see Troubleshooting USB devices using USB quirks in Fusion (1025256). If your device does not appear in Fusion's list, modify your .vmx settings to display all devices detected. For more information, see Connecting a second mouse or keyboard directly to a Fusion virtual machine (1003418).If your virtual machine detects your USB ports as low-speed ports, ensure that USB 2.0 support is enabled in the virtual machine settings. To enable USB 2.0 support, go to Virtual Machine > Settings, select USB & Bluetooth, expand Advanced USB options, and select USB 2.0 support under USB compatibility. Ensure your USB ports are in working order by running Apple Hardware Test. For more information, see: MacBook Airs – Apple Knowledge Base article HT2644All other Macs – Apple Knowledge Base article HT1509 Reset your Mac's PRAM. For more information, see Apple Knowledge Base article HT1379 Note: The preceding links were correct as of November 19, 2014. If you find a link is broken, provide feedback and a VMware employee will update the link. If you get an error code 13, follow these steps: Shutdown the Virtual MachineClick on Virtual Machine > Settings > USB & BluetoothAt the bottom of the pane click on Advanced USB optionsRemove and re-add the USB controllerStart the Virtual Machine. If the issue continues to exist even after trying these troubleshooting steps: Shutdown the virtual machine.Enable USB Verbose Logging. For Fusion 6.x and earlier: Open your .vmx file using a text editor. For more information, see Editing the .vmx file for your VMware Fusion virtual machine (1014782).Add this line to the file: usb.analyzer.enable = "TRUE" For 7.x and above: Click on Virtual Machine > Settings > AdvancedSelect Enable USB verbose debugging Enable debug logging for the virtual machine. In Fusion 4.x and earlier, select Preferences from the Fusion menu and then select the Enable debugging checks option. In Fusion 5.x and above, ensure that the virtual machine is shutdown, go to Settings > Advanced,and set Troubleshooting to Performance or Hang/Crash. Select the appropriate option from dropdown: Select Performance if you experience performance related issue with your virtual machine.Select Hang/Crash if you experience a hang or crash issue with your virtual machine. Power on your virtual machine.Connect the USB device to your virtual machine.Collect the VMware support information. For more information, see Collecting diagnostic information for VMware Fusion (1003894).File a support request with VMware Support and quote this Knowledge Base article ID (1027964) in the problem description. Attach the support information you collected to the Support Request. For more information, see Filing a Support Request in Customer Connect (2006985). After collecting the support information, go to VMware Fusion > Preferences and deselect Enable debugging checks (Fusion 4.x) or go to Settings > Advanced and set Troubleshooting to None.
USB 3.0 devices may not be recognized, or may malfunction, when connected to Windows 7 or earlier. Windows 7 does not include native support for USB 3.0 devices.Workaround: Ensure the Settings > USB And Bluetooth > USB Compatibility is set to USB 2.0, then connect the device to your Mac using a USB 2.0 hub or USB 2.0 cable to force USB 2.0 mode.If you encounter a specific issue or error with your USB device, see: Connecting USB audio devices in a virtual machine (1004973)USB audio device produces distortion in guest operating system (1014741)Connecting an external hard drive to a Fusion virtual machine (1021853) Connecting a second mouse or keyboard directly to a Fusion virtual machineCollecting diagnostic information for VMware FusionA connected USB storage device is not displayed in a Windows virtual machineConnecting USB audio devices in a virtual machineWorking with printers, disks, and other devices in VMware FusionUninstalling, reinstalling, and upgrading VMware FusionUSB audio device produces distortion in guest operating systemConnecting an external hard drive to a Fusion virtual machineOverview of VMware Tools for VMware FusionTroubleshooting USB devices using USB quirks in FusionConfiguring Windows Hosts for Use with USB Monitors (Sniffers)How to file a Support Request in Customer ConnectFusion 仮想マシンにおける USB デバイスの接続と機能のトラブルシューティング
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
