Forum Discussion
Bluetooth and Wireless display not working on Windows Server 2022
Dear All,
While this may not be the required case in production.
However, on my standalone laptop, I have installed Windows Server 2022 Datacenter Edition(GUI).
Wireless Network is working which helps me to connect to WiFi network for internet.
- BUT, Bluetooth devices are NOT connected. They are detected and showed as 'paired' but never connects.
- ALSO, it fails to detect the Microsoft Wireless Display Adapter. This is useful when I want to present my laptop screen with all Hyper-V machines on a projector with which Microsoft Wireless Display Adapter is connected.
Let me know if anyone has experienced this similar behavior and if there are any suggestions around.
regards
Kayyum
/wave from the Windows Server product team. I just want to confirm what Karl said, we have been monitoring this thread and we hear your feedback. For the next release of Windows Server we have addressed these issues. THANK YOU for your feedback and passion for Windows Server!!!
I announced a week ago at Ignite, here's the session if you want to go learn more about what is coming in the next release of Windows Server:
What’s New in Windows Server v.Next (microsoft.com)
Thanks!!
Elden Christensen
Principal Group PM Manager
Windows Server Development Team
- SergejKillerBrass Contributor
I was finally able to make Bluetooth audio devices work on Windows 2022.
I've installed required drivers and services from Windows 10 donor images.
It was hard and time consuming. Don't really understand why Microsoft doesn't want to include Bluetooth audio support into Windows Server images, specifically that is was working fine in Windows Server 2019.
Anyway the steps are not trivial at all and requires good knowledge of registry and permissions model in windows.- Kayyum MCopper Contributor
SergejKiller - I installed Windows Server 2022 build 22483 and finally Bluetooth device works however, the Miracast wireless display device now shows the message that it is not supported 😞
- laowangCopper ContributorCan you share Bluetooth audio devices?
- SergejKillerBrass ContributorI've never heard of the ability to share audio devices. What exactly do you mean by "share devices"?
- Jan_PavelCopper ContributorHello, can you please provide detailed information about using drivers from Win10? I've tried to backport AVRCP drivers, but with no luck 😞
- SergejKillerBrass ContributorHave sent a private message.
- Good news, the next Iteration of Windows Server will have WiFi and Bluetooth Support out of the box.
- EldenChristensenMicrosoft
/wave from the Windows Server product team. I just want to confirm what Karl said, we have been monitoring this thread and we hear your feedback. For the next release of Windows Server we have addressed these issues. THANK YOU for your feedback and passion for Windows Server!!!
I announced a week ago at Ignite, here's the session if you want to go learn more about what is coming in the next release of Windows Server:
What’s New in Windows Server v.Next (microsoft.com)
Thanks!!
Elden Christensen
Principal Group PM Manager
Windows Server Development Team- DrSunCopper Contributor
EldenChristensen good job listening to the community, thanks!
- pennesCopper Contributorand thats based on the Win 11 OS? the UI is horrible though.
- YourusernamemustbeatleastCopper Contributor
Karl-WE, Yash_Shekar That's great, finally! But note one more as well:
In Windows Server versions prior to 2022, you could take drivers from Windows 10, modify their .inf files for the Server, and install them in no signature verification mode. And this method worked not only with the Bluetooth drivers (including HIDs, gamepads, and other client OS drivers), but also with third-party drivers whose .infs needed to be changed for whatever reason.
Whereas in 2022, client Windows drivers fail to start with a no signature error. I don't know if the WS2022 issue extends to drivers other than the client ones, but if so, this issue should definitely be fixed as various hardware depends on it.
And if you ask me, I think the best possible solution is to let administrators (PC Masters if you will, a concept that is forgotten these days) choose which drivers should run, regardless of their signatures or the Windows version specified in their .inf files. And, of course, face well-described errors if the chosen drivers fail to run.
- pennesCopper Contributorbtw do you know what to do with these files and how to install them in windows 10? would love to have a step by steps what to do..
Great news Microsoft has implemented our feedback and the next Windows Server, hopefully released end of 2024 will include WiFi and Bluetooth Support.
Thank you EldenChristensen and the team.
Oh, missed your follow up above and that I have already noted it before. I am getting old...
Kayyum M would you mind marking Eldens posting as best response?
What are your options if you are affected:
If your workload isn't a production workload
And your policy doesn't require Microsoft Support or strict data protection rules, regarding to telemetry, register with the Windows Insider programme, and fetch Windows Server vNext, Inplace Upgrade to Windows Server vNext from existing Windows Server 2019 or 2022.
The activation keys are to be found in each release announcement over at the Windows Server Insider techcommunity section.
What are your questions left?
- Reza_AmeriSilver ContributorFor security reason services like Bluetooth and Wi-Fi are off by default but you could enable them and test them out. In case you have access to a Windows 10 PC, open start and open the Feedback Hub app and in the category select Windows Server and file a bug report and if you have any log files like errors, then attach it to the report, so Windows Server team would be able to investigate it.
Reza_Ameri I can support this issue partly.
If you have a bluetooth radio (usb dongle) and install the latest Server 2022 LTSC preview it will work.
if you upgrade from 2019 LTSC to 2022 LTSC preview the same dongle will not work, and there is no way to make it work (driver issue in device manager)- Kayyum MCopper ContributorI have a fresh install of Windows Server 2022 LTSC and even with a USB dongle, it fails to connect.
- Austin_MBrass ContributorIt was referenced as filenames. ISO images for the general availability build of Windows Server 2022 are open at Microsoft Evaluation Center.
Inspect if Bluetooth hardware is on your computer and enabled. Ensure your computer has the required hardware and that wireless is turned on. Bluetooth requires both hardware and software to work. Unfortunately, not all wireless networking hardware supports Bluetooth. - antonwas1Copper Contributor
I also want to experiment with your explanation to this issue.
Can you please send me the Bluetooth_WS2022_v3.zip?
Thank you in advance!!
- Duke2kBerlinCopper ContributorHi, could you also send me Bluetooth_WS2022_v3.zip as well as Bluetooth_HID_v2.zip?
Thanks very much in advance. - obarbuCopper ContributorHello Serge.
Thanks for sharing your hard work, but there is a better and simpler alternative. There is a full BT stack available from Toshiba (https://dynabook.com/assistpc/download/modify/soft/btswt/TC00632300N.exe). I have tested on Server 2022 and vNext, audio works fine.- Jimmy007Copper Contributor
please send me Bluetooth_WS2022_v3.zip and Bluetooth_HID_v2.zip。tks
- jecudragosionutCopper Contributor
SergejKiller
Please can you send me Bluetooth_WS2022_v3.zip and Bluetooth_HID_v2.zip.
Thanks in advance!!- obarbuCopper ContributorDon`t waste your time, just download this: https://dynabook.com/assistpc/download/modify/soft/btswt/TC00632300N.exe , run and enjoy sound on Windows Server. O zi buna.
- jecudragosionutCopper Contributor
obarbu Thank you, but I tested and it’s not working with Sonos Era 300, I want to try the another way and let’s see if it’s working. Mulțumesc!!
- DrSunCopper Contributoreverything perfect except bluetooth PAN, it says not signed still, even after hid_v2
with signing disabled shows in device manager perfectly fine
ws2022 standard april 2023 build 20348.1668- SergejKillerBrass ContributorMost likely a newer version of a driver was released by Microsoft. I don't have Windows Server anymore to update the drivers.
But you can try to find the bthpan.sys file in \Windows\WinSxS\ folder extract it over the modified drivers. Then you can install it and the driver will be recognized by windows as signed.- Abraziv777Copper ContributorHello, SergejKiller I would sure appreciate if could share the zip of those Bluetooth_WS2022_v3.zip for windows server 2022!