Skip to content

Fix raw CLIXML progress output in diagnostic reports - #44

Merged
0x0bug merged 4 commits into
mainfrom
fix/suppress-progress-clixml
Sep 18, 2026
Merged

0x0bug merged 4 commits into
mainfrom
fix/suppress-progress-clixml

Conversation

@0x0bug

@0x0bug 0x0bug commented Sep 18, 2026

Copy link
Copy Markdown
Owner

Summary

Prevents PowerShell progress records from leaking into the report's Errors and warnings section as raw #< CLIXML / <Objs ...> data.

Cause

When diagnostic modules run in a redirected child PowerShell process, progress records produced by PowerShell/storage cmdlets can be serialized to stderr as CLIXML. The report runner currently treats stderr as ordinary text, so that serialization is copied verbatim into reports.

Fix

  • set $ProgressPreference = 'SilentlyContinue' inside the diagnostic child process before invoking a module;
  • add a process-runner regression test that emits Write-Progress and verifies normal stdout is preserved and no CLIXML leaks into ErrorLines.

Progress output is transient UI state and is not useful diagnostic evidence, so suppressing it does not remove report findings or actual warning/error output.

@0x0bug
0x0bug merged commit 5c6e158 into main Sep 18, 2026
3 of 5 checks passed
@0x0bug
0x0bug deleted the fix/suppress-progress-clixml branch September 18, 2026 05:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant