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. |
-
Provide a simply way to filter results to items owned by Microsoft.
Provide a simply way to filter results to items owned by Microsoft. Some companies only allow official Microsoft tools and scripts to be used.
3 votes -
PowerShell ISE does not have the ability to restart the console independent of restarting the entire ISE
Restarting the Powershell process independent of the entire ISE would be a beneficial feature for ISE users during testing and debugging, to clear variables, sessions, scopes, classes, etc... If you are working in the ISE and have several script files open on the editor it is cumbersome to have to save files, restart the entire ISE application and reopen files etc...
37 votesThis will be enabled when PowerShell ISE moves to PowerShell Editor Services as its core.
-
Install-PackageProvider doesn't work with proxy authentication
Install-PackageProvider cannot retrieve the list of available providers if the machine doesn't have direct access to the internet.
PS C:\Windows\system32> Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
WARNING: Unable to download the list of available providers. Check your internet connection.
Install-PackageProvider : No match was found for the specified search criteria for the provider 'NuGet'. The package
provider requires 'PackageManagement' and 'Provider' tags. Please check if the specified package has the tags.
At line:1 char:1
+ Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : InvalidArgument: (Microsoft.Power...PackageProvider:InstallPackageProvider) [Install-Pac
kageProvider], Exception
+ FullyQualifiedErrorId : NoMatchFoundForProvider,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackagePro
vider
How to reproduce:
1.…49 votes -
PowerShell ISE should support sytax highlighting for JSON
Votes from Connect: 10
Original Date Submitted: 3/4/2015 1:43:50 AM
Description:
Contact Information
Handle: JasonHorner
Site Name: PowerShell
Feedback ID: 1159120
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
JSON is fast becoming a viable alternative to XML.. Therefore PowerShell ISE should support syntax coloring in a similar manner as it treats XML filesProduct Studio item created by Connect Synchronizer due to creation of feedback ID 1159120 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1159120).
Repro Steps:
open a json file in powershell all the text is blackExpected Results:
.Json should be added to the list of supported…64 votesHi Jason,
We definitely consider this hugely valuable, but it is a big work item, and we’re not sure where it sits in our current roadmap.
We’ll post back here as more details become available.
Thanks,
Joey -
ISE: Add support for "Copy Full Path" context menu command on script tabs
I often need the path name to the file I'm editing. In V3 I can hover the mouse over the tab and a tooltip will present the path. However, I usually need to provide this path to other commands (like cd or paste them into another window), and I currently have to hand-repeat it.
Right-Click on tab -> Copy Full Path is a great way to solve this; it's the same approach used by Visual Studio.
23 votesThis is definitely high-value, and we plan to do it eventually in the PowerShell ISE Preview. Read more about it here: https://blogs.msdn.microsoft.com/powershell/2016/01/20/introducing-the-windows-powershell-ise-preview/
-
[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]@{}
}
}1 voteThank you for reporting this issue. It has been fixed in our internal builds and the fix is available in latest insider fast ring builds.
-
WMF 5.1 - Update misleading prerequisite information for Win7 SP1
WMF 5.1 requires .NET Framework 4.5.2 should indicate :
WMF 5.1 requires .NET Framework 4.5.2 or later1 voteWe will update that documentation, thanks.
-
Cannot specify remote filename when calling Copy-Item with -ToSession
The use case is copying a local file to a remote server using PowerShell remoting and Copy-Item:
$remote = "aremotemachine.example.com"
$cred = Get-Credential
$session = New-PSSession -ComputerName $remote -Credential $cred
echo "testcontent" > testfile.txtWorks when we only specify a destination directory
Copy-Item -Path testfile.txt -Destination C:\ -ToSession $session
Doesn't work when we specify a filename
Copy-Item -Path testfile.txt -Destination C:\testfile.txt -ToSession $session
Even if it's different from the original filename
Copy-Item -Path testfile.txt -Destination C:\testfile2.txt -ToSession $session
Here is the output I get for the first failed command
Copy-Item : Destination folder 'C:\testfile.txt' does not exist.At line:1
char:1
+…5 votesWe believe we understand the problem and are working to address it.
-
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
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 aboutRemoteTroubleshooting Help topic.
At line:1 char:1
+ Enter-PSSession server -Credential server\account -ConfigurationName ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : InvalidArgument: (server:String) [Enter-PSSession], PSRemotingTransportException
+ FullyQualifiedErrorId : CreateRemoteRunspaceFailedSwitching configuration RunAsVirtualAccount to $false will allow to authenticate
Server reports following error during failure
An account failed to log on.
Subject:
…Security
1 votePer 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.” -
Allow dot sourcing PowerShell Classes based DSC Resources into the psm1 module file
WMF 5.0 lets you create DSC Resources using Powershell Classes like so:
[DscResource()]
class MyDSCResource
{
...
}But right now it will only look in the .psm1 file. If you try to dot source a class based DSC resource into the .psm1 file then Get-DSCResource can't find it and it can't be used in DSC configurations.
We have many DSC resources combined into a single module, and our .psm1 file is getting difficult to manage. If two people are working on different resources they are likely to have a git merge conflict.
We would prefer to have…
6 votesWe are working on enabling support for multiple psm1 files. This will allow you to group different class-based DSC resources into different files.
-
Issue with register-packagesource where adding internal source errors on sourcelocation but successfully adds.
Register-PSRepository -InstallationPolicy trusted -PackageManagementProvider Nuget -Sourcelocation
https://binrepo.target.com/artifactory/api/nuget/powershell-gallery2 -name PSModule_TGT
PackageManagement\Register-PackageSource : The property 'SourceLocation' cannot be found on this object. Verify that
the property exists.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:3281 char:17
+ ... $null = PackageManagement\Register-PackageSource @PSBoundParamete ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : NotSpecified: (Microsoft.Power...erPackageSource:RegisterPackageSource) [Register-Packag
eSource], Exception
+ FullyQualifiedErrorId : PropertyNotFoundStrict,Microsoft.PowerShell.PackageManagement.Cmdlets.RegisterPackageSou
rce
PS C:\Users\vagrant> get-packagesource
Name ProviderName IsTrusted IsRegistered IsValidated Location
PSGalleryTGT PowerShellGet True True False https://binrepo.target.com/ar...
PSModule_TGT PowerShellGet True True False https://binrepo.target.com/ar...23 votesThanks for the updates an input on this item. We are working on a solution, and will update this item when it is publicly available.
-
BUG: Using ConfigurationNames generates a weak certificate
If a Node is configured using a RegistrationKey so that ConfigurationNames can be used, then the CertificateID attribute is ignored under the ConfigurationRepositoryWeb block, and instead a self-signed certificate is generated called "DSC-OaaS".
This certificate is used for both client authentication to the pull server as well as encrypting configuration Mofs at rest on the server host.
The problem is two fold:
Becuase the CertificateID gets ignored when using CONfigurationNames, admins cannot control the key length or encryption of the files.
The certificate generated is a SHA-1 1024bit length. This is completely unacceptable as 1024 went out of use years…
6 votes -
Bug: Get-Module -List throws if an installed module uses Import-Module with $PSScriptRoot
In WMF 5.0 (tested on Win7 w/ KB3134760 and Win10 10240), the presence of certain Import-Module statements in a module in $env:PSModulePath will cause Get-Module -List to throw. In particular, if a module attempts to import another module with a path relative to $PSScriptRoot, it seems to break things. We do this type of thing within psm1s in cases where a manifest cannot express the behavior we need. Here's a repro:
On Win7, using the re-released WMF 5.0 (KB3134760):
PS C:> $PSVersionTable
Name Value
PSVersion 5.0.10586.117
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.10586.117
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion…2 votesHi Matt,
A lot of this code has since been rewritten to fix problems like this. I’m followed your steps very particularly on the latest internal build, and I can’t seem to get it to repro.
I understand you’re using WMF 5 on Windows 7, but if you’ve got a test machine lying around, I highly encourage you to see if the Windows Insider build fixes your problem.
Either way, this should be fixed in a future version of Windows 10 (and potentially WMF as well).
Thanks,
Joey -
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-installationAfter 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
[HKEYLOCALMACHINE\SOFTWARE\Microsoft\Windows\StreamProvider] "LastFullPayloadTime"=dword:00000000allows 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.
9 votesWe will make sure this doesn’t repro with WMF 5.1 release.
-
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 votesWe will make sure this doesn’t repro with WMF 5.1 release.
-
Issue with DSCFileDownloadManager Credentials
So, it seems as though in WMF 5.0 there is a regression in functionality. In WMF 4.0, you could set up a DSCFileDownloadManager and Credential to have a Target Node contact a Pull Server SMB Share and download new mof files and resources. Everything worked perfectly including Certificate based encryption of the credentials. However, in WMF 5, it seems as though the LCM of the Target Node attempts to contact the SMB Share Anonymously, even in credentials are provided. Now, in a Non domain joined environment, you can just provide EVERYONE full control and then change Local Security Policy such…
1 voteThis bug has been identified and the issue has been resolved. The fix will be available in future releases, including the Windows Insider Fast Ring preview
-
Windows PowerShell ISE: Implement a Save All files feature and tie it to Ctrl+Shift+S
Votes from Connect: 18
Original Date Submitted: 6/20/2013 11:40:16 PM
Description:
Contact Information
Handle: deadlydog
Site Name: PowerShell
Feedback ID: 790577
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
It would be great if PS ISE had a "Save All" files feature to save all open, unsaved files. This is considered standard functionality in most IDEs these days, and it is typically bound to the keyboard shortcut Ctrl+Shift+S. Basically the same functionality as Ctrl+S, just iterate over all open, unsaved tabs and do the same.Product Studio item created by Connect Synchronizer due to creation…
14 votesWe’d plan on doing this eventually in a future version of the ISE Preview. Read more about it here: https://blogs.msdn.microsoft.com/powershell/2016/01/20/introducing-the-windows-powershell-ise-preview/
-
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 versionsProblem 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 & ExamplesAn example of a better formatted Find-Module command could be
Find-Module -Command 'SharePoint' and this should return all…
8 votesThe approach we are taking to solve this is to support an addition to PowerShellGet: find-command.
-
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 SUCCESSPS> invoke-command win81 {import-module testme;test-output -verbose}
Test-Output SUCCESS
VERBOSE: Test-Output VERBOSE SUCCESSPS>
2 votes -
Make the ISE Toolbar Extensible via $PSISE
Votes from Connect: 13
Original Date Submitted: 1/19/2012 11:46:28 PM
Description:
Contact Information
Handle: Steve Murawski
Site Name: PowerShell
Feedback ID: 719357
Frequency: Always Happens
Regression: Yes, this happens in previous released versionsProblem Description:
The ISE toolbar has a lot of unused space and there have been suggestions for other items to be added to the toolbar.Could you make the toolbar extensible via the $PSISE variable? This would allow add-on authors to offer toolbar buttons for their extensions.
Product Studio item created by Connect Synchronizer due to creation of feedback ID 719357 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=719357).
Repro Steps:
The…5 votesNo timeline right now, but we do plan on extending the add-on model for the ISE: https://blogs.msdn.microsoft.com/powershell/2016/01/20/introducing-the-windows-powershell-ise-preview/
- Don't see your idea?