Microsoft releases Windows 10 20H1 Build 18995 with new sign-in option and Windows Subsystem for Linux (WSL) updates

Microsoft will begin rolling out the Windows 10 19H2 update very soon, but in the meantime it’s working hard on the next big feature release -- the May 2020 Update, due out next spring.

Fresh from its big hardware event yesterday, the software giant today rolls out a new flight to Fast ring Insiders. Build 18995 introduces a number of new features, including adding Windows Hello PIN sign-in support to Safe mode, and yet more improvements for Windows Subsystem for Linux (WSL).

Safe mode can come in very handy when troubleshooting issues in Windows, and now you can use a Windows Hello PIN to sign you in. To set this up follow these instructions:

• Set up Windows Hello in Settings > Accounts > Sign-in options
• Boot your device into Safe mode:
  • Settings > Update and Security > Recovery
  • Under Advanced startup select Restart now
  • After your PC restarts to the Choose an option screen, select Troubleshoot > Advanced options > Startup Settings > Restart. You may be asked to enter your BitLocker recovery key.
  • After your PC restarts, you’ll see a list of options. Select 4 or press F4 to start your PC in Safe Mode. You can also select 5 or press F5 to use Safe Mode with Networking.
• Sign in to your device with your Windows Hello PIN

This new build also fixes a number of problems with Windows Subsystem for Linux (WSL). New features are being rolled out for the Your Phone app too. You can read more about that here.

Other changes, improvements, and fixes in this build include:

• Microsoft has 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.
• Fixed an issue resulting in some Insiders seeing error 0x80242016 when trying to upgrade.
• 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.
• Fixed an issue resulting in the mouse cursor unexpectedly showing up in screenshots in recent builds.
• Fixed an issue impacting reliability of taking screenshots with WIN+Shift+S / Snip & Sketch.
• 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.
• Fixed an issue where the Action Center might be visible in screenshots recently if you started them by pressing the Screen Snip quick action.
• Fixed an issue for multi-mon devices that could cause random crashes in UWP apps when switching focus between monitors.
• Fixed a high hitting DWM crash from the last few flights.
• Fixed an issue in recent flights that resulted in Skype unexpectedly closing the first time it was launched and you tried to sign in.
• Microsoft has updated its 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.
• 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.
• Microsoft has made some improvements to help address an issue where search may appear blank.
• Fixed an issue resulting in some users seeing a 0x000007D1 when trying to print.
• Fixed an issue where the publisher information was unexpectedly blank for some apps in App Settings.
• Fixed an issue where the Windows Update information in the Settings header could be out of date.
• Fixed an issue where turning Bluetooth off then back on while a Bluetooth audio device was paired could take an unexpectedly long time.
• Fixed a crash when adding devices in Devices Settings.
• Fixed an issue where the ImmGetVirtualKey function wasn’t returning VK_PROCESSKEY even if an IME was enabled.
• Fixed an issue where pressing space to enter selected word with the Changjie IME when using the touch keyboard might not work.
• Fixed a ctfmon.exe crash when using the Japanese IME if reconversion was triggered with a partial selection.
• Fixed an issue where ctfmon.exe would crash if you attempted to use dictation from the touch keyboard in certain apps.
• Fixed an issue impacting Windows Ink Workspace reliability.
• 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.
• Fixed an issue where calendar events created from the taskbar clock and calendar flyout wouldn’t have a default 15min reminder set.
• 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.
• Fixed an issue resulting in transparent/invisible app thumbnails in snap assist when snapping an app to the side when in tablet mode.
• Fixed an issue where Task View would display that the navigation pane of certain apps was expanded, even if it was actually collapsed.
• Microsoft has improved Magnifier performance when using touch.
• Microsoft has updated its logic, Magnifier UI will now show properly when alt-tabbing if Magnifier was minimized originally.
• Microsoft has fixed a few small issues with the Text cursor indicator page in Settings.
• Fixed an issue where, when using the text cursor indicator, you might unexpectedly see a focusable Eoaexperiences.exe app running in the taskbar.
• Microsoft has 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.
• Fixed a bug in Narrator where the link sound did not play in certain scenarios.
• Fixed an issue with older drivers showing as available for download.

Known issues are:

• 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. 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.
• Certain 2D apps (like Feedback Hub, Microsoft Store, 3D Viewer) are incorrectly being treated as having protected content within Windows Mixed Reality. During video capture, these 2D apps block their content from being recorded.
• When capturing a repro video while filing a bug via Feedback Hub in Windows Mixed Reality, you won’t be able to select Stop video, due to the protected content issue noted above. If you want to submit a repro video, you will need to wait 5 minutes for the recording to time out. If you’d like to file the bug without a repro video, you can close the Feedback Hub window to end the recording and resume filing your bug when you reopen the app in Feedback > Drafts.
• When using the Search bar in either Control Panel or File Explorer, the box becomes grey and prevents input. Microsoft has identified the cause, and is working on a fix for a future flight.
• Devices configured for dual scan (WSUS and Windows Update) for updates may not be offered new builds in the Fast ring. Selecting Check online for updates from Microsoft Update will scan for updates, but may return with the message, "Your device is up to date." Microsoft is working on a fix for a future flight.
• Some devices configured to Use HDR may experience a bluish tint on their HDR displays after using Night Light.
• Theme packs downloaded from the Microsoft Store fail to apply.
• Starting with the previous flight, some Insiders may find that Settings doesn’t launch from the button in Start, isn’t listed in the All apps list, or as a search result. If you are impacted, pressing WIN+R and inputting "ms-settings:" (without the quotes) will launch Settings if you need it.
• After successfully updating to a new build, the Windows Update Settings page may show the same build needs to install. You can verify the build was successfully installed by checking the build number in the corner of the screen or going to Win+R, typing winver, and confirming the build number.

Photo credit: charnsitr / Shutterstock