Add documentation for Test-WdacEnablement null reference issue#295
Open
erskinejohn wants to merge 2 commits into
Open
Add documentation for Test-WdacEnablement null reference issue#295erskinejohn wants to merge 2 commits into
erskinejohn wants to merge 2 commits into
Conversation
Document known issue with Test-WdacEnablement failing due to null reference during upgrade validation, including symptoms, resolution steps, and applicable versions.
Added a known issue regarding Test-WdacEnablement failing with a null-reference error during upgrade validation.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a new Environment Validator known-issue troubleshooting guide documenting a Test-WdacEnablement null-reference crash that can block upgrade readiness validation, with steps to identify the condition and apply a temporary workaround.
Changes:
- Adds a new known-issue markdown document describing symptoms and affected scenarios for the
Test-WdacEnablementnull-reference failure. - Provides a workaround procedure (identify GUID-named active
.cipfiles and temporarily rename them) and guidance to re-run validation. - Documents affected/fixed version ranges and includes related Microsoft Learn references.
Comment on lines
+101
to
+104
| ## Applicable Versions | ||
|
|
||
| - **Affected**: EnvironmentChecker 10.2509.0.2010 and all releases prior to 2607 | ||
| - **Fixed in**: 2607 - the fix adds a null-check so supplemental-only policy configurations no longer crash the validator |
Comment on lines
+58
to
+61
| ### Step 2: Temporarily rename the supplemental policy files | ||
|
|
||
| On **each cluster node** (not just the seed node), rename the supplemental `.cip` files so the validator no longer detects them: | ||
|
|
Comment on lines
+67
to
+71
| foreach ($file in $cipFiles) { | ||
| $backupName = $file.FullName + ".backup" | ||
| Rename-Item -Path $file.FullName -NewName $backupName | ||
| Write-Host "Renamed: $($file.Name) -> $($file.Name).backup" | ||
| } |
| @@ -0,0 +1,110 @@ | |||
| # Known Issue: Test-WdacEnablement Fails with Null-Reference Error During Upgrade Validation | |||
Collaborator
|
@erskinejohn you have some reviews to answer before this can be approved/merged. Can you please look them over? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document known issue with Test-WdacEnablement failing due to null reference during upgrade validation, including symptoms, resolution steps, and applicable versions.