KB5073722: Overview with user sentiment and feedback

Overview

This security update for Windows Server 2016 and Windows 10 Enterprise LTSB 2016 includes several fixes and improvements. It addresses a security hardening behavior that restricts certain applications from autofilling credentials during remote support sessions or automated authentication workflows. The update also removes several modem drivers and fixes a vulnerability in the WinSqlite3.dll component. While there are no known issues with this update, users should be aware of the upcoming expiration of Secure Boot certificates and the end of support for Windows Server 2016 and Windows 10 Enterprise LTSB 2016 in the coming years.

General Purpose

The key changes in this KB5073722 update include:- Security hardening to restrict certain applications from autofilling credentials during remote support or automated authentication workflows. This change prevents credential dialogs from responding to virtual keyboard input from remote desktop or screen sharing tools.- Removal of several modem drivers (agrsm64.sys, agrsm.sys, smserl64.sys, smserial.sys) which will impact modem hardware dependent on those drivers.- An update to the WinSqlite3.dll component to address a previously detected security vulnerability. Note this is separate from the sqlite3.dll component found in application directories.This update is part of the cumulative updates released in December 2025 (KB5071543) and December 2025 (KB5074974). Users should ensure they have the latest Servicing Stack Update (KB5073447) installed prior to applying this patch.

General Sentiment

Overall, this update appears to address some important security and stability issues for Windows Server 2016 and Windows 10 Enterprise LTSB 2016 users. The changes around credential autofill and modem driver removal may cause some disruption for certain users, but Microsoft has provided guidance on mitigating these impacts.The lack of any known issues with this update is a positive sign, though users should still be aware of the upcoming Secure Boot certificate expiration and end of support deadlines for these older Windows versions. As with any security update, it's recommended to test the update in a non-production environment before deploying broadly, to ensure compatibility with existing applications and workflows.

Known Issues

• None reported

Disclaimer: We take measures to ensure that AI-generated content is of the highest possible quality, but we cannot guarantee its accuracy and recommend that users do their own independent research. Generated on 2026-02-28 07:19 PM

Back to Knowledge Base Catalog