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. Jea can not be used with local account if RunAsVirtualAccount is set to $true

    Jea will not allow authenticate as local user on Windows if "RunasVirtualAccount" is set to $true for PssessionConfiguration

    [ADMIN]: PS > Enter-PSSession mivcustftp1 -Credential $gregcred -ConfigurationName JEA
    Enter-PSSession : Processing data from remote server mivcustftp1 failed with the following error message: There are currently no logon servers available to
    service the logon request. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + Enter-PSSession server -Credential server\account -ConfigurationName ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidArgument: (server:String) [Enter-PSSession], PSRemotingTransportException
    + FullyQualifiedErrorId : CreateRemoteRunspaceFailed

    Switching configuration RunAsVirtualAccount to $false will allow to authenticate

    Server reports following error during failure

    An…

    1 vote
    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 →
    planned  ·  Zachary Alexander responded

    Per Ryan’s response:
    “This is a known issue in WMF 5.0 and Windows Server 2016 Technical Preview. We are working to get this fixed in a future release, but until then you can only use virtual accounts in JEA on domain-joined machines.”

  2. Bug: WMF 5 Production Preview on Windows Server 2008R2 breaks sysprep

    I just ran into the exact problem described in this ServerFault article:
    http://serverfault.com/questions/749441/sysprep-fails-on-windows-2008-r2-after-wmf5-installation

    After installing WMF 5 Production Preview, sysprep fails out, complaining that a registry key it is trying to delete doesn't exist.

    The workaround in that link works. Adding:

    REGEDIT4
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\StreamProvider] "LastFullPayloadTime"=dword:00000000

    allows sysprep to complete properly.

    This appears to be related to the sysprep failure caused by WMF5 on Server 2012. The changes in Generalize.xml in that bug include the registry delete command implicated in this bug.

    http://windowsserver.uservoice.com/forums/301869-powershell/suggestions/11518368-bug-wmf-5-production-preview-on-windows-server-20

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

    We’ll send you updates on this idea

    8 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  3. [ordered] does not work inside class definition

    An unresolvable type name token inside a class definition is considered a parse error. [ordered] is not a valid type, so using of it inside class definition cause parse error.

    class C {
        [object] M(){
            return [ordered]@{}
        }
    }

    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 Engine  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for reporting this issue. It has been fixed in our internal builds and the fix is available in latest insider fast ring builds.

  4. Bug: WMF 5 Production Preview on Windows Server 2012 breaks Sysprep

    Installing the WMF Production Preview on a Windows Server 2012 machine causes sysprep to fail with the following messages:

    2016-01-14 15:58:26, Error [0x0f00bf] SYSPRP CreateSysprepActionList: Invalid action node sysprepOrder found for component Microsoft-Windows-SoftwareInventoryLogging-ScheduledTasks
    2016-01-14 15:58:26, Error SYSPRP SysprepSession::Execute: Error in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x10dd
    2016-01-14 15:58:26, Error SYSPRP RunPlatformActions:Failed while executing SysprepSession actions; dwRet = 0x10dd
    2016-01-14 15:58:26, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x10dd
    2016-01-14 15:58:26, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep generalize internal providers; hr = 0x800710dd
    2016-01-14 15:58:26, Info [0x0f004c] SYSPRP WaitThread:Exiting…

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

    We’ll send you updates on this idea

    2 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  5. Find-Module needs improvements to enable better discoverability

    Votes from Connect: 3

    Original Date Submitted: 11/3/2015 7:38:42 PM

    Description:
    ********Contact Information********
    Handle: Ryan Yates 90
    Site Name: PowerShell
    Feedback ID: 1976168
    ***************************************

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

    Problem Description:
    The Find-module command needs some further improvements to allow there to be better discoverability of functions and Modules including the ability to search for functions using Wildcards and also to get back results based on the functions Synopsis, Description, Function Name, Notes & Examples

    An example of a better formatted Find-Module command could be

    Find-Module -Command '*SharePoint*' and this should return all modules…

    8 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 Engine  ·  Flag idea as inappropriate…  ·  Admin →
  6. Invoke-command does not return output from modules on v2 targets

    I have the following PS module (testme.psm1) saved to a properly-named folder on Win7 (powershell v2) and Win8.1 (powershell v4) machines:
    --------
    #requires -version 2.0

    function Test-Output {
    [CmdletBinding()]
    Param ()

    Write-Output "Test-Output SUCCESS"
    Write-Verbose "Test-Output VERBOSE SUCCESS"
    }
    -----

    When I test it from a Win10 (PS v5) system, output is as follows:

    PS> invoke-command win7 {import-module testme;test-output}
    (no output)

    PS> invoke-command win7 {import-module testme;test-output -verbose}
    (no output)

    PS> invoke-command win81 {import-module testme;test-output}
    Test-Output SUCCESS

    PS> invoke-command win81 {import-module testme;test-output -verbose}
    Test-Output SUCCESS
    VERBOSE: Test-Output VERBOSE SUCCESS

    PS>

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

    We’ll send you updates on this idea

    planned  ·  2 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base