PowerShell

The PowerShell forum accepts bug reports as well as feedback and suggestions. For more information, check out the PowerShell Homepage

The following is a list of the states we use to track items.

status meaning
survey We saw this and we are considering it. Please upvote if it’s important to you.
needs more information We don’t understand the issue and need additional details.
investigating We are looking at this internally to understand things like: scenario, reproduction of issue, costing, or other technical details.
in queue The issue is understood and in our unprioritized backlog. Your votes will be used to drive prioritization of this work.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. WMF 5.1 breaks class registrations for the ConfigMgr client agent

    I've localized this issue to WMF 5.1 on Windows 7. With this installed, the WMI namespace: root\ccm\policy\defaultmacine\requestedconfig becomes invalid. This is important because in In-Place upgrade scenarios from Windows 7 to Windows 10, the task sequence agent cannot resume the task sequence without being able to read this namespace. I know this is a combination of WMF and ConfigurationManager so I will post there as well.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →

    This issue was recently reported via another channel, and is being actively investigated.
    Don’t have an ETA at this time, but will update this thread as we learn more.

  2. [BUG] Configuration enact fails when resource instances of same type have different PSDscRunAsCredentials

    Take a look at the following configuration:
    $configurationData =
    @{
    AllNodes =
    @(
    @{
    NodeName = 'S16-01'
    PsDscAllowPlainTextPassword = $true
    PSDscAllowDomainUser = $true
    }
    )
    }

    Configuration DSCRunDemo
    {
    param (
    [pscredential] $Credential
    )
    Import-DscResource -ModuleName PSDesiredStateConfiguration

    Node $AllNodes.NodeName
    {
    Script DSCRunDemo1
    {
    SetScript =
    {
    Write-Verbose -Message $(whoami)
    }
    TestScript =
    {
    return $false
    }
    GetScript =
    {
    return @{}
    }
    PsDscRunAsCredential = $Credential
    }

    Script DSCRunDemo2
    {
    SetScript =
    {
    Write-Verbose -Message $(whoami)
    }
    TestScript =
    {
    return $false
    }
    GetScript =
    {
    return @{}
    }
    }
    }
    }

    DSCRunDemo -ConfigurationData $configurationData -Credential (Get-Credential)

    One instance of the…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    investigating  ·  0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add maintenance window awareness to DSC / LCM

    Votes from Connect: 17

    Original Date Submitted: 8/13/2015 12:17:49 AM

    Description:
    ********Contact Information********
    Handle: PowerShellDon
    Site Name: PowerShell
    Feedback ID: 1659904
    ***************************************

    Problem Description:
    Suggestion one:

    Add maintenance window awareness to the Local Configuration Manager. Edited via metaconfig, it specifies times when configuration changes are acceptable, when automated reboots are acceptable. Further automates configuration maintenance especially when you're implementing changes vs. correcting drift.

    Suggestion two:

    Add universal "DoNotImplementBefore" and "ImplementBy" settings to DSC resources. Just as "Present=" specifies to add/remove something, these would indicate a date/time for the setting to become valid (e.g., "we want to implement a bunch of…

    137 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    investigating  ·  Mark Gray responded

    Your votes on this and other features helps us in our feature prioritization.

    Thank you!!

    MarkG

  4. Find-Module and Install-Module does not get the modules from the custom nuget fileshare repositories though they are registered successfully

    PS C:\Windows\system32> Get-PSRepository

    Name InstallationPolicy SourceLocation
    ---- ------------------ --------------
    PSGallery Untrusted https://www.powershellgallery.com/api/v2/
    TestRepo Trusted \\NugetServer\BMNNuGet\packages

    PS C:\Windows\system32> Find-Module * -Repository TestRepo

    Version Name Repository Description
    ------- ---- ---------- -----------
    1.0.1 cConfigNode TestRepo Provides a way to manipulate nodes of the xml configu...
    1.3.0 cNtfsAccessControl TestRepo The cNtfsAccessControl module contains DSC resources ...
    3.2.0 xNetworking TestRepo Module with DSC Resources for Networking area
    1.0.0 xReleaseManagement TestRepo Host a custom DSC Resource to transform files based o...
    1.17.0 xWebAdministration TestRepo Module with DSC Resources for Web Administration

    PS C:\Windows\system32> Find-Module xNetworking -Repository TestRepo
    PackageManagement\Find-Package : No match was found for the specified…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →

    Sorry for the long lag in responding to this, all I can say is that we missed it.

    This problem is not something we’re familiar with. If the problem is still repro’ing, please try re-running your commands with -Verbose, and attach the information to this thread.

    One additional question that might help us: what version of the NuGet server are you using?

  5. Powershell (self) update

    It would be very helpful if we could update PowerShell to newest version through PS package manager or OS included script - with all dependencies and prerequisites checks.

    8 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →

    This is definitely something we’re thinking about and working towards. The question becomes whether it’s “good enough” to update all the built-in modules (like MS.PS.Utility or MS.PS.Management) via PowerShellGet or if we need to actually update PowerShell itself.

    As we work on PowerShell Core on GitHub (https://github.com/powershell/powershell) we’re beginning to think about how more engine work might be abstracted into individual modules (which, again, could be updated async from the Gallery).

    That being said, there also is probably some value in installing PowerShell Core all up via “Install-Package” or “Update-Package”. Given that PS Core is fully side-by-side enabled, you could slap down a new version of PowerShell Core next to the one from which you’re actually running PowerShell Core.

    At the same time, updating Windows PowerShell (the Windows-only edition of PowerShell that sits on top of the full, .NET Framework) from within Windows PowerShell is significantly trickier…

  6. converting multiple lines of code to comment

    Votes from Connect: 5

    Original Date Submitted: 2/20/2015 2:01:32 PM

    Description:

    ********Contact Information********
    Handle: john.s2011n
    Site Name: PowerShell
    Feedback ID: 1139497
    ***************************************

    Frequency: Always Happens
    Regression: Yes, this happens in all previous versions

    Problem Description:
    in PS 4.0 and also previous versions, there is no option to easily convert multiple selected lines to comment block. so when we have selected multiple lines & we want to make them as comment, we have to insert comment block in another location on the pane, and then cut these multiple lines and paste them inside comment block which is a bit cumbersome.
    but…

    79 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  7. ISE should provide an option to restore previously opened files at startup

    When ISE starts up, it should by default (make that configurable: always, prompt, never) restore all files that were open in the previous session.

    56 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  8. Windows Update Provider for Powershell Package Manager

    Votes from Connect: 3

    Original Date Submitted: 6/1/2015 12:20:47 AM

    Description:
    ********Contact Information********
    Handle: Matt McNabb
    Site Name: PowerShell
    Feedback ID: 1386686
    ***************************************

    Problem Description:
    Please distribute Windows Updates via a package provider. This will allow browsing and installing updates via existing cmdlets such as Find-Package and Install-Package.

    Product Studio item created by Connect Synchronizer due to creation of feedback ID 1386686 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1386686).

    Repro Steps:

    Internal BugId: 14531

    63 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  9. PowerShell ISE VariableExplorer

    Votes from Connect: 6

    Original Date Submitted: 10/16/2015 2:00:41 PM

    Description:
    ********Contact Information********
    Handle: Gimli92
    Site Name: PowerShell
    Feedback ID: 1907258
    ***************************************

    Problem Description:
    It would be nice to have a built in VariableExplorer in order to see and browse through all variables of the current PowerShell session.

    Product Studio item created by Connect Synchronizer due to creation of feedback ID 1907258 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1907258).

    Repro Steps:

    Internal BugId: 15901

    58 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  10. [Bug] Install-Module -Force prompts for user input when NuGet-anycpu.exe is not present

    Steps to reproduce:

    1. Install WMF5 RTM on a fresh Windows 2012 R2 system
    2. Open an Administrator PS prompt and run "Install-Module Pester -Force"

    Expected result: The -Force parameter causes the NuGet client to be installed without user intervention.

    Actual result: The following message is displayed:

    NuGet-anycpu.exe is required to continue.
    PowerShellGet requires NuGet-anycpu.exe to interact with NuGet based galleries. NuGet-anycpu.exe must be available in
    'C:\Program Files\PackageManagement\ProviderAssemblies' or
    'C:\Users\Administrator\AppData\Local\PackageManagement\ProviderAssemblies'. For more information about NuGet provider,
    see http://OneGet.org/NuGet.html. Do you want PowerShellGet to download NuGet-anycpu.exe now?
    [Y] Yes [N] No [S] Suspend [?] Help (default is "Y"):

    The MSDN…

    24 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow Register-PSRepository to persist credentials

    NuGet feeds allow security around both listing/retrieving packages as well as pushing packages. NuGet.exe and other clients further allow you to persist credentials for listing/retrieving packages using the "nuget sources" command. (https://docs.nuget.org/consume/command-line-reference#sources-command)

    This persistence is important for two reasons:

    1) When you push a package to a secured NuGet feed, NuGet clients generally do a list/read operation first. That list/read operation doesn't contain any API key that you pass along in the push operation. In order for a push to succeed with an API key, you also need to have credentials set for the read operation. You can…

    29 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  12. Test-DscConfiguration fails once running against remote machine

    Having the following script:

    configuration SimpleConfig2
    {
    Import-DscResource –ModuleName 'PSDesiredStateConfiguration'

    node $remoteCommputer
    {
    Environment TestVersion
    {
    Ensure = "Present" # You can also set Ensure to "Absent"
    Name = "TestEnvironmentVariable"
    Value = "TestValue2"
    }
    }
    }

    SimpleConfig2

    Start-DSCConfiguration -Path "SimpleConfig2" -Force -Wait -ComputerName $remoteCommputer -Credential $g_AutomationDefaultVMAccounCred -verbose

    $result = Test-DscConfiguration -Path "SimpleConfig2" -ComputerName $remoteCommputer -Credential $g_AutomationDefaultVMAccounCred

    The config is applied correctly, yet Test-DscConfiguration fails with the following message:

    The configurationData parameter is reserved for future use. The current configuration is used by default.
    + CategoryInfo : InvalidArgument: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : MI RESULT 4
    + PSComputerName : target-machine

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    investigating  ·  Mark Gray responded

    Anton,

    I am not able to reproduce your issue. What PS / WMF version are you running into this on? Also what OSes are running on the local and remote machines?

    MarkG

  13. BUG: The certificate for the WMF 5.1 setup has expired WMF 5.1 cannot be installed

    The certificate for Win7AndW2K8R2-KB3191566-x64.msu has expire and installing WMF 5.1 fails with the following error in Event Log/Windows Logs/Setup

    Windows update "Update for Windows (KB3191566)" could not be installed because of error 2148204801 "A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file." (Command line: ""C:\Windows\system32\wusa.exe" "C:\Users\username\Downloads\Win7AndW2K8R2-KB3191566-x64\Win7AndW2K8R2-KB3191566-x64.msu" ")

    Is WMF 5.1 still supported?

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  14. [BUG] Cannot import both PSDesiredStateConfiguration in-box module and PSDscResources (gallery module) in the same configuration

    OS: Windows Server 2016 1607 (14393.1593)
    PSVersionTable:
    Name Value
    ---- -----
    PSVersion 5.1.14393.1532
    PSEdition Desktop
    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
    BuildVersion 10.0.14393.1532
    CLRVersion 4.0.30319.42000
    WSManStackVersion 3.0
    PSRemotingProtocolVersion 2.3
    SerializationVersion 1.1.0.1

    PSDscResource module: v2.8.0.0

    Take a look at this configuration:
    Configuration DependentConfig
    {
    Import-DscResource -ModuleName PSDscResources -Name Registry

    Node MyNode01
    {

    File SetupScript
    {
    DestinationPath = 'C:\Scripts\hello.txt'
    Contents = 'somecommand'
    Type = 'File'
    Ensure = 'Present'
    DependsOn = '[Registry]regCheck'
    }

    Registry regCheck
    {
    Key = 'HKEY_LOCAL_MACHINE\SYSTEM\SomeKey'
    ValueName = 'SomeValue'
    ValueData = 0
    ValueType = 'DWord'
    Ensure = 'Present'
    }
    }
    }

    DependentConfig -OutputPath C:\DependentConfig

    This requires PSDscResources module version 2.8.0.0 from…

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    investigating  ·  4 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  15. Message Cannot unprotect message. The input contained no encrypted content

    When upgrading to WMF 5.1, we are seeing errors in the DSC event log on servers that use a configuration with encrypted content (passwords). We are using encrypted credentials to create application pools and assign a service account as the identity. The data gets decrypted fine and the app pools get created with the correct identities. However the following error gets logged in the DSC event log every time a consistency check runs:

    Job :
    Message Cannot unprotect message. The input contained no encrypted content. Specify the '-IncludeContext' parameter if you wish to output the original content when no encrypted…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    investigating  ·  0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  16. Creators update: stop-computer : Privilege not held

    I ran into this one, after I noticed my newly patched workstation was still turned on in the morning even though I had explicitly requested it to shutdown at a certain time. Basically the repro steps are as follows:

    > Open Non-Administrative Shell
    > Stop-Computer
    Output:
    stop-computer : Privilege not held.
    At line:1 char:1
    + stop-computer
    + ~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (***:String) [Stop-Computer], ManagementException
    + FullyQualifiedErrorId : StopComputerException,Microsoft.PowerShell.Commands.StopComputerCommand

    Administrative shell works as expected, this specific workstation has never participated in any fast/slow ring builds. Windows version is 15063.138

    Another Windows 10 system, fast ring, that is on build 15063.14…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →

    FYI, we’re aware of this problem and are currently investigating it.

    Other threads here that we’re aware of:

    I THINK we understand the problem, but I can’t offer an ETA on a fix right now, unfortunately.

  17. Bug: DSC Decryption across Servers not Working

    On 2 Fully Updated Windows Server 2016 Machines running and provisioned from Azure I have created a Pull Server Configuration. I have created the DSC Signing Certificate using a custom template on a Enterprise Root CA which has worked for 2012R2 nodes and also tested using xDSCUtils New-xSelfSignedDscEncryptionCertificate. Using the same Certificate to Compile and Execute the MOF on the same Computer works, it is only if you compile on one and execute on another that the problems arise.
    I kept getting errors when passing in credentials. I therefore wrote a tiny custom DSC Resource that Displays the Password as…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    investigating  ·  0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  18. partial

    Hi all,
    I am using DSC partials to create role-based architectures with Azure virtual machines.
    When switching to Windows 2016 (everything works great on Windows 2012 R2), I get errors when DSC is compiling the MOF.
    The idea is that I have multiple partials that contain the same Windows Feature installation, because it's needed for a certain roles. When I apply more roles on the same machine, the partials need to merge. So I have one partial that contains this:
    WindowsFeature DotNetFrameworkRole1
    {
    Name = 'AS-NET-Framework'
    }
    and another partial that contains this:
    WindowsFeature DotNetFrameworkRole2
    {
    Name = 'AS-NET-Framework'
    } …

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    investigating  ·  1 comment  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  19. workflow common parameters

    The WorkflowCommonParameters entry is missing from help for workflows.

    PowerShell workflows have both common parameters and workflow common parameters.

    Get-Help help for workflows has an entry in the Parameters section for CommonParameters, but not for WorkflowCommonParameters. It needs both.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  20. No StdOut output on console until second object

    Let me explain. I have a script that is collecting data, and I send it to StdOut by simply piping it into Select (but problem also happens if I add a ForEach loop and simply make [PSCustomObject] objects). Then my script loops to the next server. That output is not displaying on the screen. All is not lost though, when the script loops to the second server and displays both the first and second will now display. When the third server finishes it displays OK, as does the 4th.

    So it looks like it's just the first one. Normally I…

    5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4
  • Don't see your idea?

Feedback and Knowledge Base