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. |
-
Please hide the API Key in the PowerShell Gallery UI
When you log into the PowerShell Gallery, if you click on your username you're taken to your account page. This account page contains your API Key in plain text, visible by default. Since the API Key is the key that is used to publish your modules/scripts to the Gallery, the UI should hide these "keys to the kingdom" by default with an option in the UI to show the Key. I have seen many demos of the Gallery where the API Key is shown when it simply shouldn't be shown at all, simply because the person delivering the demo clicked…
23 votesThanks again for the input everyone! This functionality is now released.
-
Get-Help -Online in 5.0 opens core cmdlet help for 4.0
For the core modules in PowerShell 5.0, Get-Help -Online opens the help for PowerShell 4.0, not for PowerShell 5.0. Typically, -online gets help for the latest version of the module by default.
For example: Get-Help Import-Module -Online
...opens "https://technet.microsoft.com/library/af616c24-e122-4098-930e-1e3ea2080ade(v=wps.630).aspx", the 4.0 version of help.That's because the first related link in the XML help topic has the FWLink for the 4.0 topic.
I suspect this is a bug caused by an incomplete understanding of how -Online works. The tool (or person?) that was supposed to update the links for 5.0 didn't know how it worked and updated only…
15 votesThis should be fixed in 5.0 and 5.1. If not, definitely let us know.
Thanks,
Joey -
Change from edb file to SQL Server database for Desired State Configuration Pull services
Votes from Connect: 6
Original Date Submitted: 4/25/2015 5:54:58 AM
Description:
Contact Information
Handle: Ihadadream
Site Name: PowerShell
Feedback ID: 1275973
Problem Description:
If Pull services databases change to SQL Server, we could have high availability and build a real pull infrastructure. It also brings possibility to have tierce applications that read datas and build reports using SSRS, etc.Product Studio item created by Connect Synchronizer due to creation of feedback ID 1275973 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1275973).
Repro Steps:
Internal BugId: 14408
71 votesThis feature has been shipped in Windows Server 2019. We do not have plans to pack-port the capability to earlier versions of Windows.
-
Install-PackageProvider -Name NuGet not working
Upgraded from WMF 4.0 to WMF 5.0 on Windows 7 SP1 x64 with .NET 4.6.1 and can't get NuGet/OneGet etc. to work at all. Already tried uninstall of WMF 5.0 and reinstall to no avail.
PS T:> Install-PackageProvider -Name NuGet -ForceBootstrap
Install-PackageProvider : Unable to find repository with SourceLocation ''. Please use Get-PSRepository to see all
available repositories.
At line:1 char:1
+ Install-PackageProvider -Name NuGet -ForceBootstrap
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : InvalidArgument: (Microsoft.Power...PackageProvider:InstallPackageProvider) [Install-Pac
kageProvider], Exception
+ FullyQualifiedErrorId : RegisterPackageSourceRequired,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPack
ageProvider
PS T:> Get-PSRepository
PackageManagement\Get-PackageSource : Unable to find module providers (PowerShellGet).
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:3544 char:31
+ ... ckageSources =…2 votesThank you for your patience & persistence on this.
Closing the item now that we understand it.
We do have an update planned for OneGet work item operate with FIPS enabled, as covered in the OneGet issue https://github.com/OneGet/oneget/issues/195 -
Microsoft.PowerShell.Archive module should be open source
The functionality in the Microsoft.PowerShell.Archive module is already human readable (it's just a script module with a manifest). It would be better if this was open source so that pull requests could be submitted against it to make it better (fixing the lack of custom PS drive support, supporting nupkg/other common zip package extensions, downlevel support which is easy to do). Please make it so.
13 votes -
!($a[0]=[psobject]($a=,0))
That command crash PowerShell with StackOverflowException.
2 votesThank you for the bug report!!
-
snippets
PowerShell ISE - Where are the default snippets after Win10 Upgrade?
So I've upgraded to Win10Pro 1803 17134.1, opened my trusty PowerShell ISE, pressed CTRL+J and nothing happens!? Even the Get-ISESnippet is not showing any results. I'm using the default snippets and don't have any custom snippets under my documents / PowerShell folder.
It seems to be related to OneDrive or Windows 10 update as both my Desktop and Laptop have the same problem.
According to JRV the same issue occurs on 1809 builds.
Best Regards,
Glenn$PSVersionTable
Name Value
PSVersion 5.1.17134.1
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0,…103 votesDoing a little cleanup, this has been fixed in the latest cumulative updates of Windows 10
-
Powershell ISE crashes on Ctrl+Space Intellisense
my "Ideas" is Powershell ISE should not crash.
https://github.com/PowerShell/PowerShell/issues/6846
teps to reproduce
Use Windows Powershell ISE on Windows Build 17134
Enter the name of any cmdlet, a dash, then press ctrl+Space.
Get-Help -[Ctrl+Space]
Expected behavior
Should show intellisense popup.
Actual behavior
Instead of an intellisense dropdown, a small dot appears.Messagebox as follows, followed by closing:
Windows PowerShell ISE - Error
An unexpected error has occurred, and Windows PowerShell ISE must close.
OK
Running in the visual studio debugger shows two exceptions, one from Xaml (associated with the appearance of the dot) the other a NullReferenceException which appears to occur…
37 votesDoing a little cleanup, this has been fixed in the latest cumulative updates of Windows 10
-
PowerShell Intellisense Broken on Windows 10 1803
Intellisense is broken after upgrading to Windows 10 1803. Only a single white pixel is displayed.
5 votes[UPDATE] Good news! This has been fixed internally already, and may already be showing up in Windows Insider builds. I don’t have an ETA for when the fix will show up for 1803, but it is on the way.
Hey everyone,
I’ve managed to reproduce this issue on my 1803 box, it’s definitely not awesome. Let me get an investigation going on our side to find out what’s going on.
Thanks,
Joey -
New Verb: Deploy
"Deploy" is a de facto PowerShell verb, as many popular official Azure PowerShell scripts already contain this verb. Considering deployments are a primary scenario for PowerShell, it would be great to add this as an official verb--especially since PSScriptAnalyzer needs to be modified to not flag Azure's official scripts.
2 votesGreat idea! We’ve actually added both Build and Deploy to PowerShell 6.0: https://github.com/PowerShell/PowerShell/issues/3346
-
update-help : Failed to update Help for the module(s) 'Provisioning'
I receive the following error when running Update-Help in PowerShell.
PS C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Provisioning> update-help
update-help : Failed to update Help for the module(s) 'Provisioning' with UI culture(s) {en-US} : Unable to retrieve
the HelpInfo XML file for UI culture en-US. Make sure the HelpInfoUri property in the module manifest is valid or
check your network connection and then try the command again.
At line:1 char:1
+ update-help -force
+ ~~~~~~~~~~~~~~~~~~+ CategoryInfo : ResourceUnavailable: (:) [Update-Help], Exception
+ FullyQualifiedErrorId : UnableToRetrieveHelpInfoXml,Microsoft.PowerShell.Commands.UpdateHelpCommandPowerShell info:
PS C:> $PSVersionTable.PSVersionMajor Minor Build Revision
5 1 15063 138
27 votes -
WMF 5.0 incompatibilities still valid for WMF 5.1?
WMF 5.1 download page has a warning that heads to this site:
https://msdn.microsoft.com/en-us/powershell/wmf/5.0/productincompat
Are the listed incompatibilities still valid for 5.1, as only 5.0 is named here.
1 voteThere have been no changes to the applications that have approved the use of WMF between the 5.0 and 5.1 releases.
-
Dynamic inplace syntax help without ISE
Hi Microsoft,
ever used to program a Switch or Router. Not only at Cisco's you can issue a ? anytime to know what you can do next, instead of browsing each command in technet or completely dump your line to enter get-help ... this is too complicated!ISE is a help but I don't want ISE all the time. Make your "command line" user-friendly please
1 voteStarting in PowerShell 5 (shipped with Windows 10, Windows Server 2016, and WMF 5), we included the PSReadline module by default in powershell.exe for improved usability. Based off of what you’re looking for, I’d highly recommend trying Ctrl+Space to see all available Tab completions wherever you’re at in your expression.
Also check out the PSReadline GitHub repo for more documentation on using all of its available features: https://github.com/lzybkr/psreadline#usage
-
Error in topic about_Pipelines under INVESTIGATING PIPELINE ERRORS
The example command given under "INVESTIGATING PIPELINE ERRORS" in the about_Pipelines help topic is incorrrect. the example situation is moving a registry entry from one key to another, in the example it's trying to move the entry "product" from the hklm:\software\mycompany\design registry key to the hklm:\software\mycompany\sales key. The second ("fixed") command at the end:
get-item -path hklm:\software\mycompany\design |
move-itemproperty -dest hklm:\software\mycompany\design -name productshould be:
get-item -path hklm:\software\mycompany\design |
move-itemproperty -dest hklm:\software\mycompany\sales -name productI also think the source and destination seem switched or misplaced throughout that section of the topic, unrelated to the example error given for the purpose…
1 voteFixed in staging, will show up on live help soon, will show up in get-help upon completion of https://github.com/PowerShell/PowerShell-Docs/issues/1073
-
PowerShell Update-Help download fails for Module Appx-6-15-2017
PowerShell Update-Help download fails for Module Appx-6-15-2017
1 votefixed
-
Invoke-WebRequest should support -NoProxy parameter
Invoke-WebRequest picks up the system proxy defined in Internet Options by default. It also includes parameters -Proxy, -ProxyCredentials and -ProxyUseDefaultCredentials for changing and managing the proxy that it uses.
It would be very useful to have a -NoProxy parameter that forced a direct web connection. Currently, when this is required, the system proxy has to be disabled.
4 votesThis got implemented as part of PowerShell 6 and will part of our next alpha release (6.0.0-alpha.18, likely out in the next day or two): https://github.com/PowerShell/PowerShell/pull/3447
Thanks to @TheFlyingCorpse for the implementation!
-
Private powershell Gallery
Hi Guys,
I'm looking for a solution to manage all my powershell cmdlets.
I want to build something similar to what Microsoft is using when you type get-help cmdlet-name -online
Can anyone advice hot to build such a solution based on private PS galleryRegards
Raf1 voteHi Raf – you seem to be talking about 2 things: setting up an internal PowerShell Gallery, and providing online help.
There’s an article on how to set up an internal PowerShell Gallery (here: https://blogs.msdn.microsoft.com/powershell/2014/05/20/setting-up-an-internal-powershellget-repository/).
The help content is not in the PowerShellGallery.
In the module manifest there is a property called HelpInfoURI, which can specify where to get updatable help from.
The instructions for how to deal with updatable help are in this topic: https://msdn.microsoft.com/en-us/library/hh852735(v=vs.85).aspx -
-format not working with concatenated string
The format (-f) command does not replace a token if the token is in a string followed by another concatenated string, if the -f is executed when the string is defined. Reproduced on PowerShell v4 and v5.
Example:
$concat = "select * from '{0}'" + " stringpart2" -f 'tab1'
$concatResult:
select * from '{0}' stringpart2However if -f is applied after the concatenation, it works correctly.
Example:
$concat = "select * from '{0}'" + " stringpart2"
$concat -f 'tab1'Result:
select * from 'tab1' stringpart21 voteIvan’s comment below is correct
-
Get-ComputerInfo: Property BiosSeralNumber is spelled wrong...should be BiosSerialNumber
Get-ComputerInfo: Property BiosSeralNumber is spelled wrong...should be BiosSerialNumber
4 votesAs indicated in the comments, this has been fixed in 6.0: https://github.com/PowerShell/PowerShell/issues/3166
-
Gallery help site needs new capability
The documentation site need a menu or link item to quickly switch versions of a help topic. Like the old MSDN site.
Example Site topic: https://msdn.microsoft.com/powershell/reference/5.1/Microsoft.PowerShell.Utility/Read-Host
The version access is important for support issues to be able to quickly switch versions as the "-online" with help always targets the current version or nothing.
2 votes
- Don't see your idea?