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. |
-
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
-
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 -
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.
-
Drag and Drop to upload files to PowerShell ScriptAnalyzer Preview service portal
Drag and drop to upload a zip file with all the powershell scripts (Eg. .ps1, .psd1 and *.psm1 files) just like OneDrive uploading of files.
It will be great if it is possible to drag and drop all the powershell scripts (Eg. .ps1, .psd1 and *.psm1 files) without compressing it to a zip file. The upload will automatically detect multiple PowerShell scripts uploaded and either smart enough to know all the uploaded multiple files are considered as one functional module or zip it up at the server end for processing it as it is functioning now.
1 vote
- Don't see your idea?