Microsoft releases Windows 10 build 19002 to the Fast ring

[Karlston]

Microsoft releases Windows 10 build 19002 to the Fast ring

 

Microsoft released this week's Windows 10 Insider Preview in the Fast ring today, bringing the build number to 19002. As usual, there's not a whole lot that's new. It's really just that the Bluetooth pairing improvements seen in earlier builds are now available for all Insiders, rather than a select few.

 

While we're still a couple of weeks out from the release of the Windows 10 November 2019 Update, this is a preview of 20H1, the feature update that will roll out in the spring. It seems, however, that most of the big new features that we can expect are already included.

 

Here's the full changelog for build 19002:

Update on improving your Bluetooth Experience

With Build 18985 we announced we were working on improving our streamlined workflow for pairing your Bluetooth devices. We’re happy to share that this change is now rolling out to 100% of Insiders–thank you to those that have already tried it and shared feedback!

We also wanted to add two new peripherals to our supported device list:

• Microsoft Bluetooth Keyboard
• Microsoft Bluetooth Mouse

While 20H1 won't be shipping for another six months, the Fast ring has already been testing it for just as long. This is new territory for the Windows Insider Program, which typically starts testing new releases after the last one is out. It's unclear what's going to happen once the November 2019 Update ships, but we'll first see changes in the Skip Ahead ring.

 

 

Source: Microsoft releases Windows 10 build 19002 to the Fast ring (Neowin)

[Karlston]

Here's what's fixed, improved, and still broken in Windows 10 build 19002 

 

This week's Windows 10 Insider Preview is build 19002, and as usual, there's nothing new or exciting about it. There are only some minor improvements to the new Bluetooth pairing features, such as support for more Microsoft peripherals and that it's available for all Insiders now.

 

There is, however, a long list of fixes, improvements, and known issues to be aware of. Here's what got fixed and improved in build 19002:

• We fixed an issue that could result in upgrades failing with error 0x8007042b.
• We fixed an issue resulting in the acrylic effect in the Action Center only appearing after the Action Center opening animation had finished.
• We fixed an issue where with multiple monitors and different DPIs, the File Explorer search box could become enlarged and offset.
• We fixed an issue with the search indexer resulting in unexpected files being returned as search results when searching using French (France).
• We fixed an issue for Japanese users where the user name in the Settings header wasn’t displayed in the correct order.
• We fixed an issue resulting in clipboard history, WIN+(Period), and the touch keyboard displaying English text when being used with non-English display languages.
• We fixed a race condition that could result in devices not reconnecting after toggling Bluetooth off and back on.
• We fixed an issue resulting in the VPN sometimes not automatically connecting after waking your device from sleep.
• We fixed an issue that could result in the brightness getting stuck at 0 or 100% and requiring a reboot before it could be changed.
• Text cursor indicator works better in more experiences (e.g. Word, Run dialog, Outlook) now.
• The Magnifier centered text cursor option should now work correctly when switching Magnifier modes.
• We fixed the mouse pointer visual when using the Magnifier docked mode.
• We fixed a bug where Narrator was not saying the state of Scan mode when Edge was opened or closed.
• We fixed a bug in Narrator where Narrator sometimes say password twice when focus was in a password edit field.
• We fixed a bug in Narrator where scan mode was getting stuck in edit fields in Firefox.
• We’ve made some general improvements and bug fixes for the Windows Subsystem for Linux (WSL), please see the WSL release notes for details.
• If you were one of the Insiders experiencing frequent explorer.exe crashes recently, please go to the Microsoft Store and check for Xbox game bar app updates (specifically version 3.34.4xx should have the fix). If you’re on this app version and still seeing explorer.exe crashes, please file feedback and we will investigate.
• Just a heads up that we’re expanding the rollout of the Settings header to more Insiders, so it may now appear for you when it hadn’t before. As always, we welcome feedback about Settings – in the Feedback Hub you can share it under Desktop Environment > Settings.

There are also a bunch more known issues than there were last week:

• We’re working on a fix for an issue that started with the previous flight where some devices are getting stuck during shutdown or restart and appreciate your patience. If you’re impacted by this issue, please see this forum post for workaround options.
• There has been an issue with older versions of anti-cheat software used with games where after updating to the latest 19H1 Insider Preview builds may cause PCs to experience crashes. We are working with partners on getting their software updated with a fix, and most games have released patches to prevent PCs from experiencing this issue. To minimize the chance of running into this issue, please make sure you are running the latest version of your games before attempting to update the operating system. We are also working with anti-cheat and game developers to resolve similar issues that may arise with the 20H1 Insider Preview builds and will work to minimize the likelihood of these issues in the future.
• We’re investigating an issue where initiating “Reset this PC” with the cloud download option isn’t working on this build or the previous one when started from Windows RE.
• We’ve heard that Settings still isn’t available outside of launching via the URI (ms-settings:) for some Insiders and are investigating.
• When using dark theme, the hardware keyboard text prediction candidate window is unreadable due to black text on a dark grey background.
• When optional updates are available, Insiders with the Settings header may see the Windows Update indicator in a warning state, although the main page of Windows Update Settings shows that everything is up to date.
• Bluetooth devices may not reconnect as expected after closing the device lid for certain devices. We’re working on a fix, but in the meantime, you can toggle Bluetooth off and back on in the Settings app or reboot the device and that should resolve the issue.

As usual, you should read through the known issues before installing any Fast ring build, especially since there are a bunch of new ones here. Many of them seem to have workarounds though. There's a 'Reset this PC' issue that only occurs from the Recovery Environment (there are many other ways to reset your PC), Settings might not work from the Start Menu but you can manually use the URI, and so on.

 

You can grab today's build through Windows Update. If you're not on the Fast ring yet, you can go to the Windows Insider Program tab in Settings to get started.

 

 

Source: Here's what's fixed, improved, and still broken in Windows 10 build 19002  (Neowin)

[masterupc]

It's not worth the time... I've reverted to the previous version because of all errors and bugs and crap... damn!

[Karlston]

Microsoft releases Windows 10 build 19002.1002 with a single fix

 

Earlier this week, Microsoft released Windows 10 Insider Preview build 19002 to the Fast ring. Unfortunately, it came with some new known issues, one of which was that a machine might get stuck shutting down. Today, the team is issuing a fix.

 

The new build is 19002.1002, and it's once again available in the Fast ring. According to the blog post, that's all that's new in this minor update. There wasn't a lot that was new in the build to begin with, only providing some minor improvements to the new Bluetooth pairing features introduced previously.

 

There are still a bunch of known issues to be found in this build though. The new cloud download feature might not work when it's initiated from the Recovery Environment, and Settings might not launch from the Start Menu, requiring users to enter the URI. There are a few others as well, none of which are particularly deal-breaking.

 

Of course, there will likely be a new build next week, as there usually is. If you're looking for any of the other issues to be fixed, you'll have to wait until then.

 

 

Source: Microsoft releases Windows 10 build 19002.1002 with a single fix  (Neowin)