updated LKGC script v1.3

[anmocanu]

This script enables Last Known Good Configuration (LKGC) by incrementing registry values for recovery from boot issues. It includes enhancements for logging and error handling, ensuring proper execution and tracking of applied changes. This update enhances the win-LKGC.ps1 script to increment Last Known Good Configuration (LKGC) registry values, log changes, and ensure proper handling of nested VMs. It includes improved error handling, logging, and a new mechanism to track whether LKGC was applied on any disk. .VERSION
v1.3: [May 2026] - Updated the script (current)
- Added LKGC_APPLIED log flag (per disk + overall) and corrected final summary message.
- Fixed Get-VM crash when Hyper-V module is not installed on host (guarded Get-VM).
- Fixed false "already set" detection by requiring ALL thresholds (AND instead of OR).
v1.1: Previous version
v0.1: Initial commit

[EdwinBernal1]

Issues Found

🟢 Minor: OS version parsing is heuristic-based

The script derives $winosver from first numeric token in ProductName. This is pragmatic but brittle if naming format changes.

Recommendation: consider reading a stable version key (e.g., CurrentMajorVersionNumber / CurrentBuild) when available.

[EdwinBernal1]

@anmocanu could you help us with the review of these findings

Findings

Critical

File	Context	Issue	Recommendation
—	—	None	—

Warning

File	Context	Issue	Recommendation
win-LKGC.ps1	version number	PR title says v1.3, but the top .VERSION entry in the file is v1.4 ("Production hardening").	Reconcile the version in the title/history so it is unambiguous.
win-LKGC.ps1	Log-* wrapper	Logging-wrapper pattern duplicated across the batch.	Extract shared helper.

Info

File	Context	Suggestion
win-LKGC.ps1	backup + rollback	SYSTEM hive backup with restore-on-failure is the strongest safety pattern in the batch. Good.
win-LKGC.ps1	AND-logic fix	The OR→AND change is a genuine bug fix; verify the version-specific thresholds (Win10/2016+ vs 2012) match intended LKGC semantics.
win-LKGC.ps1	unload retry	Pre-load defensive reg unload, plus 3× unload retry with GC — reduces stuck-hive risk on detach.

Operational Risk Assessment

Factor	Rating	Notes
Scope	Low-Medium	Single script; registry hive load/modify/unload.
Destructive ops	Low-Medium	Registry Select edits — but backed up and rolled back on failure.
Rollback possible	Yes	Per-disk SYSTEM hive backup + automatic restore on failure.
Testing documented	Unknown	Confirm test evidence in the PR.
Gen compatibility	Gen1+Gen2	Operates on the lettered Windows volume; generation-agnostic.