[release/v7.5.7] Fix checks for local user config file paths by adityapatwardhan · Pull Request #27479 · PowerShell/PowerShell

Copilot

Backport of #26269 to release/v7.5.7

Triggered by @adityapatwardhan on behalf of @SeeminglyScience

Original CL Label: CL-Engine

/cc @PowerShell/powershell-maintainers

Manual merge as co-pilot merge was incorrect.

Impact

REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.

Tooling Impact

Required tooling change
Optional tooling change (include reasoning)

Customer Impact

Customer reported
Found internally

Fixes user configuration path handling so SYSTEM uses the expected default config location and skips user config loading when the configured Documents folder resolves to an empty/whitespace path.

Regression

REQUIRED: Check exactly one box.

This is not a regression.

Testing

Cherry-pick completed onto release/v7.5.7 and conflict resolution preserved release-specific telemetry module lists while applying the config-path fix logic. The changed files match the original PR scope and the backport commit applied cleanly after resolving one conflict in Telemetry.cs.

Risk

REQUIRED: Check exactly one box.

High
Medium
Low

Change is scoped to path derivation and guard logic for user config locations. The backport keeps existing release branch behavior outside this targeted fix, minimizing regression surface.

Merge Conflicts

Resolved one conflict in src/System.Management.Automation/utils/Telemetry.cs by preserving release/v7.5.7 content and applying the intended CanSendTelemetry/telemetry.uuid path derivation update from PR #26269.