Forum Discussion
Kayyum M
Mar 19, 2021Copper Contributor
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
- pnt-ychengCopper Contributor
There is a problem regarding Bluetooth connection on the Windows Server 2025 system:
personal area network (pan) not connecting and giving an error.
Hi,
When I try to connect via PAN it gives the option belowAfter that, it gives me this screen and does not connect
- SergejKillerBrass Contributor
There are no BTPAN drivers for windows server 2025.
What you can do is:
1. load windows with disabled driver signature enforcement.
2. find BTPAN drivers in Windows\WinSxS folder
3. copy driver in a separate folder
4. modify .inf file and remove "...1" suffix from inf sections and any references to those sections.
5. install that driver
6. accept installing driver from unknown source.
7. reboot.
8. profit!
- SergejKillerBrass Contributor
file is called bthpan.inf located in \Windows\WinSxS\amd64_dual_bthpan.inf_31bf3856ad364e35_10.0.26100.1150_none_ba62e7e3ffd67b5c
replace all occurrences of "NTamd64...1" with"NTamd64"
- ccxz84Copper Contributor
SergejKiller, can you please send these zip files to me? Thank you! - fsnufferCopper ContributorI am just a a rookie admin but when I started the Windows Audio service my headset started working.
- JustKlodCopper Contributor
@SergejKiller, can you please send these zip files to me? Thank you!
- brwilkinsonCopper Contributor
When adding a BT device in 2025, I don't get any pop up, when adding Audio device is selected. The driver appears to be there, however, not sure how to actually add a device?
- Yash_Shekar
Microsoft
brwilkinson Could you email me a screenshot of what you're seeing at yashshekar at Microsoft dot com?
- Elden_Christensen
Microsoft
We have added WiFi and Bluetooth to Windows Server 2025, please go try out the Windows Server Insider builds and give us feedback to ensure it meets your needs. This was in direct response to the feedback in this thread, so help us make sure we are going to deliver what you want 🙂- pidimensionsCopper ContributorSimilar to what brwilkinson said, on the Windows Server 2025 Pre-Release Insider build, specifically build 26212, there is no option to actually connect to a device. Also, there is the "driver is unavailable" message under my bluetooth adapter even though I have installed the driver from the website, like what happened in Windows Server 2022.
- MaximeRastelloBrass Contributor
Hello SergejKiller, would it be possible to have the links for the drivers? Thank you!
- DEVASTECCopper Contributor
SergejKiller, can you please send those zip files to me?
@everyone if someone has those files would he care to maybe send em to me?
Thank you 🙂 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 Elden_Christensen 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?
- Good news, the next Iteration of Windows Server will have WiFi and Bluetooth Support out of the box.
- Elden_Christensen
Microsoft
/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- Kayyum MCopper Contributor
Elden_Christensen - Thanks for your response and having this fixed in future release of Server OS version.
- Abraziv777Copper ContributorI apologize in advance for the amateurish question. But what do you mean by "the next Iteration of Windows Server"? Do you mean Windows Server 2022 updates in December? Or Windows Server 2024-2025 which has not even been announced yet?
- 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..
- mexxtronCopper ContributorSergejKiller Can you please PM me both links to Bluetooth_WS2022_v3.zip and Bluetooth_HID_v2.zip? I found them on pcbeta but this forum ask for registration (invites only).