Helo Windsman , thanks for your effort for helping me Lets start then ; My Bios is already 403 Net Framework Feature is already enabled via Dism using offline image Wireless Network Feature is already enabled All Drivers are okay except blueetooth driver ( Afaik Server has no bluetooth support , am i right ?) I am using Latest Intel RST drivers version 14.8.12.1059 NVidia is also latest version 375.86 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\pciide\Start is set to 0 I disabled the features below and restarted the machine dism /online /disable-feature /featurename:WCF-Services45 dism /online /disable-feature /featurename:WCF-TCP-PortSharing45 dism /online /disable-feature /featurename:Microsoft-Hyper-V-Common-Drivers-Package dism /online /disable-feature /featurename:Microsoft-Hyper-V-Guest-Integration-Drivers-Package dism /online /disable-feature /featurename:SmbDirect Unfortunately the result is the same. My next try will be the eventviewer logs , i hope it will tell me the cause of slow start of windows server Thanks Again Windsman
Install Toshiba Bluetooth stack, it should work. ok, so apparently there is something else, maybe the bluetooth, i don't know. if i found something i tell you. Take care. windsman. EDIT: yes maybe the event viewver can tell you something.
Bluetooth UPDATE: Microsoft Bluetooth Mouse 3600 does not work either. Hello Folks, 10 years on and still everything is painful with this Bluetooth. Does anyone know how to get Blues**t working? I have Bose QC35 headphones, Microsoft BT stack pairs them but no Sound Device is installed under Sound Controllers. I think it is because A2DP profiling is not on Server 2016. They work fine on Win10 Enterprise. Would installing these help from Win10: Microsoft-OneCore-Connectivity-Bluetooth-drivers-Package~31bf3856ad364e35~amd64~de-DE~10.0.14393.0 Microsoft-OneCore-Connectivity-Bluetooth-drivers-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-OneCore-Connectivity-Bluetooth-onecore-Package~31bf3856ad364e35~amd64~de-DE~10.0.14393.0 Microsoft-OneCore-Connectivity-Bluetooth-onecore-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-OneCore-Connectivity-Bluetooth-onecoreuap-Package~31bf3856ad364e35~amd64~de-DE~10.0.14393.0 <etc> Not interested in Toshiba. I am willing to pay for this. Thanks! Jim PS: Many thanks to MDL. I am lurking 10+ years!
I don't like Toshiba's stack. It uses more power. I lose 1.5 hour on my laptop out of the 8 I have if I have just a Bluetooth mouse enabled. It is almost nothing on Microsoft's one probably because of BLE. Everything is there and functional on Windows 10.
Hi Server User Friends ; I have a slow startup problem from the first day when Server 2016 released till now. After searching Event Viewer , i have seen 3 errors and 1 warning in event viewer. I want to ask a question about the warning [FONT=&]Microsoft-Windows-Kernel-Processor-Power Event ID 37 -[/FONT][FONT=&]The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. [/FONT][FONT=&]-The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. [/FONT][FONT=&]-The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.[/FONT][FONT=&] [/FONT]-[FONT=&]The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. [/FONT]Now i want to ask what the 71 seconds is ? Does that mean my computer starts 71 seconds late or what ? And are there friends who know how to solve Event:37 warning ? P.S. the same computer under 2016 LTSB doesnt give that warning
For Windows Mail (HotMail) on Windows Server 2016, give this a try: To Uninstall Microsoft-Windows-Server-Features-Package-AutoMerged-inetcore~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-inetcore~31bf3856ad364e35~amd64~~10.0.14393.0 To Install Microsoft-Windows-Server-Features-Package-AutoMerged-inetcore~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-Windows-Server-Features-Package-AutoMerged-inetcore~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0 Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-inetcore~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-inetcore~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0
The toshiba stack is 1000 times better than MS'. Lighter, functional, reliable, and you don't have to pair the BT device each time you switch the OS in dual boot. Everything is better than the crappy MS stack, Blutonium, Widcomm/broadcomm, Toshiba and so on. Anyway if you want to use the thing just follow the path used for previous servers, get the drivers from win 10, mod them, and disable the driver signature enforcement
I have specifically mentioned that I DO NOT WANT TOSHIBA BT STACK. Is there any reason why everyone is telling me the same despite mentioning this in my post or do you all automatically assume we do not do our research prior to asking a question? 1) Win10 Ent: Everything works perfect with MS Stack. 2) Toshiba Stack: * Bluetooth mouse consumes about 2 Watts per hour whereas it is 0.3 Watts in MS Stack. This is a huge power waster on a laptop. My average is about 10 watts per hour. * Does not find some devices whereas all my devices were found and functional with Microsoft. * Worst of all: If you switch off the BT radio from Toshiba, you need to REBOOT to get it back on. Some of us use BT items intermittently and do not want to have the radio on all the time to save power. This is a simple ON/OFF from Microsoft Action Center. So tell me... why again would I want to use Toshiba c/r/a/p?
T-S, this is beyond my expertise level. I am willing to donate to this if you can take on the project for those of us who needs a solution on 2016 Server.
Progress. Microsoft Bluetooth Mouse 3600 works on Windows Server 2016 Standard on default install. So back to my initial issue... It is A2DP support that is missing. Can't post pics, so image is here (please remove space): https ://i.imgur.com/4Y5MkAK.jpg All files are available on standard places like inf/system32 except: BthA2DP.sys BthA2DP.sys is available on C:\Windows\System32\DriverStore\FileRepository\wdma_bt.inf_amd64_9b500f042c6787e9 Driver details on picture above and quoted part were taken from a working Win10 system. It is under "Sound Controllers" section. On Server 2016, this item is "Other Devices > Bluetooth Peripheral Device". Any experts on how to get this going?
My ServerDatacenter has these files too: C:\Windows\WinSxS\amd64_dual_wdma_bt.inf_31bf3856ad364e35_10.0.14393.0_none_c7e13da0987f31ad BthA2DP.sys BthHfAud.sys wdma_bt.inf It's located in this package: Microsoft-OneCore-Connectivity-Bluetooth-onecoreuap-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-OneCore-Connectivity-Bluetooth-onecoreuap-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0 Give this a try: Step1: Run Command Prompt as Administrator. Step2: Run these commandlines. Code: dism /online /add-package:C:\Windows\servicing\Packages\Microsoft-OneCore-Connectivity-Bluetooth-onecoreuap-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum dism /online /add-package:C:\Windows\servicing\Packages\Microsoft-OneCore-Connectivity-Bluetooth-onecoreuap-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0.mum Step3: Reboot if necessary. Step4: Check device drivers status, and if necessary, manually install the driver by pointing to C:\Windows\System32\DriverStore\FileRepository\wdma_bt.inf_amd64_9b500f042c6787e9\wdma_bt.inf. Step5: Reboot if necessary. Note: 1. xx-XX is your language. e.g. en-US. 2. This is the best I can do for I am not good at drivers.
Many thanks Xinso. I installed these (plus 18 others that has "bluetooth" from Packages directory) successfully but still no go. I will check Win10Ent to see if I am having some additional packages there.
Maybe because forums are meant to get and provide good suggestions? Maybe because , personally, as a BT user since the AD 2001 I know the matter better than most of the other users (clearly you included)? Not everything, the MS bt stack lacks a tons of BT profiles, and sure it works sure for two weeks or so, then there is always a problem. No way MS and most of the american companies tried to kill and to undermine the BT standard in any way, at the end they lost the battle, but they have still to do a lot of homework to put it on pair with good BT stacks. I can't confirm here, I'm using BT mices on all my devices and they work way better than with MS stack, w/o having to repair them every now and then. Never had a problem there I can turn on and off the BT radio from the systray icon w/o a problem Again, because MS stack is the worst BT stack available out there.
@countingcrows According to your screenshot, Code: BtaMPM.sys BthA2DP.sys drmk.sys ksthunk.sys portcls.sys SysFxUI.dll WMALFXGFXDSP.dll all necessary drivers are located in these two packages: Code: Microsoft-OneCore-Connectivity-Bluetooth-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-OneCore-Connectivity-Bluetooth-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0 Microsoft-Windows-Desktop-Shared-Drivers-onecoreuap-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-Windows-Desktop-Shared-Drivers-onecoreuap-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0 And here are the full packages: Code: Microsoft-OneCore-Connectivity-Bluetooth-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-OneCore-Connectivity-Bluetooth-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0 Microsoft-OneCore-Connectivity-Bluetooth-WOW64-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-OneCore-Connectivity-Bluetooth-WOW64-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0 Microsoft-Windows-Desktop-Shared-Drivers-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-Windows-Desktop-Shared-Drivers-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0 Microsoft-Windows-Desktop-Shared-Drivers-WOW64-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-Windows-Desktop-Shared-Drivers-WOW64-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0 No. One more ksthunk.sys missing... Microsoft-Windows-Server-Features-Package-AutoMerged-onecoreuap~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-Windows-Server-Features-Package-AutoMerged-onecoreuap~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0
I had all of these installed previously, there was another driver that I did not mention before which was in one these shared packages. However, it did not work. On Win10Ent, I have this service: BthHFSrv: Bluetooth Handsfree Service Enables wireless Bluetooth headsets to run on this computer. If this service is stopped or disabled, then Bluetooth headsets will not function properly with this machine. This service was not there on Server. Files are in: Microsoft-Windows-Desktop-Shared-Drivers-drivers-Package~31bf3856ad364e35~amd64~~10.0.14393.0 This must have been installed. I will check if that service was activated.
Xinso, after dism successfully completes, isn't BthA2DP.sys supposed to be somewhere on system? I do not see it in usual places. It still is in: C:\Windows\System32\DriverStore\FileRepository\wdma_bt.inf* and WinSXS. PS: Handsfree service does not make a difference as I am not using handsfree but Audio Sink. Tested on Win10E, no difference when it is disabled.
The packages are all present in the installation, but actually not being installed. So, for Server, we need to install these packages before we can install the drivers. Or, you can try to install the drivers thru searching Windows 10 installation, or built-in drivers of Server. One other reason, the drivers working for Windows 10 are not necessarily applicable to Server. For example, my Server 2016 on Asus X99 uses built-in Intel(R) Ethernet Connection I218-LM, not the Intel(R) Ethernet Connection (2) I218-V for Windows 10.