If using customization specs (sysprep) or templates in a virtualized environment, ensure the "Generate new identity" options are used so SIDs/UUIDs are unique. We only had issues with servers running on VMware, which also had identical SIDs (due to a failure in the cloning process), after applying the KB update. Uninstalling the update helped, but what we finally did was reinstalling the VM's affected, this means using sysprep and reinstalling the OS, software etc etc. I believe this tool was used on some servers (https://www.stratesave.com/html/sidchg.html), but we did fresh installs on SQL Server clusters to avoid any issues down the road (supportability etc).
KB5065426 Security update - SQL Server Failover cluster (AlwaysOn) problems
Hi. Has anyone else experienced problems after the september KB installation on Windows Server 2025 ? We are running SQL Server 2022 in a Always-On scenario with Failover cluster on two nodes. After the installation, we are unable to connect to the cluster, Failover Cluster manager on both nodes dot not recognize the cluster and communication between sql server nodes fails with: SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. Also we see the following events in system-log: Event 6167, LSA (LsaSrv): There is a partial mismatch in the machine ID. This indicates that the ticket has either been manipulated or it belongs to a different boot session. Failing authentication. Uninstalling the KB fixes all problems.