Windows Server 2022 — Windows LAPS fails to rotate local administrator passwords — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Windows LAPS fails to rotate local administrator passwords on Windows Server 2022 disrupts operations and prevents the affected service from meeting its SLA until remediated.

Environment & Reproduction

The issue reproduces on Windows Server 2022 hosts where the security subsystem is in use, typically following configuration drift or recent updates.

Get-Module LAPS
Get-ADComputer SERVER01 -Properties msLAPS-Password

Root Cause Analysis

The defect stems from misaligned laps settings, missing prerequisites, or a corrupted state that blocks normal operation.

Quick Triage

Confirm the service is running and capture current configuration state before applying any change.

Update-LapsADSchema
Get-LapsADPassword -Identity SERVER01 -AsPlainText

Step-by-Step Diagnosis

Walk the security stack from configuration to runtime, collecting logs and counters that point at the failing component.

Get-LapsDiagnostics
Get-WinEvent -LogName 'Microsoft-Windows-LAPS/Operational' -MaxEvents 50

Solution — Primary Fix

Apply the corrected configuration and restart dependent services so the laps component re-initialises cleanly.

Set-LapsADComputerSelfPermission -Identity 'OU=Servers,DC=contoso,DC=com'
Set-LapsADReadPasswordPermission -Identity 'OU=Servers,DC=contoso,DC=com' -AllowedPrincipals 'CONTOSOLAPSReaders'
Set-LapsADPasswordExpirationTime -Identity SERVER01 -Force
Invoke-LapsPolicyProcessing

Solution — Alternative Approaches

Where the primary fix is blocked by policy or downtime windows, use the alternative configuration path or staged rollout below.

New-GPO -Name 'LAPS-Policy' | New-GPLink -Target 'OU=Servers,DC=contoso,DC=com'
Set-GPRegistryValue -Name 'LAPS-Policy' -Key 'HKLMSoftwareMicrosoftWindowsCurrentVersionLAPSConfig' -ValueName PasswordComplexity -Type DWord -Value 4

Verification & Acceptance Criteria

Confirm the service reports healthy state and end-to-end functionality succeeds against a representative workload.

Get-LapsADPassword -Identity SERVER01 -AsPlainText
Get-WinEvent -LogName 'Microsoft-Windows-LAPS/Operational' | Where Id -eq 10004

Rollback Plan

If the fix introduces regressions, revert configuration to the pre-change baseline and restart the service to restore prior behaviour.

Reset-LapsPassword
Remove-GPLink -Name 'LAPS-Policy' -Target 'OU=Servers,DC=contoso,DC=com'

Prevention & Hardening

Bake the validated laps configuration into baseline GPOs or DSC and add a monitoring check for early detection.

Set-LapsADAuditing -Identity 'OU=Servers,DC=contoso,DC=com' -AuditedPrincipals 'CONTOSODomain Admins'
Get-LapsADPassword -Identity SERVER01

Related Errors & Cross-Refs

Related: other security failures, dependent service errors, and downstream client-side symptoms.

Related tutorial: View the step-by-step tutorial for Windows Server 2022.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn documentation for Windows Server 2022 and the relevant component, plus internal runbooks.