Votes from Connect: 72
Original Date Submitted: 2/23/2011 3:47:03 AM
Handle: Joel Reinford
Site Name: PowerShell
Feedback ID: 646172
Frequency: Always Happens
Regression: Yes, this happens in all previous versions
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).
Internal BugId: 2822173 votes
Tracking 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!
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 parameter4 votes
Given 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
Get-Service -Name $Null returns all services. Expected behavior would be for Name to have ValidateNotNullOrEmpty attribute assigned.4 votes
Because this is technically a breaking change, can you guys provide some data on what kind of scenario this might be impacting for you?
When executing the Get-Winevent cmdlet with only the -MaxEvents parameter specified the cmdlet ends up in an infinite loop spewing errors:
Get-WinEvent -MaxEvents 1
Get-WinEvent : The data is invalid
At line:1 char:9
+ $null = Get-WinEvent -MaxEvents 1
+ CategoryInfo : NotSpecified: (:) [Get-WinEvent], EventLogInvalidDataException
+ FullyQualifiedErrorId : The data is invalid,Microsoft.PowerShell.Commands.GetWinEventCommand
I reproduced this error on PowerShell 5.1 and 4.0 on multiple systems. The behavior I expected was to receive the most recent event from any of the event logs. I feel this error could be prevented by using proper parameter validation.3 votes
Not critical, but definitely annoying. I’ve filed a bug internally.
- Don't see your idea?