Take Windows Up to 11

Category: Windows Hello

Windows 10 20H2 nice to know for me and IT Pros and Enterprise admins (curated link list)

Latest Update: January 13, 2020

Windows 10 20H2 is again a small fall release with a long support cycle of 30 months. It shares a lot with the spring release (NTK 2004) so check out my list for this release, too.
If you found something new before me or if I missed anything important, please send me a message via Twitter.

General

Topic Link Source
What’s new for IT Pros New and Updated Features of interest for IT Pros Microsoft
What’s new What’s new in Windows 10, version 2004 Microsoft
Release Status Known issues and notifications Microsoft
Removed features Features and functionality removed in Windows 10 Microsoft
Connection Endpoints Manage connection endpoints for Windows 10 Enterprise, version 20H2 Microsoft

Group Policies

Topic Link Source
WMI Filter Select Version,ProductType from Win32_OperatingSystem WHERE Version LIKE "10.0.19042%" and ProductType = "1" Sascha Stumpler
ADMX ADMX files for 20H2 Microsoft
Baseline (DRAFT) Security Baseline (DRAFT) for Windows 10 20H2 Microsoft
Baseline (FINAL) Security Baseline (FINAL) for Windows 10 20H2 Microsoft
Baseline Download Security Compliance Toolkit Microsoft

Autopilot, OSD, MEMCM, Intune and MDT

Topic Link Source
MDM What’s new in mobile device enrollment and management Microsoft
MDM-CSP Policy CSP – LocalUsersAndGroups Microsoft
LCU+SSU Combined Servicing Stack and Cumulative Updates Microsoft
Renamed BUILTIN Accounts Windows 10 2004/20H2 and renamed Administrator accounts are recreated Michael Niehaus

Misc

Topic Link Source
Important Issues Knowledgebase: Important Issues for Windows 10, version 20H2 build 19042 DirTeam, Sander Berkouwer
MMC error After updating to Windows 10, version 20H2, you might receive an error when accessing the sign-in options or users MMC snap-in Microsoft

Windows 10 2004 nice to know for me and IT Pros and Enterprise admins (curated link list)

Latest Update: January 13, 2020

Windows 10 2004 is the first big release since 1903 (NTK 1903) and compared to the small update of Windows 10 1909 (NTK 1909) this brings a lot of changes.
If you found something new before me or if I missed anything important please write a comment or send me a message via Twitter.

General

Topic Link Source
What’s new for IT Pros New and Updated Features of interest for IT Pros Microsoft
What’s new What’s new in Windows 10, version 2004 Microsoft
Release Status Known issues and notifications Microsoft
Removed features Features and functionality removed in Windows 10 Microsoft
Connection Endpoints Manage connection endpoints for Windows 10 Enterprise, version 2004 Microsoft

Group Policies

Topic Link Source
WMI Filter Select Version,ProductType from Win32_OperatingSystem WHERE Version LIKE "10.0.19041%" and ProductType = "1" Sascha Stumpler
New settings 17 new ADMX settings Jörgen Nilsson
ADMX ADMX files for 2004 Microsoft
Baseline (DRAFT) Security Baseline (DRAFT) for Windows 10 2004 Microsoft
Baseline (FINAL) Security Baseline (FINAL) for Windows 10 2004 Microsoft
Baseline Download Security Compliance Toolkit Microsoft

Autopilot, OSD, MEMCM, Intune and MDT

Topic Link Source
Autopilot Autopilot features in 2004 Michael Niehaus
MDT BIOS Making MDT work with Windows ADK 2004 for BIOS Machines Johan Arwidmark
MDT Hotfix Windows 10 deployments fail with MDT on computers with BIOS type firmware Microsoft
Servicing New custom actions during and after a feature update Microsoft
Dynamic Update New switches to exclude Drivers and Cumulative Updates Microsoft
New MDM What’s new in MDM for Windows 10, version 2004 Microsoft
MUI Better Language Handling Michael Niehaus
MDT Updates OSD MDT and installing updates during a task sequence Michael Niehaus
Renamed BUILTIN Accounts Windows 10 2004/20H2 and renamed Administrator accounts are recreated Michael Niehaus

