Install KB4503267 to fix Windows Hello authentication issues

Milan Stanojevic
by Milan Stanojevic
Deputy Editor
1 Comments
Download PDF

Download KB4503267

Cumulative update KB4503267 is now available for download on PCs running Windows 10 v1607. This June 2019 Patch Tuesday update bumps Windows 10 to build version 14393.3025.

Apart from the security updates for Edge, and other Windows Components, KB4503267 fixes some annoying authentication issues affecting Windows Hello. 

Unlike the other Patch Tuesday updates released this month, KB4503267 brings a bundle of known issues. Microsoft says that they are working to fix all of them.

However, you need to wait until the next release to get rid of all these issues. 

And now let’s quickly review some of the key changes and fixes included in KB4503267.

KB4503267 improvements and fixes

Authentication issues fixed

Microsoft addressed an issue with Windows Hello for Business that triggered authentication issues. The issue affected the program when Server Core was installed on Windows Server 2016.

Device startup bug resolved

KB4503267 resolved a bug that caused premature termination of your connection to the WDS server. The issue basically trigged because the Preboot Execution Environment (PXE) failed to start a device from the WDS server.

Internet Explorer 11 launch issues fixed

Internet Explorer 11 is often affected by bugs and issues. The previous cumulative update introduced a new bug in IE11 but KB4467684 fixed the problem.

Alternatively, if you’re tired of IE’s limitations, you can switch to a new browser. If you’re looking for a fast, privacy-focused browser, then UR Browser is the right choice for you.

Editor's recommendation
ur browser
  • Fast page loading
  • VPN-level privacy
  • Enhanced security
  • Built-in virus scanner

KB4503267 known issues

Cumulative update KB4503267 is affected by some issues of its own. For example, the cluster service may sometimes fail to launch.

The big M says that the problem occurs if you have used more than 14 characters to configure the group policy setting for Minimum Password Length. 

You can visit Microsoft’s support page to check out all the known issues.

  • My current home lab is setup for an SCCM 1902 environment.

    It has 3 Servers – all are 2016 Standard x64
    1 is AD, DHCP, IIS and DNS – updated fine
    2 is SCCM with IIS, WDS, WSUS – updated fine
    3 is SQL Server 2016 – showed as installed

    But Windows updates insisted it still needed to be downloaded and installed. So I manually uninstalled just KB4503267.

    Grabbed the update off of Windows Update Catalog Server,

    Manually installed it. Crossing fingers (very big, very slow 1.4 Gig update) hoping it will work. And it worked!

    My systems update off of WSUS and SCCM which is unique. Most users get their updates from MS servers.

    So mine may be a fluke problem, but the fix is a manual update for KB4503267. AND only on the SQL Server.

    Hopes this helps someone.