Excel and Power BI Windows Authentication Fails After November 2026 Windows Update (Installer-based AtScale)
Summary
Microsoft's November 10, 2026 Windows update changes how Windows PCs send NTLM credentials. After the update, Excel and Power BI users may be unable to sign in with Windows Authentication to installer-based AtScale servers that use NTLM authentication. A client-side registry setting restores sign-in, and Kerberos over XMLA avoids the issue entirely. Container-based AtScale is not affected.
Applies to|
Configuration |
Affected |
|---|---|
|
Installer-based AtScale, NTLM authentication, Excel or Power BI clients |
Yes |
|
LDAP with SSL disabled |
No |
|
LDAPS (LDAP over SSL) |
No |
|
Netlogon |
No |
|
Kerberos over XMLA |
No |
|
Container-based AtScale |
No |
Only client PCs that have received the Microsoft update are affected. Connections that use a username and password keep working.
Symptoms
Users who previously signed in with Windows Authentication see one of these errors:
- Excel: "Unable to connect to data source. Reason: Access denied. You either made a mistake typing in your User ID and/or Password…"
- Excel, refreshing an existing connection: "Initialization of the data source failed."
- Power BI Desktop: "Unable to connect…"
The AtScale engine log shows:
NTLM Type3 Bind failed Error while trying to authorize NTLM against LDAP: 00002029: LdapErr: ... Cannot bind using sign/seal on a connection on which TLS or SSL is in effectCause
Microsoft KB5135557, "NTLM signing security improvements in Windows," makes Windows clients offer NTLM message signing by default on every non-anonymous connection. On Windows 11 it ships in the November cumulative update, KB5132061.
When AtScale passes the signed NTLM credentials to LDAP over a TLS/SSL connection, the directory rejects the bind, so authentication fails.
Workaround
Set a registry value on each affected client PC so Windows stops offering NTLM signing. In AtScale's testing, this restored Windows Authentication immediately. No AtScale or Windows Server setting resolves the issue, so the change must be made on the client PCs.
- Have your Windows or security team review Microsoft KB5135557 before deploying. Microsoft is the authoritative source on the security trade-off.
- Run the following command on each affected PC as an administrator, or deploy the same value with Group Policy or Intune:
reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 /v ClientAllowUnsignedNtlm /t REG_DWORD /d 1 /f
- Have the user reconnect from Excel or Power BI.
Important: Microsoft describes this as a temporary compatibility setting. The KB outlines a later phase in which Windows servers will require NTLM signing, so plan a move to the long-term solution below.
Long-term solution: Kerberos over XMLA
AtScale supports Kerberos authentication for XMLA connections from Excel and Power BI, and Kerberos over XMLA is not affected by this change. For setup steps, see Kerberos Connections to XMLA endpoints.
Getting help
To plan a move to Kerberos, open a support ticket at help.atscale.com and AtScale Technical Support will schedule time to review it with you.