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.

Please feel free to provide feedback or file bugs here.

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Disable SSL CRL check on Linux boxes

    I tried to follow "How to Script Disabling CRL Checking With Netsh and Powershell" guide: (https://blogs.msdn.microsoft.com/timomta/2013/06/24/how-to-script-disabling-crl-checking-with-netsh-and-powershell/)
    However netsh is not available on Powershell 6.0.0-alpha Linux version. Could you provide me an alternative?

    Regards,

    ~~~
    PS /root> $PSVersionTable

    Name Value
    ---- -----
    PSVersion 6.0.0-alpha
    PSEdition Core
    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
    BuildVersion 3.0.0.0
    GitCommitId v6.0.0-alpha.14
    CLRVersion
    WSManStackVersion 3.0
    PSRemotingProtocolVersion 2.3
    SerializationVersion 1.1.0.1

    PS /root> netsh netsh : The term 'netsh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling
    of the name, or if a path was included, verify that…

    1 vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)

      We’ll send you updates on this idea

      0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    • [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
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        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 →
      • Position of PowerShell window appears behind Windows taskbar when taskbar is at top

        Dynamically detecting the taskbar position, and dynamically modifying the starting position of the powershell window when opening powershell might be a good solution. I am on Windows 10 with three monitors. The taskbar is locked, not automatically hidden, taskbar is only shown on main display.

        2 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)

          We’ll send you updates on this idea

          0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
        • Composite DSC Resources DependOn Bug?

          Composite Resources DependsOn Bug?

          Bumped into this URL and it seems I'm experiencing the same issue with composite resources DependsOn:

          https://powershell.org/forums/topic/composite-resource-dependson-bug/

          > $psversiontable

          Name Value
          ---- -----
          PSVersion 5.1.15063.502
          PSEdition Desktop
          PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
          BuildVersion 10.0.15063.502
          CLRVersion 4.0.30319.42000
          WSManStackVersion 3.0
          PSRemotingProtocolVersion 2.3
          SerializationVersion 1.1.0.1

          1 vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)

            We’ll send you updates on this idea

            1 comment  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
          • Double DependsOn in mof when using foreach loops

            When using a foreach loop to create a set of resources and trying to set the previous item key as the dependsOn resource, it adds it twice in the mof file.

            Configuration example:
            configuration Test-DependsOnWithLoop {
            param([string[]]$Directories)
            Import-DscResource -ModuleName PSDesiredStateConfiguration
            node localhost {
            $dependsOn = $null
            $dirs.ForEach({
            $res = $_ -replace '\\|:', '_'
            File $res {
            Ensure = 'Present'
            DestinationPath = $_
            DependsOn = $dependsOn
            Type = 'Directory'
            }
            $dependsOn = "[File]$res"
            })
            }
            }

            $dirs = 1..10 | % { "C:\Temp\_$_" }
            Test-DependsOnWithLoop -Directories $dirs

            And if you look at the localhost.mof you'll see:
            DependsOn = { "[File]C__Temp__1", "[File]C__Temp__1"};

            2 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)

              We’ll send you updates on this idea

              In Queue  ·  0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
            • [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…

              1 vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                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 →
              • BUG: GetMetaConfiguration should validate property values against allowed values of MSFT_DSCMetaConfiguration CIM Properties

                Once a node meta configuration is enacted, it is easy for an administrator or process (with malicious intent) to modify the MetaConfig.mof file in C:\Windows\System32\Configuration directory. The GetMetaConfiguration method in MSFT_DscMetaConfiguration class does not validate the property values against the allowed values of the CIM properties.

                Steps to reproduce this behavior:
                - Enact a simple meta configuration and enact it.
                - Open the MetaConfig.MOF file in your favorite editor and change the value of ConfigurationMode to some random text.
                - Save the file and close it.
                - Run Get-DscLocalConfigurationManager.
                - You will see the random value assigned to ConfigurationMode in…

                1 vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

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

                  Ravikanth,

                  We have validated this issue and created two bugs for it.

                  1. We will validate the MOF when it is passed in as part of our API (i.e. Set-DscLocalConfigurationManager) and error if the values are not valid.
                  2. We will write a warning when Get-DscLocalConfigurationManager reads a MOF that has invalid values and at LCM startup. The resultant behavior will behave like it does today where invalid values will be read as the default value by the LCM.

                  Please let us know if this meets your expectations.

                  Regards,

                  MarkG

                • Bug comparing identical DSC resources with complex properties

                  I have system modules that are deployed in nodes according to the configuration data file (psd1). For example, one node can have three modules, or there may be three nodes each one with a module.
                  All modules have a common configuration, so I put this configuration in a separate composite resource. Then, if there are more than one module in a node, the resulting configuration will have duplicate resources.
                  The problem occur when one of these duplicate resources have some complex property. Here is a simplified version of my configuration:

                  Configuration BaseWebConfiguration
                  {
                  Import-DscResource -ModuleName xWebAdministration

                  xWebsite DefaultSite
                  {
                  Ensure…

                  1 vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                  • Type restrictions when rendering a property as a string in a MOF-file

                    Dear,

                    As we use Powershell V5 Classes extensively, we create instances of a class and add them to a Hashtable.

                    This hashtable is assigned to an member of a DSC Resource. When creating the .MOF file, I receive an System.ArgumentException on the DSC resource "PSDesiredStateConfiguration.psm1"

                    -> Only certain basic-types are allowed to be serialized to MOF-file :
                    $elementsAsStrings = foreach ($p in $Value.GetEnumerator())
                    {
                    if($p.Value -isnot [string] -and
                    $p.Value -isnot [char] -and
                    $p.Value -isnot [int64] -and
                    $p.Value -isnot [uint64] -and
                    $p.Value -isnot [double] -and
                    $p.Value -isnot [bool] -and
                    $p.Value -isnot [datetime] -and
                    $p.Value -isnot [ScriptBlock])
                    {
                    $errorMessage = $LocalizedData.HashtableElementTypeNotAllowed -f…

                    1 vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      I agree to the terms of service
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                      0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                    • Bug: DSC Decryption across Servers not Working

                      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 clear text when I run Start-DSCConfiguration -Wait -Verbose
                      You can find it here …

                      4 votes
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        I agree to the terms of service
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                        4 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                      • DSC need to use full width of command processor in output

                        DSC output is not respecting width of console and wraps text around despite full width is not utilized.
                        Please see details here (https://github.com/PowerShell/PowerShell/issues/4030)

                        1 vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          I agree to the terms of service
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

                          0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                        • Get-TargetResource should not use 'Required' parameters

                          I'm not sure why this is, but for some reason Get-TargetResource requires not only the 'Key' parameters, but also the 'Required' parameters. My understanding is only 'Keys' should be necessary to find an existing resource and the 'Required' parameters are necessary when you want to create/update/delete something related to a resource.

                          This really makes no sense and will hinder our ability to build higher level tech on top of DSC. If I have the key values for any piece of data in any system, I should be able to retrieve it without any additional information.

                          In almost all of the…

                          1 vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            I agree to the terms of service
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                            0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                          • Bring the Azure Automation DSC MOF encryption into the on-premises DSC pull server

                            In Azure Automation DSC the whole MOF file gets encrypted without the need to manually issue certificates for every node and then to collect the public keys.

                            From Azure documentation:
                            "Keeping credentials secure in node configurations (MOF configuration documents) requires encrypting the credentials in the node configuration MOF file. Azure Automation takes this one step further and encrypts the entire MOF file."

                            This extremely useful feature sould also be implemented in the on-premises DSC pull server. Especially because the needed functionality must alread be in the WMF 5 as nothing more than WMF 5 is needed to use the Azure…

                            6 votes
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              I agree to the terms of service
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                              survey  ·  0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                            • 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
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                I agree to the terms of service
                                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 →
                              • Add enhanced reporting, allowing you to view the status of all nodes instead of one at a time.

                                Currently, the DSC reporting server only offers the ability to query a single node at a time. I think for any environment, it would be crucial to get a list of the last reported compliance for all nodes. I'd really like to see this feature added in a future release.

                                2 votes
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  I agree to the terms of service
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

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

                                  Eric,

                                  Thanks for the feedback! This is something that we are aware of. We intentionally did not want to do this without having a way to authenticate the requests.

                                  Have you seen this community project? It should help you get the functionality that you are looking for including authentication:
                                  https://github.com/claudiospizzi/DSCPullServerWeb

                                  MarkG

                                • Compiling large number of DSC MOF files is slow

                                  We use logic to dynamically compose a ConfigurationData structure and pass it to the configuration. This logic executes quickly. Calling the configuration generates more than 5,000 MOF files for unique nodes. The process takes 1.5 hours on modern server-class hardware with 16GB RAM. Also, the MOF files are all created at the end of the process, rather than one-at-a-time throughout the process. This causes high memory usage. Please optimize the PSDesiredStateConfiguration module to generate large quantities of MOF files more quickly. This issue adds significant delay to the DSC pipeline.

                                  19 votes
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    I agree to the terms of service
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

                                    6 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                                  • 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
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      I agree to the terms of service
                                      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 →
                                    • 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
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        I agree to the terms of service
                                        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 →
                                      • Start-DscConfiguration over secure WinRM (HTTPS / 5986) without needing to provide the Cim-Session

                                        referring to my post here. http://stackoverflow.com/questions/41567036/start-dsc-configuration-securely-usessl-without-needing-to-provide-the-compute

                                        Having the ability to continue using the ConfigurationData with multiple nodes and use a secure session (WinRM over 5986)

                                        2 votes
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          I agree to the terms of service
                                          Signed in as (Sign out)

                                          We’ll send you updates on this idea

                                          0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                                        • ConfigurationAST should include resource modules being imported

                                          The ConfigurationAST added in v4 for PowerShell DSC does a good job at providing resource configuration details. However, to determine what modules are being imported, we should still use the keyword AST to find the resource module names from the Import-DSCResource command. While this is a workaround, it will be easier if ConfigurationAST can provide this information for simplicity.

                                          14 votes
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            I agree to the terms of service
                                            Signed in as (Sign out)

                                            We’ll send you updates on this idea

                                            survey  ·  0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                                          ← Previous 1 3 4 5 6 7
                                          • Don't see your idea?

                                          Feedback and Knowledge Base