Fix empty path handling for Windows PowerShell adapter #1097
Conversation
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
SteveL-MSFT
requested changes
Sep 7, 2025
SteveL-MSFT
requested changes
Sep 8, 2025
Gijsreyn
force-pushed
the
gh-1095/main/fix-empty-winpspath-handling
branch
from
8cde7cf to
e49334d
Compare
SteveL-MSFT
approved these changes
Sep 9, 2025
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.
PR Summary
This pull request addresses an issue when
$env:PSModulePathcontains empty entries, the PSDesiredStateConfiguration v1.1 module errors out and returns empty results.Rather than the suggestion in the fixed issue, a reset should always happen because of the line 158 and 170
PR Context
Fix #1095