KB5021237

After installing KB5001342 or later, the Cluster Service might fail to start because a Cluster Network Driver is not found.

This issue occurs because of an update to the PnP class drivers used by this service.  After about 20 minutes, you should be able to restart your device and not encounter this issue.
For more information about the specific errors, cause, and workaround for this issue, please see KB5003571.

After installing this update, apps that use ODBC connections utilizing the Microsoft ODBC SQL Server Driver (sqlsrv32.dll) to access databases might fail to connect. You might receive an error within the app or you might receive an error from SQL Server, such as "The EMS System encountered a problem" with "Message: [Microsoft][ODBC SQL Server Driver] Protocol error in TDS Stream" or "Message: [Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server".

Note for developers Apps affected by this issue might fail to fetch data, for example when using the SQLFetch function. This issue might occur when calling SQLBindCol function before SQLFetch or calling SQLGetData function after SQLFetch and when a value of 0 (zero) is given for the ‘BufferLength’ argument for fixed datatypes larger then 4 bytes (such as SQL_C_FLOAT).

If you are unsure if you are using any affected apps, open any apps which use a database and then open Command Prompt (select Start then type command prompt and select it) and type the following command:  

tasklist /m sqlsrv32.dll

This issue is addressed in KB5022286.

After installing this update on Hyper-V hosts managed by SDN configured System Center Virtual Machine Manager (VMM), you might receive an error on workflows involving creating a new Network Adapter (also called a Network Interface Card or NIC) joined to a VM network or a new Virtual Machine (VM) with a Network Adapter joined to a VM network. Existing VMs with existing Network Adapters should not have issues connecting after installing this update, only new Network Adapters created after installation of this update are affected.

When experiencing this issue, you might receive one of the following errors:

• When creating a new VM or a new network adapter on an existing VM, you might receive, "<vmName> failed to modify device 'Ethernet Connection"

• Software defined networking (SDN) software load balancer service might fail, and you might receive, "<SLBVMName> failed to modify device 'Ethernet Connection' error"

• SDN RAS Gateway service might fail, and you might receive, "<GatewayVMName> failed to modify device 'Ethernet Connection' error"

This issue is addressed in KB5022554.