Windows Subsystem for Linux 2 aka WSL2

Topic Link Source
Cool WSL tips Cool WSL (Windows Subsystem for Linux) tips and tricks you (or I) didn’t know were possible Scott Hanselman
Docker in WSL2 How to set up Docker within Windows System for Linux (WSL2) on Windows 10 Scott Hanselman
Remote debugging Remote Debugging a .NET Core Linux app in WSL2 from Visual Studio on Windows Scott Hanselman
Update to WSL2 Manually update Linux Kernel to WSL2 Craig Loewen, MS
Access WSL VHDX Access WSL2 .vhdx on External Drive Within a Windows 10 System Image Ed Burns

Misc

Topic Link Source
MSIX MSIX Installation possible without Sideloading Microsoft
Upgrade HVCI Update to Windows 10, version 2004 might encounter an update compatibility hold due to HVCI Microsoft
Wifi 2004 supports Wi-Fi 6 and WPA3 Microsoft
Identity Identity-related Features in Windows 10 version 2004 DirTeam.com
Reset Reset PC from the cloud Microsoft
Reserved Storage DISM Reserved Storage Command-line Options Microsoft
Notepad Notepad enhancements in Windows 10 2004 Microsoft
VMware Workstation VMware Workstation 15.5.5 supports Hyper-V and therefor Credential Guard and WSL on the hosting system VMware
VMware Workstation VMware Workstation and Hyper-V Microsoft
Citrix Issues Citrix Known Issues with 20H1 Insider Preview including a problem with ICA connections Citrix
OneDrive Issues using OneDrive On-Demand after updating to 2004 Microsoft
AppX the list of removeable apps did not change
Windows 10 1903 Built-In Apps: What to Keep
Anton Romanyuk, Microsoft

“Something went wrong” error when enabling Windows 10 facial authentication

Problem

When I was at a customer’s site lately and tried to enable the Windows Hello face recognition feature I encountered an error. After pressing the Get started button on the Windows Hello setup page Sorry, something went wrong was displayed without further explanations.

Windows Hello Setup
Windows Hello Setup Error

When I checked the Windows Event Log I could find a DistributedCOM error with the EventID 10016 which stated that the application did not have the local activation permission for the COM application.

Windows eventlog error DCOM

After that I looked up the APPID from the event in the Component Services and found out that it was the RuntimeBroker which controls the execution of the AppX(Universial)-Apps. Thinking about that I remembered that we had limited the access to the camera to certain AppX-Apps via Group Policy.

Component Services

I opened regedit as an Administrator and removed the value

HKLM:\Software\Policies\Microsoft\Windows\AppPrivacy!LetAppsAccessCamera

and tested again. Then it worked! So I just needed to find out which AppX needs access to the camera. I looked up the installed AppX with the PowerShell command:

Get-AppxPackage | select Name | sort

There it was the Microsoft.BioEnrollment_cw5n1h2txyewy AppX which looked like the app I was searching for. I reset my registry changes with a Group Policy update and added the AppX name to the value of:

HKLM:\Software\Policies\Microsoft\Windows\AppPrivacy!LetAppsAccessCamera_UserInControlOfTheseApps

Registry privacy camera

After that I tested again and it still worked to setup the facial recognition.

Camera working

Solution

Adding the AppX Microsoft.BioEnrollment_cw5n1h2txyewy to the Put user in control of these specific apps or the Force allow these specific apps fields of the Let Windows apps access the camera setting in the GPO under Computer Settings\Administrative Templates\Windows Components\App Privacy resolved the issue and users are able to use their face to authenticate on Windows.

GPO settings camera privacy