Windows 10 build 19025 is out in the Fast ring with a fix for Sandbox and more

[Karlston]

Windows 10 build 19025 is out in the Fast ring with a fix for Sandbox and more

 

Today, Microsoft released Windows 10 Insider Preview build 19025 to the Fast ring, making it the second one this week. Once again, there are no new features to be aware of. It only contains a list of fixes, one of which resolves an issue that prevented Sandbox and WDAG from working properly.

 

Here's the full list of fixes:

• We fixed an issue from the previous flight preventing Sandbox and WDAG from working.
• We fixed an issue resulting in certain fingerprint readers no longer working as of Build 19013.
• We fixed an issue that could result in VPN Settings hanging after upgrade.
• We’ve done some work to help address an issue that could result in certain modern UI components (including notifications and the network flyout), scaling either too large or too small after attaching an external monitor or remoting into the machine from a monitor with a different DPI.
• We fixed an issue impacted login performance for some users in recent builds.
• We fixed an issue resulting in Windows Hello authentication not working with certain apps in recent builds.
• We fixed an issue that could result in the mouse pointer not displaying when logging in to a PC locally after remoting in.
• We fixed an issue where, when using the touch keyboard docked on a large screen, the keys would stretch out to span the width of the monitor, rather than staying an optimal width for touch interaction.
• We fixed an issue that could result in ctfmon.exe crashing when using reconversion with the Japanese IME in certain text fields.
• We fixed an issue that could result in web activities in Timeline not opening if you had new Edge installed.
• We fixed an issue where a high number of app deployment failures in a short period of time could result in an unexpectedly large volume of disk space being used by evtx files saved under %windir%\temp.
• We fixed an issue resulting in some apps failing to update with error 0x8007000A.
• We fixed an issue resulting in jitters when using Magnifier in certain multi-monitor configurations.
• We fixed an issue where the mouse pointer did not start from where the Magnifier viewport was if it had moved from typing.
• We fixed an issue impacting Narrator performance reading aloud in Outlook after switching focus from an email back to the list of emails in your inbox.
• We fixed a memory leak in EoAExperiences.exe after using the text cursor indicator for prolonged periods of time.

There are also some known issues to be aware of:

• BattlEye and Microsoft have found incompatibility issues due to changes in the operating system between some Insider Preview builds and certain versions of BattlEye anti-cheat software. To safeguard Insiders who might have these versions installed on their PC, we have applied a compatibility hold on these devices from being offered affected builds of Windows Insider Preview. See this article for details.
• We’ve heard that Settings still isn’t available outside of launching via the URI (ms-settings:) for some Insiders and are investigating.
• Some Insiders are reporting that after successfully installing printer drivers from the Optional Updates section, the same driver is still showing as available for install. We’re looking into the issue.
• We’re looking into reports where, when certain external USB 3.0 drives are attached, they stop responding with Start Code 10 or 38.

As usual, this build is from the 20H1 development branch, but it's been a few weeks since we've seen any new features in a Fast ring build at all. Typically, this means that Microsoft is gearing up for RTM, something that's also usually signified by having more than one new build in a week. If so, it gives more credibility to an earlier report that 20H1 will RTM in December. If so, you can still expect to wait a few more months until this update is released to non-Insiders.

 

 

Source: Windows 10 build 19025 is out in the Fast ring with a fix for Sandbox and more (Neowin)

[Karlston]

Windows 10 search fix will stop it sometimes hogging disk or CPU resources

Latest preview version continues work to cure the sluggishness experienced by some users

•  
•  
•  
•  

(Image credit: Future)

 

The latest preview version of Windows 10 has benefited from improvements which continue work to fix problems with excessive disk and processor usage caused by Windows Search, which some users have been experiencing in the past.

 

This comes courtesy of preview build 19025, which is for the update due to land in the first half of next year (20H1), and has just been released to testers in the fast ring – and it’s the only real noteworthy element of this build (although there are also some other minor bug fixes, as ever).

 

The issue with search can actually be traced back all the way to July 2018, when Microsoft first posted about a thorny issue with search functionality which was causing Windows 10 testers to turn it off.

 

So last summer, Microsoft kicked off a three-month survey to find out why people were disabling the search indexer (the engine that drives Windows Search, pre-cataloguing information to make for speedier searching).

 

Microsoft notes it discovered that the main reasons by far were “excessive disk usage” and “performance issues”, along with a perceived lack of value. “Excessive CPU usage” was also mentioned as the sixth most bothersome problem.

Throttling back

And so Microsoft introduced a new algorithm to detect excessive disk usage and other performance issues, and if found, Windows 10 was given the ability to throttle (or indeed completely stop) any search indexing activity to prevent such slowdowns from occurring.

 

This algorithm has been developed down the line, and Microsoft says it has been continuing to work on curing these performance issues while developing the Windows 10 update for 20H1.

 

In a blog post for the new build 19025, Microsoft notes: “Based on [feedback from May 2019 Update testers], we’re introducing an algorithm that detects high disk usage and activity, so it can better identify peak usage times and manage the indexer accordingly. We’re also making changes for developers to prevent searches of certain repositories and project folders to improve disk usage.”

 

It sounds like this is very much an ongoing process, but the end goal is that any such performance problems will hopefully all be banished with the Windows 10 update for the first half of 2020.

 

Remember that this 20H1 update is expected to be finalized as soon as next month, so anyone still suffering at the hands of Windows Search induced sluggishness on their PC could get a remedy very soon (which doesn’t involve turning off the indexer). Indeed, there are even some whispers that 20H1 could be deployed as soon as January 2020.

 

Meanwhile, Microsoft also observes that it continues to improve Windows 10 search in other ways, to boost the overall perception of the service (tackling that perceived lack of value bugbear), with measures including Enhanced search mode.

 

And some nifty further measures are planned to make Windows Search more intelligent in the 20H1 update as we’ve seen previously.

 

 

Source: Windows 10 search fix will stop it sometimes hogging disk or CPU resources (TechRadar)