After many generations of Windows patches, reinstalling the latest Windows will resolve these issues.
How can the conflict between hyper-v (virtualization) and the drivers of Bluetooth and USB 3.2 be fixed in the Intel Ultra 258v platform?
唯 木
0
Reputation points
It occurs on the new AI Laptop named "ASUS Zenbook S 14 (UX5406)".
After enabling virtualization and using Hyper-V for WSL, the Bluetooth and USB 3.2 drivers began to function at fault.
I attempted rebooting and reinstalling the official drivers, but the issue persists.
Using WSL is crucial, and any assistance from the community would be appreciated.
Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V
{count} votes
-
唯 木 0 Reputation points
2024-10-17T03:08:15.6666667+00:00 I'm sorry that descriptions could cause a misunderstanding about that issue.
Then I will make some additions to that.
The situation I found is that a conflict appears when enabling Hyper-v. The Intel(R) USB 3.20 extensible host controller and Bluetooth will halt in that case when using Windows but not the VM of Hyper-v. I don't mean a fault occurs when passing Bluetooth or USB to the VM of Hyper-v, but the device's drivers will fault on Windows when enabling Hyper-v on Windows. Not only the Bluetooth but the whole USB also were fault. I could not connect to any USB device. And my Bluetooth is on Intel BE201, not USB Bluetooth. But the interesting thing is that my Wi-Fi on Intel BE201 is running correctly.
Sign in to comment
2 answers
Sort by: Most helpful
-
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous2024-10-17T02:13:56.4366667+00:00 Hi 唯 木,
Thanks for your post. Generally speaking, rather than focusing on passing Bluetooth to the VM, you need to focus on passing the actual Bluetooth adapter. Basically, the only hardware peripheral passthrough available to Hyper-V is PCIe. So in order to access a Bluetooth adapter, you'd need to pass through whatever PCIe device it's attached to. As such your best bet is you have a dedicated Bluetooth PCIe card to pass to the VM.
If you wanted to pass a USB Bluetooth Adapter, I'm pretty sure you'd have to pass the entire USB root hub (or do something unusual like USB over IP.)
Best Regards,
Ian Xue
If the Answer is helpful, please click "Accept Answer" and upvote it.
-
唯 木 0 Reputation points
2024-10-17T03:02:05.78+00:00 I'm sorry to make a misunderstanding about that issue. The situation I found is that a conflict appears when enabling Hyper-v. The Intel(R) USB 3.20 extensible host controller and Bluetooth will halt in that case when using Windows but not the VM of Hyper-v. I don't mean a fault occurs when passing Bluetooth or USB to the VM of Hyper-v, but the device's drivers will fault on Windows when enabling Hyper-v on Windows. Not only the Bluetooth but the whole USB also were fault. I could not connect to any USB device. And my Bluetooth is on Intel BE201, not USB Bluetooth. But the interesting thing is that my Wi-Fi on Intel BE201 is running correctly.
-
唯 木 0 Reputation points
2024-10-17T03:02:57.3133333+00:00 I'm sorry to make a misunderstanding about that issue. The situation I found is that a conflict appears when enabling Hyper-v. The Intel(R) USB 3.20 extensible host controller and Bluetooth will halt in that case when using Windows but not the VM of Hyper-v. I don't mean a fault occurs when passing Bluetooth or USB to the VM of Hyper-v, but the device's drivers will fault on Windows when enabling Hyper-v on Windows. Not only the Bluetooth but the whole USB also were fault. I could not connect to any USB device. And my Bluetooth is on Intel BE201, not USB Bluetooth. But the interesting thing is that my Wi-Fi on Intel BE201 is running correctly.
-
Anonymous
2024-10-22T07:55:23.9866667+00:00 Hi Wei,
Thanks for your reply. I have done a lot of research but didn't find any known issue between the Intel(R) USB 3.20 and Hyper-V function. It is recommended to reinstall the Intel(R) USB 3.20 driver and see if it works.
To find the latest drivers you can visit the Intel Download Center or use the Intel Driver & Support Assistant (IDSA) tool to automatically detect and update your drivers.
- Using the Intel Driver & Support Assistant:
Go to the Intel Driver & Support Assistant download page:https://www.intel.com/content/www/us/en/support.
Click "Download now" to download the installer.
Run the installer and follow the on-screen instructions to install the IDSA tool.
Once installed, the IDSA tool will automatically launch and start scanning your system for Intel hardware and drivers.
If an update is available for your USB controller, the tool will provide you with the option to download and install it.
- Alternatively, you can manually search for drivers on the Intel Download Center:
Go to the Intel Download Center:https://downloadcenter.intel.com/
In the search bar, type "USB 3.20 Extensible Host Controller" and press Enter.
Look for the appropriate driver for your system (consider your operating system and system architecture).
Click on the driver to access the download page, and then click "Download" to get the driver installer.
Run the installer and follow the on-screen instructions to update your USB controller driver.
After updating the drivers, restart your computer to ensure the changes take effect.
I hope this is helpful. If you require any additional assistance, don't hesitate to respond to this.
-
唯 木 0 Reputation points
2024-12-07T08:31:39.39+00:00 Hi,
It has been a while since I last responded to you. During this period, I finally resolved the driver issue by reinstalling the latest Windows 11 in a night. However, I regret to say I was still unsure of the exact cause. I could only speculate that it might be due to the ultra-258V CPU being too new, which could lead to incomplete synchronization with Windows 11's adaptation. In any case, I sincerely appreciate your efforts and those of other active community members who have paid attention to this issue.
Thank you for your contributions!
Sign in to comment -