PowerShell / PowerShell/PSResourceGet

`PSResourceList` set operation fails when warning contaminates stdout JSON

Open
#1,999 0 comments 0 reactions 1 assignee View on GitHub

@adityapatwardhan is already working on this.

Since Aug 6, 2026.

Dominant language
C#
Stars
576
Forks
114
Avg merge
1d 2h
Merged PRs (30d)
7

Description

Prerequisites
  • Write a descriptive title.
  • Make sure you are able to repro it on the latest released version
  • Search the existing issues.
Steps to reproduce

On a fresh Windows Server 2025 box, the Microsoft.PowerShell.PSResourceGet/PSResourceList DSC resource fails during a set operation. This is because by default the modules path isn't added to the PATH throwing a warning like:

The installation path for the script does not currently appear in the CurrentUser path environment variable. To make the script discoverable, add the script installation path, C:\Users\vmadmin\Documents\PowerShell\Modules, to the environment PATH variable.

Because PSResourceGet runs cmdlets in the same runspace as the script, the warning reaches the stdout pipe that DSC reads as JSON, causing the verification step to fail.

To reproduce the issue, create a fresh Windows Server 2025 box (I used Azure) and run:

$in = @'
$schema: https://aka.ms/dsc/schemas/v3/bundled/config/document.json
resources:
  - name: Install required modules
    type: Microsoft.PowerShell.PSResourceGet/PSResourceList
    properties:
      repositoryName: PSGallery
      trustedRepository: true
      resources:
        - name: Pester
          version: 5.7.1
        - name: PSScriptAnalyzer
          version: 1.25.0
'@
dsc config set --input $in 
Expected behavior
Return result through `dsc.exe`.
Actual behavior
See message above
Error details

Environment data
ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
---------- -------    ---------- ----                                --------- ----------------
Binary     1.3.0      preview1   Microsoft.PowerShell.PSResourceGet  Core,Desk {Compress-PSResource, Find-PSResource, …

Key   : PSVersion
Value : 7.6.2
Name  : PSVersion


Key   : PSEdition
Value : Core
Name  : PSEdition


Key   : GitCommitId
Value : 7.6.2
Name  : GitCommitId


Key   : OS
Value : Microsoft Windows 10.0.26100
Name  : OS


Key   : Platform
Value : Win32NT
Name  : Platform


Key   : PSCompatibleVersions
Value : {1.0, 2.0, 3.0, 4.0…}
Name  : PSCompatibleVersions


Key   : PSRemotingProtocolVersion
Value : 2.4
Name  : PSRemotingProtocolVersion


Key   : SerializationVersion
Value : 1.1.0.1
Name  : SerializationVersion


Key   : WSManStackVersion
Value : 3.0
Name  : WSManStackVersion
Visuals

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.