zenficus's Posts

Try explicitly setting this thing in configuration, not removing it. Also, this was relevent for Workstation 16, not 17. If you're using 17, some of newer version - try to play around with this sett... See more...
Try explicitly setting this thing in configuration, not removing it. Also, this was relevent for Workstation 16, not 17. If you're using 17, some of newer version - try to play around with this setting. I mean, instead of  usb.restrictions.defaultAllow = "TRUE" try to remove quotes completely usb.restrictions.defaultAllow = TRUE or to replace them with apostrophes  usb.restrictions.defaultAllow = 'TRUE' We never knew how this feature works because it was never (openly) documented, so the only way to figure that out - is just to experiment with it.
Did you used "Easy Setup" feature? As far as I know, it's taking responsibility of configuring Windows during installation with paramerets that you're setting. The issue could happen during this auto... See more...
Did you used "Easy Setup" feature? As far as I know, it's taking responsibility of configuring Windows during installation with paramerets that you're setting. The issue could happen during this automatic configuration. From the other side: issue is not in Windows setup or OS config, it's in VM config, so maybe Easy Setup is not is not affecting VM's config file in a way of adding above mentioned line. Also could be helpful: do you have this line in *.vmx config file? Maybe the value has been set to "TRUE" on your side. Anyways, it's an undocumented configuration parameter that couldn't be changed in GUI. Googling this parameter gave me nothing. It is not mentioned in VMWare Docs. There is no way of knowing what is blocking USB redirection in case you don't have other fully functioning VM. So, is there a way to report issue to knowledge base or something similar?
I found the solution! Thanks @CarltonR for idea to check behavior of other VMs, and good that I'e had one. I've compared configuration files for two VMs mentioned before: created in older version o... See more...
I found the solution! Thanks @CarltonR for idea to check behavior of other VMs, and good that I'e had one. I've compared configuration files for two VMs mentioned before: created in older version of VMWare Workstation and newest one (at the moment 16.2.1). There were some differences caused by a way of creating VM (I suspect that I've created old one without using VMWare's Easy Install), but that's not the case, I assume. I've found one very interesting line in "*.vmx" configuration file: usb.restrictions.defaultAllow = "FALSE" It's very interesting because looks like it has been added automatically in the VM creation process, and it is NOT configurable from the GUI. I am considering this as a major flaw, but don't know how to report that problem to VMWare bug-tracking team. Also, there's not enough documentation about configuring VMs directly in "*.vmx" files, all of the docs I've seen so far are explaining configuration in GUI only. After deleting this line from VM's configuration file all listed USB devices became able to be connected to VM. Problem solved.   tl;dr Open VM config file (with ".vmx" extension) with a text editor, find line mentioned above and delete it completely. Do this when VM is powered off.
>But suggest confirming, under the Settings - Hardware tab for the Guest [Win 7] in question that there is a 'USB Controller' entry present on the list of Devices. Yes, I haven't touched it at all, ... See more...
>But suggest confirming, under the Settings - Hardware tab for the Guest [Win 7] in question that there is a 'USB Controller' entry present on the list of Devices. Yes, I haven't touched it at all, didn't removed and added again, it's there, I can choose 1.1, 2.0 & 3.1 versions of USB.   >Is this happening for all Guests or just this one ? That was a very good question! I moved this VM to laptop and tried to launch it there - no luck, same problem. But, on the laptop I've had previous VM, created in another version of Workstation 16. I can't say it's version because I've upgraded application version to the same that I'm using on desktop. So, USB redirection works in other VM without any problems! And that's weird. Same settings for USB controller. The only difference I've noticed: "Version" field in VM's description. Old & functional one has "Workstation 16.x virtual machine", when new one has "Workstation 16.2.x virtual machine". Anyways, it's just giving us hint, but not solves the initial problem: non-functional USB redirect on new VM. Of course, I could download older version of Workstation 16, but to check if it's working - I should install OS completely, update it (because several drivers from VMWare Tools are signed with SHA-2 which is not supported natively by Win7 SP1), install VMWare Tools and only then - check if it works. Looks to me like a useless effort, but I could be wrong.
All USB Devices are greyed out. VMWare Tools installed, both on host and guest. VMWare Wrkstation Player: 16.2.1 VMWare Tools: 11.3.5 Host OS: Windows 10 21H1 x64 Guest OS: Windows 7 SP1 x86 VM... See more...
All USB Devices are greyed out. VMWare Tools installed, both on host and guest. VMWare Wrkstation Player: 16.2.1 VMWare Tools: 11.3.5 Host OS: Windows 10 21H1 x64 Guest OS: Windows 7 SP1 x86 VMWare USB Arbitration Service is running, never stopped. Device that I want to redirect is named "Ethernet Gadget", connected to USB 2.0, USB controller in VM's setting also 2.0. VM just has been created in this version of VMWare Workstation Player.   What could be the root of the problem? What additional logs could help to resolve the problem?