Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | SEC_E_SECPKG_NOT_FOUND (0x80090305) | Teams crash logs, Event Viewer | |
| Affected build range | Windows 10 / Windows 11, Microsoft Teams 2.0+ | ||
| Registry key involved | HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Security Packages | Registry Editor | -> Ensure contains kerberos, msv1_0, schannel, wdigest, tspkg, pku2u |
| Relevant service/endpoint URL | |||
| Log line signature | Event IDs 36871, 36874 in Windows Logs > System | Event Viewer |
Log Files to Check
%appdata%\Microsoft\Teams\logs.txt%windir%\System32\winevt\Logs\Security.evtx
What This Error Actually Means
The error code 0x80090305, formally known as SEC_E_SECPKG_NOT_FOUND, is a critical authentication failure originating from the Windows Security Support Provider Interface (SSPI). When Microsoft Teams encounters this error during startup or sign-in, it indicates that the client application attempted to negotiate a security context with the Azure Active Directory (now Microsoft Entra ID) service but failed because the underlying cryptographic provider required for that negotiation is missing, disabled, or corrupted on the local endpoint. Specifically, this points to a breakdown in the Kerberos or NTLM authentication handshake managed by the Local Security Authority Subsystem Service (lsass.exe). The Teams client relies heavily on Windows integrated authentication to obtain and refresh access tokens; when the requested security package—typically kerberos or msv1_0—is not registered in the LSA registry hive, the token generation process aborts immediately. This is not a network connectivity issue nor a credential error; it is a fundamental OS-level cryptographic failure that prevents the Teams client from establishing a trusted identity session with Microsoft 365 services.
Affected Versions and Scope
This issue predominantly affects endpoints running Windows 10 (versions 1909 and later) and Windows 11, specifically when utilizing the new Microsoft Teams client (version 2.0+). The legacy "Teams classic" client was less susceptible to this specific LSA dependency due to different authentication libraries, but the modern Electron-based client tightly integrates with Windows Credential Manager and SSPI. The scope of impact is usually isolated to individual devices or specific organizational units where aggressive Group Policy Objects (GPOs) or third-party endpoint security solutions have modified the default LSA configuration. It does not affect web-based Teams usage in Edge or Chrome, as those browsers utilize their own credential stores and TLS handshakes independent of the local Windows LSA security packages. However, any device enrolled in Intune with custom compliance policies that restrict cryptographic providers may trigger this state. Administrators should note that this error is often seen in environments where "Protected Users" security group membership is enforced without corresponding adjustments to NTLM fallback settings, as Teams requires specific authentication flexibility for hybrid cloud scenarios.
Where To Look First: Logs and Event IDs
To diagnose 0x80090305, you must correlate client-side application logs with system-level security events. Begin by examining the Teams crash logs located at %appdata%\Microsoft\Teams\logs.txt. Search this file for the literal string SEC_E_SECPKG_NOT_FOUND. You will likely see a stack trace indicating a failure in the AcquireCredentialsHandle or InitializeSecurityContext API calls. Concurrently, open Windows Event Viewer and navigate to Windows Logs > System. Look for Event ID 36871, which indicates that a security package failed to load, or Event ID 36874, which signals that the LSA service encountered an error while initializing security packages. Additionally, check %windir%\System32\winevt\Logs\Security.evtx for audit failures related to Kerberos pre-authentication. If you see repeated Event ID 4625 (Logon Failure) with sub-status codes pointing to cryptographic mismatches immediately preceding the Teams crash, this confirms the LSA is rejecting the authentication request due to missing providers.
Root Causes
Corrupted or Missing LSA Security Packages
The most common cause is a corruption in the registry key HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Security Packages. This multi-string value must contain specific entries such as kerberos, msv1_0, schannel, and wdigest. If a third-party tool or a misconfigured GPO removes these entries, the LSA cannot load the necessary DLLs to process authentication requests. You can verify this by checking if the value exists and contains the expected packages. If kerberos is missing, Teams will fail with 0x80090305 because it cannot negotiate a Kerberos ticket.
Protected Users Group Membership Conflicts
If a user account is a member of the "Protected Users" security group, Windows enforces strict authentication policies that disable NTLM and restrict Kerberos delegation. Teams often requires NTLM fallback for certain hybrid on-premises to cloud authentication flows or when connecting to legacy Skype for Business infrastructure. When this fallback is blocked by the Protected Users policy, and the primary Kerberos path fails due to network latency or DNS issues, the client throws SEC_E_SECPKG_NOT_FOUND because it cannot find a valid, permitted security package to complete the handshake.
Third-Party Endpoint Security Interference
Advanced endpoint detection and response (EDR) solutions or host-based firewalls may intercept SSPI calls. If the security software incorrectly flags the Teams process (Teams.exe) as suspicious during its attempt to access the LSA, it may block the load of the security package DLLs. This results in a false "not found" error because the package is technically present but inaccessible to the application context.
Fix Procedure
- Verify LSA Service Status: Open PowerShell as Administrator and run
sc query lsass. Ensure the state is "RUNNING". If it is stopped, attempt to restart it withnet start lsass, though this usually requires a reboot if the service is stuck. - Repair System Files: Corruption in system DLLs can cause LSA failures. Run
sfc /scannowfollowed byDISM /Online /Cleanup-Image /RestoreHealth. Reboot the machine after completion. - Validate Registry Configuration: Open Registry Editor and navigate to
HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Security Packages. Ensure the value data includeskerberos,msv1_0,schannel,wdigest,tspkg, andpku2u. If any are missing, add them manually.Warning: Modifying the LSA registry key incorrectly can prevent all users from logging into Windows. Create a system restore point before making changes. - Check User Authentication Policies: Use PowerShell to inspect the user's Teams policies. Run
Get-CsOnlineUser -Identity [email protected] | Select-Object PresencePolicy,TeamsAppPermissionPolicyto ensure no conflicting policies are applied. Additionally, check if the user is in the Protected Users group usingGet-ADPrincipalGroupMembership -Identity [email protected] | Where-Object {$_.Name -eq "Protected Users"}. - Clear Teams Cache: Close Teams completely (check Task Manager for background processes). Delete the contents of
%appdata%\Microsoft\Teams. Restart the client. - Verify Calling and Meeting Policies: If the issue persists, check if specific policies are blocking authentication methods. Run
Get-CsTeamsMeetingPolicy -Identity Global | Select-Object AllowPresenceFromTelephonyProviderto ensure telephony integration isn't forcing an unsupported auth method. Also verify calling settings withGet-CsUserCallingSettings -Identity [email protected].
Error Code Variants
| Error Code | Description | Distinguishing Factor |
|---|---|---|
0x80090305 |
SEC_E_SECPKG_NOT_FOUND | Security package (Kerberos/NTLM) missing from LSA registry or blocked by policy. |
0x8009030E |
SEC_E_TARGET_UNKNOWN | The target server (Teams service) is unknown to the client, usually a DNS or SPN issue. |
0x8009030D |
SEC_E_UNSUPPORTED_FUNCTION | The requested security function is not supported by the package, often a version mismatch. |
Verification
To confirm the fix, launch Teams and monitor the sign-in process. A successful authentication will result in no error codes in %appdata%\Microsoft\Teams\logs.txt. You should see log entries indicating successful token acquisition from login.microsoftonline.com. In Windows Event Viewer, verify that Event ID 36871 and 36874 are no longer appearing in the System log. Additionally, you can validate the user's connectivity state via the Teams Admin Center by navigating to Teams admin center > Users > [username] > Account and checking the "Status" field for active presence. For deeper insight, use the Call Quality Dashboard in the Microsoft 365 Defender portal to ensure no authentication-related call drops are recorded for this user.
Prevention
To prevent recurrence, establish a baseline configuration for LSA security packages using Group Policy or Intune Configuration Profiles. Ensure that HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Security Packages is protected by permissions that prevent unauthorized modification. Regularly audit the "Protected Users" group membership to ensure only necessary accounts are included, as this group strictly limits authentication flexibility. Furthermore, implement a monitoring alert for Event ID 36871 in your SIEM solution to detect LSA failures early. Use PowerShell scripts in scheduled tasks to periodically verify the integrity of system files using DISM /Online /Cleanup-Image /RestoreHealth. Finally, ensure that all endpoint security solutions are configured to whitelist Microsoft Teams processes from SSPI interception rules.