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. RMDIR bug - causing "Access is denied"

    : z:\ca\WinRdBug.cmd * L=001 --- 2017/12/05 13:02:28

    : The RMDIR command has a bug that, as well as not working,

    : causes the target directory to become inaccessible.

    : i.e. operation on it all result in "Access is denied" or similar :messages.

    : The problem is easily demonstrated using the sequence of :commands below.

    : This bug is causing significant inconvenience and we need a fix or

    : reasonable work-around quickly please. (just upgraded to Win10
    : from XP where this is not an issue).

    mkdir c:\t1229

    echo *** >c:\t1229\x.x

    type c:\t1229\x.x

    rmdir c:\t1229 /s /q

    type c:\t1229\x.x

    pause

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

    We’ll send you updates on this idea

    2 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  2. Resolve-Path behaviour inconsistent

    Resolve-Path turns a string (path to some directory) into a PathInfo object.
    If that returns wthout error, the path exists and is 'correct' i.e. no typo etc. Its a great way to sanity-check user input.

    It also normalizes input. some examples:
    (resolve-path 'C:\users').Path -eq (resolve-path 'c:\users').Path
    > True # (yes, this is also due to -eq acting case-insensitive on strings)
    (resolve-path 'c:\use').Path -eq (resolve-path 'C:\users').Path
    > True
    (resolve-path 'c:\use
    \\').Path
    > C:\Users

    This is very nice. And here's a Trap that's built in:
    (resolve-path 'C:\Users').Path -eq (resolve-path 'C:\Users').Path
    > False

    Note: no error is thrown, so apparently all is…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  3. Bug: sort is incorrect for strings containing the '-' character

    "somefile1","somefile2","s-abc","s-little","s-foo","s-poo","s-wtf" | sort
    s-abc
    s-foo
    s-little
    somefile1
    somefile2
    s-poo
    s-wtf

    ----compare to the correct----
    "somefile1","somefile2","sabc","slittle","sfoo","spoo","swtf" | sort
    s
    abc
    sfoo
    s
    little
    spoo
    s
    wtf
    somefile1
    somefile2

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  4. AppBackgroundTask manifest lists parameter aliases

    The module manifest for AppBackgroundTask lists 3 cmdlet aliases:

    iru
    pfn
    tid

    But, when you import the module into the session, those aliases are not exported.

    PS C:> ipmo AppBackgroundTask -PassThru

    ModuleType Version Name ExportedCommands


    Manifest 1.0.0.0 AppBackgroundTask {Disable-AppBackgr

    PS C:> Get-Alias | where Source -eq 'appbackgroundtask'
    PS C:>

    The problem is that they're not cmdlet aliases; they're parameter aliases defined in the module CDXML files.

    You should not list module aliases in a .psd1 file.

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  5. Bug? SCOM cmdlets don't fully load until first execution of cmdlet

    SCOM module is loaded.
    Get-SCOMAgent cmdlet (among other SCOM cmdlets) is not recognized as cmdlet.
    Execute 1 cmdlet from the loaded SCOM cmdlet.
    Get-SCOMAgent cmdlet is now recognized.

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  6. Get-ComplianceSearch

    Get-ComplianceSearch | Select-Object Items on multiple content searches comes back as 0. If you check then individually you get an accurate item count

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  7. Resolve-DnsName -DNSSECOK output should indicate validation success or failure (AD flag set)

    When using "Resolve-DnsName -DNSSECOK" to resolve a DNS name that may be signed with DNSSEC, the output of the command should indicate validation success or failure somehow; for example, the output object could have a new property named "DnsSecValidated" or "AuthenticatedData" set to true/false.

    In various documents, Microsoft currently demos testing a DNSSEC response with a third-party tool (dig). It would be better to handle it all natively in PowerShell.

    ( Here is how the dig tool does it: https://techglimpse.com/dns-dnssec-testing-validating-tools/ )

    More specifically, a response to a DNS query with the "DNSSEC OK" flag should set another flag named "Authenticated…

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

    We’ll send you updates on this idea

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

    Hi Jason,

    Thanks for the report! Unfortunately, this UserVoice is for core modules included with PowerShell itself, while the DnsClient module belongs to the Windows 10 team. The best way to reach them is to file feedback using the Windows Feedback Hub in Windows 10 to drive this request.

    Thanks,
    Joey

  8. Get-MsmqOutgoingQueue is not returning anything

    I am running Get-MsmqOutgoingQueue on a Windows Server 2012 R2 machine with MSMQ enabled. I have messages queues created and I have messages in the queues. When I run Get-MsmqOutgoingQueue -Name "MyQueue" it returns nothing. If then run Get-MsmqOutgoingQueue with no params, it also returns nothing (according to the documentation it should return all the queues) - so what is going on?

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    external  ·  Zachary Alexander responded

    This cmdlet is not owned by the PowerShell team. See comments for feature team’s explanation.

  9. Crash on OS X

    PowerShell crashed on OS X:

    PS /Users/PATH> ibtool ./Base.lproj/Main.storyboard --generate-strings-file Main.strings

    ^[[24;1R^[[24;1RPS /Users/PATH>
    Unhandled Exception: System.IO.IOException: The process cannot access the file because it is being used by another process.
    at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func2 errorRewriter)
    at Interop.CheckIo(Int64 result, String path, Boolean isDirectory, Func
    2 errorRewriter)
    at System.IO.StdInStreamReader.ReadKey(Boolean& previouslyProcessed)
    at System.IO.SyncTextReader.ReadKey(Boolean& previouslyProcessed)
    at System.ConsolePal.ReadKey(Boolean intercept)
    at System.Console.ReadKey(Boolean intercept)
    at Microsoft.PowerShell.Internal.TTYConsole.ReadKey()
    at Microsoft.PowerShell.PSConsoleReadLine.ReadOneOrMoreKeys()
    at Microsoft.PowerShell.PSConsoleReadLine.ReadKeyThreadProc()
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    zsh: abort /usr/local/bin/powershell

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    external  ·  Zachary Alexander responded

    Please file issues for PowerShell Core directly on GitHub, especially for other operating systems. GitHub has an issues template which helps us get the information we need to start debugging.

  10. Windows Management Framework 4.0, 5.0, 5.1

    Please make sure, that all Microsoft applications are compatible with Windows Management Framework in conjunction with Microsoft .NET Framework 4.x
    Escpecially SharePoint, Exchange Server or System Center products were often not compatible.

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

    We’ll send you updates on this idea

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

    The PowerShell team is working with the teams you mentioned to provide support for WMF releases. It is the decision of those teams (SharePoint, Exchange, and System Center) whether or not to provide support, and on which OS targets that the WMF installs to.
    You may be able to assist by raising the request to support WMF to those teams via your TAMs and their feedback channels.

  11. Add-VPNConnection does not suport using L2tp with PAP and Required Encryption

    Bug! Add-VPNConnection does not suport using L2tp with PAP and Required Encryption. You can do this in the GUI but you cant do it in PowerShell

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    external  ·  Zachary Alexander responded

    Thanks so much for the feedback. Unfortunately, this functionality is not owned by the PowerShell Core team. We recommend that you file the feedback with the Windows team using the Windows Feedback/Feedback Hub app included with Windows 10

  12. Default Resolve-DNSName Object Output Results in Array of Mixed Object Types

    Using the DNSClient module included in RSAT, the default output of the cmdlet mixes different object types.

    You can see examples of using the cmdlet, and the cluttered multi-object output, here:
    https://blogs.technet.microsoft.com/heyscriptingguy/2013/01/08/replace-nslookup-with-a-built-in-windows-8-powershell-function/

    You can see that the default output is a mix of Format-Table and Format-List styles, due to the different types in the result. This seems very non-standard for PowerShell cmdlets to be producing different object types. Maybe this could be resolved based on parameter usage? Or by nesting objects within results when retrieving multiple record types at once?

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    external  ·  Zachary Alexander responded

    Thanks for the feedback! Unfortunately, the Resolve-DNSName cmdlet isn’t managed by our team, but we’ll do our best to pass the bug on to the appropriate team.

  13. Feature Request: Provide Working Tabs for PowerShell

    Feature Request:
    Include an optional tabbed interface within PowerShell.exe to allow multiple instances of concurrent active PowerShell windows. This would allow different interactive sessions to be open instead of launching multiple PowerShell.exe windows to save the end user additional screen real estate when using PowerShell where Enter-PSSession and Exit-PSSession may not be utilized based on the user's workflow.

    Idea from blog post:
    http://www.hanselman.com/blog/ConEmuTheWindowsTerminalConsolePromptWeveBeenWaitingFor.aspx

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

    We’ll send you updates on this idea

    1 comment  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  14. The Tip of the week doesn't work for me.

    The Tip of the week doesn't work for me. https://technet.microsoft.com/en-us/library/ff730941.aspx
    I know it's not the right place to post but maybe you can forward to someone to fix. Everything seems to work but I get no output for $x

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  15. Expand-Archive.ps1 should unzip non zip-formats without .zip extensions (like .nupkg)

    Votes from Connect: 6

    Original Date Submitted: 4/17/2015 10:10:19 PM

    Description:
    Contact Information
    Handle: alejandro5042
    Site Name: PowerShell
    Feedback ID: 1255281


    Problem Description:
    There are many file formats that are actually just .zip files but with different extensions. For example, NuGet packages are really zip files with the .nupkg extension. My company (National Instruments) has many of these types of formats, as does Microsoft with their Office formats, and many other companies.

    It's silly to have to copy/rename the file to have a .zip to have this cmdlet extract the contents. I suggest removing the .zip file check in all…

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

    We’ll send you updates on this idea

    2 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  16. Compress-archive add password switch to allow create protected zip files

    Votes from Connect: 7

    Original Date Submitted: 5/20/2015 9:21:45 PM

    Description:
    Contact Information
    Handle: MDrobul
    Site Name: PowerShell
    Feedback ID: 1350514


    Problem Description:
    Add support to create password protected zip files and extract them.

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

    Repro Steps:

    Internal BugId: 14497

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add functionality to Expand-Archive so that it can open password-protected archive (zip) files

    Votes from Connect: 4

    Original Date Submitted: 5/12/2015 2:38:00 AM

    Description:
    Contact Information
    Handle: Set-Name Mark Wilson
    Site Name: PowerShell
    Feedback ID: 1323774


    Problem Description:
    Please add a -Password switch to Expand-Archive so that it can open password-protected archive files. These files can currently be opened only through the GUI.

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

    Repro Steps:

    Internal BugId: 14458

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  18. Set-UserPhoto Exchange Online 413 Request Entity Too Large

    Votes from Connect: 3

    Original Date Submitted: 7/18/2014 3:23:48 PM

    Description:
    Contact Information
    Handle: Chen V
    Site Name: PowerShell
    Feedback ID: 923189


    Frequency: Always Happens
    Regression: I do not know if this issue existed previously

    Problem Description:
    We tried Pushing high resolution picture to exchange online to replicate the same in LYNC 2010 on premises environment. We do have a plan to migrate 2010 Lync Client to 2013.

    I tried Set-UserPhoto in Exchange Online with WMF 2.0 in 2008 R2 server. It worked fine. Ideally it shouldn't because the maximum size allowed is 10 KB with 96 X 96. If…

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base