Microsoft today released Windows 10 build 14376 for Fast Ring Insiders. This build is from the Redstone branch which identifies itself as "version 1607". Microsoft is focused on bugs so this new release comes with no major changes or features. Instead, it comes with a huge list of bugfixes. Windows 10 version 1607, also known as Anniversary Update, will be released on 2 August, 2016, so Microsoft is polishing the existing functionality.
This new build comes with a very minor changes from the recently released build 14372, so you will not find many new features:
We have been testing with Windows Insiders a preview of the “Messaging everywhere” feature that allows you to receive and send text messages from your Windows 10 phone directly to and from your Windows 10 PC. The experience was well-received by Insiders however we believe we can deliver an even better experience through the Skype app. Because of this, we decided not to release this feature as part of the Windows 10 Anniversary Update this summer. Starting with Build 14376 and going forward, Insiders will no longer have the ability to reply to text messages from their phone via the Messaging app on their PCs. The ability to reply to text messages on your PC using Cortana is unaffected. Going forward, we will be working with the Skype Team on delivering a great “messaging everywhere” experience on your Windows 10 devices through the Skype app. We will share more details about this experience in the months ahead.
Advertisеment
There are no known issues for Windows 10 build 14376, so this build can be considered stable.
The list of fixes looks as follows:
- We’re rolling out an Store update (11606.1001.25) that improves performance and reliability and includes fixes for accessibility as well.
- Clicking on networks or VPN connections in the network flyout on the taskbar should now launch the network settings page like it should. We also fixed an issue where the network flyout would sometimes only show the network settings link, despite being currently connected to Wi-Fi.
- For my dev peeps: we fixed the issue causing an error message when you enable Developer Mode due to the necessary package needed from Windows Update not being published appropriately. Go forth and create!
- We have updated Narrator to now support using physical volume buttons to adjust the volume while Narrator is in Scan Mode. We also fixed an issue that could result in Narrator crashing when arrowing through list entries.
- We have updated Windows Hello on the Lock screen to not repeat the name of the person logging in, when it is already displayed on the screen.
- We have fixed an issue where you might be unable to type in some UWP apps. We also fixed an issue resulting in certain Polish characters being duplicated when typed into UWP apps.
- We fixed an issue where the Lock screen background might not be displayed correctly.
- We fixed an issue where your password would revert be being hidden if you tried to edit it while holding the reveal button.
- We fixed an issue where the search dropdown in the Settings app could end up displaying above the search box instead of below it. We also fixed an issue where the “For developers” settings page would be blank while checking for an optional package, and an issue resulting in no handwriting, speech and other optional components being listed for languages that do support them.
- We fixed an issue that could result in not being able to turn on “set time zone automatically”.
- We fixed an issue where the icons in some Start menu tiles could appear zoomed in, for example Alarms & Clock app or Calculator app.
- We have improved the consistency in scrolling and zooming speeds between monitors when using a precision touchpad on a multiple-monitor setup.
- We fixed an issue that could result in Explorer.exe crashing after receiving a notification from Microsoft Edge.
- We fixed an issue where the caret might jump to the beginning of the line, rather than maintaining current y axis position when using the up and down arrow keys in a textbox in Microsoft Edge.
- We fixed an issue resulting in an authentication error when launching mstsc.exe from an elevated Command Prompt.
That's it.
Support us
Winaero greatly relies on your support. You can help the site keep bringing you interesting and useful content and software by using these options:
If you like this article, please share it using the buttons below. It won't take a lot from you, but it will help us grow. Thanks for your support!
Advertisеment