News

Microsoft Releases Windows 10 20H1 Build 18995

Microsoft today released Windows 10 18995 to Insiders in the Fast ring. It includes new login and Your Phone app features. Here’s what you can expect in today’s latest build.

Microsoft today released Windows 10 20H1 preview build 18995 to Insiders in the Fast ring. This is the follow up to last week’s build 18990 which was light on new features but contains a ton of fixes. Today’s build introduces a new Windows Hello PIN Safe mode, improvements to the Your Phone app, and a lengthy list of other overall system changes and improvements.

Windows 10 20H1 Preview Build 18995

This build is introducing Windows Hello PIN in Safe Mode. Booting into Safe Mode only launches the minimum files and drivers to get Windows and your system running. It’s a great troubleshooting tool. And with 18995 Microsoft is “adding Windows Hello PIN sign-in support to Safe mode, so that you no longer have to rely on your password when troubleshooting your device.”

The Your Phone app is gaining new features including the Link to Windows, Phone Screen, and Battery Level Indicator. It’s rolling out to Samsung Galaxy S10, S10+, S10e, S10 5G, and Fold devices in select markets. Microsoft says the new features will gradually roll out to all users as the testing continues.

In addition to the improvements listed above, here is the list of other changes and fixes to expect in today’s build:

  • We’ve made some improvements to address an issue resulting in some users frequently seeing a notification saying their account needed to be fixed, but the Settings page that opened showed no action was necessary.
  • We fixed an issue resulting in some Insiders seeing error 0x80242016 when trying to upgrade.
  • We fixed an issue where you might be prompted to fix something before you could update, but the dialog with what to fix didn’t display the issue that needed fixing.
  • We fixed an issue resulting in the mouse cursor unexpectedly showing up in screenshots in recent builds.
  • We fixed an issue impacting reliability of taking screenshots with WIN+Shift+S / Snip & Sketch.
  • We fixed an issue where, if you started a snip from Snip & Sketch by pressing New and had “automatically copy to clipboard” enabled, the first initial copy might be blank.
  • We fixed an issue where the Action Center might be visible in screenshots recently if you started them by pressing the Screen Snip quick action.
  • We fixed an issue for multi-mon devices that could cause random crashes in UWP apps when switching focus between monitors.
  • We fixed a high hitting DWM crash from the last few flights.
  • We fixed an issue in recent flights that resulted in Skype unexpectedly closing the first time it was launched and you tried to sign in.
  • We’ve updated our File Explorer context menu logic, so if you right-click on a .HEIC image file, you’ll now have the option to Print or Set as Desktop Background, as you can with other image file types.
  • We fixed an issue where you might need to invoke the File Explorer context menu twice before the option to create a new Text Document would appear.
  • We’ve made some improvements to help address an issue where search may appear blank.
  • We fixed an issue resulting in some users seeing a 0x000007D1 when trying to print.
  • We fixed an issue where the publisher information was unexpectedly blank for some apps in App Settings.
  • We fixed an issue where the Windows Update information in the Settings header could be out of date.
  • We fixed an issue where turning Bluetooth off then back on while a Bluetooth audio device was paired could take an unexpectedly long time.
  • We fixed a crash when adding devices in Devices Settings.
  • We fixed an issue where the ImmGetVirtualKey function wasn’t returning VK_PROCESSKEY even if an IME was enabled.
  • We fixed an issue where pressing space to enter selected word with the Changjie IME when using the touch keyboard might not work.
  • We fixed a ctfmon.exe crash when using the Japanese IME if reconversion was triggered with a partial selection.
  • We fixed an issue where ctfmon.exe would crash if you attempted to use dictation from the touch keyboard in certain apps.
  • We fixed an issue impacting Windows Ink Workspace reliability.
  • We fixed an issue that could result in pinned websites icons in the taskbar sometimes unexpectedly switching from their actual icon to the default browser icon.
  • We fixed an issue where calendar events created from the taskbar clock and calendar flyout wouldn’t have a default 15min reminder set.
  • We fixed an issue where if the taskbar changed scale enough times while an IME was active, it would lead to the input indicator disappearing from the taskbar.
  • We fixed an issue resulting in transparent/invisible app thumbnails in snap assist when snapping an app to the side when in tablet mode.
  • We fixed an issue where Task View would display that the navigation pane of certain apps was expanded, even if it was actually collapsed.
  • We’ve improved Magnifier performance when using touch.
  • We’ve updated our logic, Magnifier UI will now show properly when alt-tabbing if Magnifier was minimized originally.
  • We’ve fixed a few small issues with the Text cursor indicator page in Settings.
  • We fixed an issue where, when using the text cursor indicator, you might unexpectedly see a focusable Eoaexperiences.exe app running in the taskbar.
  • We’ve improved the reading of email when objects such as images are embedded in the message while using Narrator to remove the repeating of information while moving through the content.
  • We fixed a bug in Narrator where the link sound did not play in certain scenarios.
  • We fixed an issue with older drivers showing as available for download. If you continue to see older drivers in the Option updates section of Windows Update, please let us know.

Windows 10 20H1 is an Insider build that will include the feature the updates we expect to see next Spring. And, as always, remember that with Insider builds you can expect a lot of bugs, instability, and other issues for both users and developers. Make sure to read Microsoft’s full blog post for all changes, known issues, and workarounds.


Click to comment
To Top