Affected versions: Windows Server 2012 R2

📖 ~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

A previously installed LCU is offered again, creating false non-compliance and unnecessary maintenance events.

Environment & Reproduction

Seen when update metadata sync is stale or package state is partially committed.

Get-HotFix | findstr /i kb
dism /online /get-packages | findstr /i rollupfix

Root Cause Analysis

Package supersedence metadata and local state diverge, so scan logic marks update as required.

Quick Triage

Compare reported KB inventory with CBS package state and WSUS approvals.

wmic qfe list brief
Get-WindowsUpdateLog -LogPath C:Tempwu-187.log

Step-by-Step Diagnosis

Identify package state transitions around install time and scan source IDs.

findstr /i /c:"state change" C:WindowsLogsCBSCBS.log
findstr /i /c:"IsInstalled" C:Tempwu-187.log
Illustrative mockup for windows-server-2012-r2 — windows_update
Same LCU repeatedly offered — Illustrative mockup — Progressive Robot

Solution — Primary Fix

Refresh update metadata, reset datastore, and run a clean detection cycle.

Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

net stop wuauserv
ren C:WindowsSoftwareDistribution SoftwareDistribution.187
net start wuauserv
usoclient StartScan
Illustrative mockup for windows-server-2012-r2 — cbs_log_analysis
Applicability state mismatch — Illustrative mockup — Progressive Robot

Solution — Alternative Approaches

Decline superseded updates in WSUS and force target group resynchronization.

wuauclt /resetauthorization /detectnow

Verification & Acceptance Criteria

Re-offer loop ends and patch appears only as Installed/NotApplicable once.

Get-HotFix | Sort-Object InstalledOn -Descending | Select -First 10

Rollback Plan

Restore old datastore folder if detection breaks after reset.

ren C:WindowsSoftwareDistribution.187 SoftwareDistribution

Prevention & Hardening

Regularly clean WSUS metadata and validate supersedence behavior in pilot rings.

wsusutil reset

Related: needed/installed mismatch, stale scan cab, SUSDB cleanup debt.

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

View all Windows Server 2012 R2 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

WSUS metadata lifecycle and client detection internals.

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.