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. |
-
Out-DataTable
Creates a DataTable based on an objects properties. Useful for converting any Powershell object into a DataTable which then can be bulk imported into a SQL Server table.
.EXAMPLE
$dt = Get-PSDrive | Out-DataTable
This example creates a DataTable from the properties of Get-Alias and assigns output to $dt variableThis idea comes from Chad Miller's Out-DataTable: https://gallery.technet.microsoft.com/scriptcenter/4208a159-a52e-4b99-83d4-8048468d29dd#content
204 votesAfter much discussion with Aaron Nelson and Chrissy LeMaire, and thanks to the enormous amount of support for this item, we’ve recognized that this is something we need to accomplish, one way or another.
We don’t want to offer an ETA on this as the work is not well understood by our team yet, and no one currently has immediate bandwidth on starting that investigation. But I want to stress the fact that is an important ask that we’re taking seriously as a priority.
In the meantime, it would be immensely useful if someone with expertise in the DataTable space could submit an RFC (basically a brief spec) to our PowerShell-RFC repository on GitHub. That way, we can have a discussion about what the design of a ConvertTo-DataTable cmdlet might look like before we dive in on an implementation. The process for doing so is located here: https://github.com/PowerShell/PowerShell-RFC/blob/master/RFC0000-RFC-Process.md#draft
I…
-
Get-Service should return the user account the services are running under
The Get-Service cmdlet should return the service account associated to each service.
We can get this information easily from the Win32_Service WMI class, but to me, it should be returned by Get-Service.
Checked with PS v5 without luck...
Thanks!
186 votesCreated an Issue on GitHub to put this in our backlog: https://github.com/PowerShell/PowerShell/issues/2579
Feel free to continue voting on this item here to drive prioritization.
-
Implement native robocopy cmdlet
Votes from Connect: 72
Original Date Submitted: 2/23/2011 3:47:03 AM
Description:
Contact Information
Handle: Joel Reinford
Site Name: PowerShell
Feedback ID: 646172
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
Powershell needs the full functionality of Robocopy as a cmdlet. Copy-Item has too many limitations and invoking robocopy from Powershell is not an elegant solution.Product Studio item created by Connect Synchronizer due to creation of feedback ID 646172 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=646172).
Repro Steps:
Expected Results:Internal BugId: 2822
176 votesTracking a list of missing robocopy-like functionality in this GitHub Issue: https://github.com/PowerShell/PowerShell/issues/2581
Feel free to continue to vote here, but you’re also welcome to add comments there or even contribute some of the missing functionality!
-
JEA is difficult for delegates to use without tab completion
By default tab completion is disabled in JEA endpoints- and there is no guidance on how (or if) it can be enabled safely.
Without tab completion it is
1. Harder to discover available commands (no Get-<tab>)
2. Harder to execute available commands with correct parameter name spelling etc.
3. Harder to populate correct values (e.g., no help with ValidateSet scenarios)
This all works against the applicability of JEA for delegation scenarios where a less expert sub-admin has to blindly type out a potentially complex and unfamiliar command.
Please make some basic level of tab completion work by default, and please…7 votes -
Windows PowerShell ISE: Add ability to rearrange tabs
Votes from Connect: 17
Original Date Submitted: 6/21/2013 12:41:41 AM
Description:
Contact Information
Handle: deadlydog
Site Name: PowerShell
Feedback ID: 790585
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
It would be nice in PS ISE if when you have multiple files open, that you could drag the tabs at the top of the Script Pane window (i.e. the file names) to rearrange them. Right now if you want to rearrange the order of the tabs, you have to actually close the tabs and re-open them in the order that you want them.This is…
57 votes -
$url = 'http://www.bloomberg.com/professional/downloads/'
I believe I have a bug with Invoke-Webrequest.
$url = 'http://www.bloomberg.com/professional/downloads/'
Invoke-WebRequest -UseBasicParsing -Uri $url "
Or
Invoke-WebRequest $url "
Using invoke-webREquest on that URL Hangs /restarts ISE for me.
I am using powershell 4.0 on windows 7 Sp1 64 bit.
Name : Windows PowerShell ISE Host
Version : 4.010 votesRepros on the latest versions of powershell.exe and ISE. Filing something internally.
-
PowerShell ISE's find dialog should have an option to start over from the beginning of file
Moved over from this connect issue:
10 votes -
add DSC Configuration to Powershell Gallery
Add a category for DSC Configurations in the PowerShell gallery just like scripts can be posted to the gallery
6 votesWe have in plan adding a new filter for “DSCConfiguration”, which will list any module or script with that tag. (Note: case is for readability, only – as usual for PowerShell.) We do not have an ETA, but it is in plan.
Users should be aware that DSC Configurations are scripts, so if they want to see items that are JUST DSC Configurations, they will need to set the filter to show only scripts, not scripts and modules.
As of the time this response is being written, the huge majority of items tagged with DSCCOnfiguration are modules, many of which have sample DSC Configurations included. -
Bug: DSC error when executing configuratin with Set-PSDebug -Strict - "$notAllowedValue cannot be retrieved because it has not been set"
When you execute a configuration .ps1 script with Set-PSDebug -Strict turned on, you get the following error:
PSDesiredStateConfiguration\Node : The variable '$notAllowedValue' cannot be retrieved because it has not been set.
I can work around this by using the following code snippet:
Set-PSDebug -Off
$mofFile = SetPullMode -ComputerName $comp -OutputPath $mofFilePath -ConfigurationId $ConfigurationId -Thumbprint $cert.Thumbprint -PullserverUri $PullServerUri
Set-PSDebug -StrictThis sounds like a scoping issue in DSC somewhere with the notAllowedValue variable.
2 votes -
Notification option for authors when publishing to PS Gallery
When an author publishes an update to their module hosted on the gallery it should provide an option to push a notification to their configured social media accounts.
So an author configures Twitter and LinkedIn profiles on their account/profile. A configuration option within the module being published should allow for a setting that will push a notification to their social media, on their behalf, announcing a new release of that module.
9 votesWe are working to support this, but have no ETA at this time.
-
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 $dirsAnd if you look at the localhost.mof you'll see:
DependsOn = { "[File]CTemp…3 votes -
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 voteRavikanth,
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
-
Powershell on Raspberry pi
add Powershell support for Raspberry Pi devices running Raspbian OS
13 votesWe’re not currently working on this, but the work is being tracked in this GitHub issue: https://github.com/PowerShell/PowerShell/issues/2463
It’s marked as `Up-for-Grabs` to indicate that anyone is welcome to help us implement support for it.
-
BUG: Get-Help Get-Service
In the help file it states that wildcards are not permitted. But it accepts a value with a wildcard on the heads or tails and it also accepts just a wildcard with no other characters.
-Name <String[]>
Specifies the service names of services to be retrieved. Wildcards are permitted. By default, this cmdlet gets all of the services on the computer.
Required? false
Position? 0
Default value None
Accept pipeline input? True (ByPropertyName, ByValue)
Accept wildcard characters? false3 votesCorrect in web help, need https://github.com/PowerShell/PowerShell-Docs/issues/1073 for this to start showing up in Get-Help
-
The description attached to the parameters -Delimiter -Encoding -Raw -Stream -Wait (This parameter is not supported by any providers that ar
This comment pertains to the help entry for Get-Content (https://msdn.microsoft.com/en-us/powershell/reference/5.0/microsoft.powershell.management/get-content) I Tried to enter the feedback into the actual page but my browser reloaded the page and lost the floating feedback link. Perhaps it was already submitted.
The description attached to the parameters
-Delimiter
-Encoding
-Raw
-Stream
-Wait
(This parameter is not supported by any providers that are installed with Windows Powershell.)
is both incorrect and useless.It is incorrect because the parameters are supported by the FileSystem provider (at least).
It is useless because it gives no information about the reason for the existence of the parameter.…
1 voteThanks! I filed an issue to track this: https://github.com/PowerShell/PowerShell-Docs/issues/1101
-
Get-Service throws wrong exception if remote host is offline
Get-Service returns exception as "Cannot find any service with service name" even if we give an offline/not existing host as argument for -ComputerName parameter
4 votesGiven the low impact of the error message, this probably won’t be a high priority for us unless it gains significantly more votes here.
That being said, I went ahead and filed this on our GitHub repository as an `up-for-grabs` issue so that any public contributor can also fix it if they choose to: https://github.com/PowerShell/PowerShell/issues/2747
-
ActiveDirectory PSDrive problem with PSReadline in Windows 10
I am experiencing an issue with Windows 10 and the PSReadline module. Apparently when the PSReadline module is in memory, the default behavior for tab completion is to append a trailing backslash to the relative path. This is not too much of a problem with the file provider and the registry providers but it appears to wreak havoc on the Active Directory PS Provider.
This may be reproduced by navigating to the AD: drive and they trying to use tab completion for the Set-Location or Get-ChildItem cmdlets. You will receive the error Cannot find path because it does not exist.
…
3 votesHi Robert,
Thanks for the report! I went ahead and opened an issue in the PSReadline GitHub repo to track this: https://github.com/lzybkr/PSReadLine/issues/473
I propose that it might be worth it to simply special case PSReadline to not append a trailing backslash while in the AD provider, but I think you should probably also file something on the AD team’s UserVoice to support trailing backslashes (though this work might be more difficult): https://windowsserver.uservoice.com/forums/304621-active-directory
Thanks,
Joey -
Format-* incorrectly format warning objects
Given this:
<#PS#> $a = Write-Warning test 3>&1
PowerShell will incorrectly prepend "WARNING: " to:
<#PS#> $a | ft * -f
WriteWarningStream FullyQualifiedWarningId Message InvocationInfo PipelineIterationInfo
WARNING: True test System.Management.Automation.InvocationInfo {0, 0, 0}
<#PS#> $a | fl * -f
WARNING: WriteWarningStream : True
WARNING: FullyQualifiedWarningId :
WARNING: Message : test
WARNING: InvocationInfo : System.Management.Automation.InvocationInfo
WARNING: PipelineIterationInfo : {0, 0, 0}
WARNING:1 voteThanks, Derp. I think this is a valid bug, so I went ahead and filed it on GitHub to see if our engineers agree: https://github.com/PowerShell/PowerShell/issues/2715
-
Documentation Bug: Wrong Language + Wrong Locale + Wrong HelpInfoUri
Documentation Bug: Wrong Language + Wrong Country + Wrong HelpInfoUri
"Update-Help -Verbose -Force" gives:
Update-Help : Failed to update Help for the module(s)
'Microsoft.PowerShell.Operation.Validation' with UI culture(s) {en-US} : The value of the
HelpInfoUri key in the module manifest must resolve to a container or root URL on a website
where the help files are stored. The HelpInfoUri 'https://www.msn.com/de-de/?ocid=NEFLS000'
does not resolve to a container.
At line:1 char:1
+ Update-Help -Verbose -Force
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : InvalidOperation: (:) [Update-Help], Exception
+ FullyQualifiedErrorId : InvalidHelpInfoUri,Microsoft.PowerShell.Commands.UpdateHelpCommand============================================
But this is the current configuration:
PS C:\WINDOWS\system32> $PSCulture
en-US
PS C:\WINDOWS\system32>…2 votesWe are aware of this issue and working on a fix.
-
Ensure Windows Management Framework can be upgraded from built-in version without multiple upgrades
Currently, when installing WMF5 on Windows 7, there is a pre-req of installing WMF4 first.
Please ensure that all supported operating systems can install the latest version of Windows Management Framework without having to do incremental upgrades. This will significantly reduce the complexity of deployment in production environments and during operating system deployment.
Thanks!
4 votesThis is something the PowerShell Team is working on for WMF 5.1, but we have not yet solved the problem.
- Don't see your idea?