Skip to content

Commit 81640bb

Browse files
authored
Merge pull request #7957 from kupdates/docs-editor/cached-user-logon-fails-lsasrv-1735670659
AB#3249: Update cached-user-logon-fails-lsasrv-event-45058.md
2 parents e5fa091 + f926d76 commit 81640bb

1 file changed

Lines changed: 8 additions & 8 deletions

File tree

support/windows-client/user-profiles-and-logon/cached-user-logon-fails-lsasrv-event-45058.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Cached user logon fails with LSASRV event 45058
3-
description: Fixes an issue that occurs when logging on to a domain-joined Windows Vista or Windows 7 computer using cached credentials.
4-
ms.date: 12/26/2023
3+
description: Fixes an issue that occurs when logging on to a domain-joined Windows computer using cached credentials.
4+
ms.date: 01/02/2025
55
manager: dcscontentpm
66
audience: itpro
77
ms.topic: troubleshooting
@@ -10,16 +10,16 @@ ms.custom: sap:User Logon and Profiles\Service Account and Interactive User Logo
1010
---
1111
# Cached user logon fails when LSASRV event 45058 indicates FIFO deletion of cached credential
1212

13-
This article fixes a logon failure that occurs when logging on to a domain-joined Windows Vista or Windows 7 computer using cached credentials.
13+
This article fixes a logon failure that occurs when logging on to a domain-joined Windows computer using cached credentials.
1414

15-
_Applies to:_   Windows 7 Service Pack 1
15+
_Applies to:_   Windows 10, Windows 11, Windows Server 2016, Windows Server 2019, Windows Server 2022, Windows Server 2025
1616
_Original KB number:_   2555663
1717

1818
## Symptoms
1919

20-
1. Users receive the following error when logging on to a domain-joined Windows Vista or Windows 7 computer using cached credentials:
20+
1. Users receive the following error when logging on to a domain-joined Windows computer using cached credentials:
2121

22-
> There are currently no logon servers available to service the logon request.
22+
> There are currently no logon servers available to service the logon request.
2323
2424
2. LsaSrv Event 45058, logged in the System event log of a domain-joined workstation, indicates that the operating system has deleted the cached credential for the user specified in the event:
2525

@@ -39,7 +39,7 @@ _Original KB number:_   2555663
3939

4040
The user logon error occurs when a user's cached credentials have been purged from the local computer by more recent domain user logons.
4141

42-
Windows Vista and Windows 7 operating systems cache credentials for a finite number of user accounts (assuming cached credentials haven't been disabled).
42+
Windows operating systems cache credentials for a finite number of user accounts (assuming cached credentials haven't been disabled).
4343

4444
Once the cached logon quota has been reached, the operating system will purge the oldest cached credential from the local computer so that the credentials for the next unique domain user successfully authenticated by a domain controller may be cached. The logging of the LsaSrv 45058 event indicates that the cached logon quota has been reached, triggering the deletion of the oldest user credential cached on the local machine.
4545

@@ -72,6 +72,6 @@ Cached credentials can also be managed with group policy by configuring:
7272

7373
Group Policy Setting path: Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options.
7474

75-
Group Policy Setting: Interactive logon: Number of previous logons to cache (in case domain controller is not available)
75+
[Group Policy Setting: Interactive logon: Number of previous logons to cache (in case domain controller is not available)](/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/interactive-logon-number-of-previous-logons-to-cache-in-case-domain-controller-is-not-available)
7676

7777
The workstation the user needs access to must have physical connectivity with the domain and the user must authenticate with a domain controller to cache their credentials again.

0 commit comments

Comments
 (0)