Forum Discussion
Bluetooth and Wireless display not working on Windows Server 2022
/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
hm, no luck - I've tried to pair/install device again and device manager looks better - but:
- headset is present - also in Sound devices - but no audio output (strange is the recording test is ok - as shows volume indicator 🙂
- when I switch sound device to HeadSet one, system is freezing - for example it's unable to play YoutTube video...
- headphones are hidden/not available in Sound Devices - screenshot...
Maybe I'll try it on clean OS installation... 🙂
Drivers looks good. Please check that you have all registry entries mentioned in the doc.
Have you forgot to manually update CurrentVersion\Svchost entries?
- Hello, Could you sent me Bluetooth_WS2022_v3.zip and Bluetooth_HID_v2.zip?
- Hi friends. Please send me this file
bluetooth_ws2022_v3.zip
Thank you My friend or someone he's already sent, could send me the file bluetooth_ws2022_v3.zip
Thank you very muchSergejKiller can you also send my the Bluetooth_WS2022.zip file? My email is mailto:email address removed for privacy reasons
thanks
- HI 2 all!
Can anyone send Bluetooth_WS2022.zip to me? Or latest Bluetooth_HID.zip?email address removed for privacy reasons
Best regards Here is the answer to your request 🙂 http://www.yhesitate.com/2011/08/07/no-madam-it-took-me-my-whole-life/
But if talk seriously: Windows is just my tiny hobby. Long time ago I used to work with a guy who did a reverse engineering and worked on windows drivers. I've learned a few tips and tricks from him back then. Interestingly enough 17 years later the same tricks still work :).
I assume anyone who writes windows drivers these days would be able to do similar things with ease. So if you also want to learn how to do that, look into reverse engineering and how drivers are created. For most stuff you don't need expensive software. But this is not my area and I'm not going to teach anyone.
- Sergej, I am not talking about instructions on how to USE Bluetooth_HID.zip. I'm talking about how you figured out what to pick and choose out of win10 to get BT support to work on Server in short how you created the Bluetooth_HID.zip file to begin with. That process might be useful in the future for some other thing MS "forgets" to add in a future server iteration.
If you have instructions inside Bluetooth_HID.zip on how to create Bluetooth_HID.zip and where to get the tools you used to figure it out, then PM me Bluetooth_HID.zip and I'll post the instructions only. I'd rather YOU post the instructions but you haven't.
Once more I'm not interested in how to USE Bluetooth_HID.zip as that's been quite sufficiently documented in this thread. I want to know you CREATED Bluetooth_HID.zip - The instruction is open for everyone. Feel free to republish it the way you want it together with any files you like. I've put it into a doc, because it was easier for me to iterate over it and fix errors.
I won't even stop on reasons why I will never publish any copyrighted content.
But again, if you know what to do and how to address that, just do it, don't blame others. - While I agree with some of what you say about the process and all, what I am positive you are WRONG about is your trying to bully the man to do something the way you wish it to be done and likely not for the puritan reasons you are stating as the man has given access to the files and process es and if you do not have access to them you certainly could have and if you feel then so strongly about all this, you can publish the **bleep** thing yourself and not come on here acting holier than thou and spruting out you bs and hoping to garner mass support for something that is non or your beeswax and if I am not mistaken accusing this helpful man of doing the very thing that you too are then guilty of for not already doing that which you demand he does when you are too lazy or too unintelligent to post yourself. Thats all.
I don't see the point of being all mysterious about the contents of bt_win2022 nor of your instructions, Serge. This forum and the Internet in general is littered with people who have posted "I have instructions for doing this here" to various links that are dead. Windows Server 2022 is going to be End Of Lifed in late 2013 are you going to keep your email address, google drive and that file around until then? What if you get hit by a bus and your heirs wipe all your accounts? Please be responsible about this.
For everyone else and for future readers there's nothing special about bt_win2022 it is just older drivers and registry entries lifted out of windows 10. If you are reading this 10 years from now and Serge has long since moved on, you can reconstruct the contents by doing the same thing he did which is by installing old copies of win10, and copying the stuff you need out of them. Of course, it would be NICE if Serge could post his instructions for actually finding and copying out of win10 all of this stuff since it would likely be applicable for other drivers than just BT but if he does not, there should be enough instructions for doing this already on the Internet you will have to piece together for yourself. Or, we might be lucky and Serve will indeed still be responding to PM's 9 years from the date of this post.
