Windows 10 Build 19025 [20H1] Verbatim to Fast Ring

Windows 10 Build 19025 [20H1] Verbatim came to Insiders in Fast Ring with Search feature and fixes for Windows Hello authentication, ctfmon.exe crashing, Magnifier, and Narrator issues.

Microsoft has rolled out Windows 10 Build 19025 for the insiders in Fast Ring with a feature for Search and a collection of fixes. The update for Verbatim includes fixes for mainly Sandbox and WDAG, VPN, Windows Hello authentication, Magnifier, and Narrator issues. The build will be installed automatically all you need to make sure Windows update is not paused or disabled. Still, you don’t get then go to Settings > Update & Security > Windows update and click on Check for updates.

  Windows 10 Build 19025 [20H1] Verbatim to Fast Ring

Windows 10 Build 19025 [20H1]  features improvements and fixes

Update for Windows Search

As per feedback from insiders, this build introduces an algorithm to detects high disk usage and activity.  The algorithm is able to better identify peak usage times and handle the indexer accordingly. The update also brings changes for developers to stop searches of certain project folders and repositories. This is aimed to improve disk usage. See the details here.

Windows 10 Build 19025 [20H1] Verbatim changes, improvements, and fixes

  • Windows 10 Build 19025 fixed WDAG and Sandbox not working issue which was persistent from the previous flight.
  • The update fixed certain fingerprint readers that no longer works. The issue was occurring in build 19013.
  • The build fixed VPN Settings hanging problem after upgrade.
  • Windows 10 insider developers have done some work to help address certain modern User Interface components (including network and notifications flyout), scaling issues. They are too large or too small after connecting to an external monitor or remoting into the machine from a monitor with a different Dot Per Inch.
  • They solved login performance problem for certain users in recent builds.
  • The update arrives with a fix for Windows Hello authentication not working problem with certain apps in recent builds.
  • The build fixed mouse pointer not showing problem when signing in to a PC locally after remoting in.
  • Microsoft’s developers for Verbatim version 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.
  • They solved “ctfmon.exe” crashing problem which happens when using reconversion with the Japanese IME in some text fields.
  • The update fixed web activities in Timeline not opening if you had the new Microsoft Edge browser installed.
  • The current build fixed a high number of app deployment failures occurring in a short period of time. This could result in an unexpectedly large volume of disk space being used by evtx files saved under %windir%\temp.
  • Windows 10 Build 19025 [20H1] fixed some apps that was failing to update with error code 0x8007000A.
  • The update fixed jitters that occurs during using Magnifier in certain multi-monitor configurations.
  • Build solved mouse pointer didn’t start from where the viewport of Magnifier tool was if it had moved from typing.
  • The Microsoft’s developers for Windows 10 insider build fixed a problem that impacts Narrator performance reading aloud in Outlook. This takes place when switching focus from an email back to the list of emails in your inbox.
  • They settled a memory leak in EoAExperiences.exe. The problem occurred after using text cursor indicator for prolonged time.

Knowns issues

  • Microsoft and BattlEye have detected incompatibility problem because of changes in the OS between some Insider builds and certain versions of BattlEye anti-cheat software. So the tech giant has applied compatibility hold on the affected builds. Get more information here.
  • Settings cannot be launched otherwise via the URI (ms-settings:).
  • On Windows 10 Build 19025, Printer driver is displaying Available to install despite it was successfully installed using the Optional Updates field.
  • External USB 3.0 drives stop responding with error Start Code 10 or 38 after they are connected.

Source – Windows experience blog.

           

Leave a Reply

Your email address will not be published. Required fields are marked *