Search the VMware Knowledge Base (KB)
View by Article ID

USB redirection does not work after upgrade to View 5.2 and 5.3 (2051801)

  • 8 Ratings
Language Editions

Symptoms

  • When using linked-clone virtual machines, you experience USB redirection issues in the cloned images after upgrading the master image from VMware Horizon View Agent 5.1 to Horizon View Agent 5.2 and View Agent 5.3.
  • In the Horizon View Agent logs, you see errors similar to:

    T14:30:04.726-05:00 ERROR (0248-0828) <MessageFrameWorkShare> [ws_vhub] Failed to plugin device, Device: 00000000009697E0 status: Hub IO error
    T14:30:04.726-05:00 ERROR (0248-0828) <MessageFrameWorkShare> [ws_vhub] Plugged in device failed, Client PlugNo: 7


  • On the linked-clone image, you see that the version numbers of the vmwvhub.sys files differ. For example:

    C:\Windows\System32\drivers\vmwvhub.sys is version 5.1.0 build-668184
    C:\Program Files\VMware\VMware View\Agent\bin\drivers\vmwvhub.sys is version 5.5.0 build-949580


    Note
    : The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


  • This issue does not occur when upgrading from Horizon View 5.2.
  • This issue occurs with 64-bit Windows 7 systems using existing customizing specification when upgrading to Horizon View 5.2.
  • This issue may also occur with Full Clone Automated Virtual Machines with Sysprep

Cause

This issue can occur if the USB device driver (vmwvhub.sys) is downgraded during the creation of the linked-clone image.

Resolution

This is a known issue affecting VMware Horizon View 5.2 and 5.3. Currently, there is no resolution.

To work around this issue if you have linked-clone images that contain different versions of the vmwvhub.sys device driver file, modify the master image, so that copies of older vmwvhub.sys files (older than 5.5.0 build-949580) are removed:

  1. Remove the older vmwvhub.sys files from C:\Windows\System32\DriverStore\FileRepository and any other locations where they may be present. For more information, see the Microsoft Technet article Remove a Driver Package from the Driver Store.

  2. Recreate the linked-clone images from the updated master image and verify that both copies of the file are the same on the new images. For example, both of these files are Version 5.5.0 build-949580:

    C:\Windows\System32\drivers\vmwvhub.sys
    C:\Program Files\VMware\VMware View\Agent\bin\drivers\vmwvhub.sys

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

See Also

Update History

05/28/2013 - Added more information to the Symptoms section. 12/31/2013 - Added a symptom about Automated Full Clone VMs 1/20/2015 - Added View 5.3 in the product list, title and resolution

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 8 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 8 Ratings
Actions
KB: