As in 14376 is an awful build and will never reach the public? Or 14376 is going to be released to Insiders today? Your message can be interpreted in multiple ways.
Where in the world did you get that I'm saying it's awful? I was asking what exactly was the "talk" around 14376 about and I threw that out there as an example of a possible "talk" related to 14376....I claim no knowledge of anything about 14376, never did.
It has been the policy of Microsoft to release .ISO's when a Build is released to the Slow Ring. As to "this week" will have to wait and see.
I've switched over to this build as soon as it was pushed out to Slow ring the other day. Has anyone else confirmed significantly flaky issues between Qualcomm Atheros Bluetooth chipsets and bluetooth mice? The bluetooth mouse seems to jump over icons on desktop and taskbar, almost like some game of trying to click on the programs that I need to run. Sadly, I am losing this game. Also, the bluetooth shuts off repeatedly and I need to use the Action Center to enable/disable bluetooth in order for the bluetooth functionality to come back on. Since Microsoft has rendered all previous drivers deprecated on these 143** builds, my options are limited at the moment. Has anybody found any tweaks or workarounds to temporarily fix this Qualcomm Atheros bluetooth chipset issue?
Perhaps, you would have to search online for latest update for your Bluetooth chipset. Have you tried to uninstall it at ''Device Manager'', restart your system and wait for it to be reinstalled?
Thank you for your suggestion. But unfortunately, yes that was one of the first things that I tried a few times initially to remove the device drivers and reinstall, reboot, etc. It seems that there are some common glitches with the bluetooth stack in these newer builds reported elsewhere as well. I will just have to be patient with it for now until a newer slow branch build comes along or an update comes along. Thank you for your suggestion regarding Toshiba bluetooth stack as well. I was unaware of that, though I did some research and testing after your suggestion. Unfortunately, this will not even install or work in these Anniversary Update builds because Microsoft is now requiring all kernel-mode drivers to be signed with SHA-256 and signed by Microsoft Windows as well. So this Anniversary Update is going to cause quite a bit of chaos when it goes live in August, I'm certain. Not a lot of smaller developers can afford EV certs and such.
I'm using the stack both on Server 2016 and 14376 And it works flawlessly. Clearly if you don't have the driver, and the driver is not included in the toshiba stack itself (as usual) the matters shifts from a BT problem to a driver problem With this pace we will need to "jailbreack" win 10 even to install a decent browser on it, in a couple of years or so. They are just taming the users