Windows 10: Powershell bug reporting

Hi - unfortunately feedback hub is disabled at my work so I can't report this directly, but if someone can report if for me?




Consider the following really simple code:

Try {
Copy-Item -Path '\\server\g$\thisfolder\thisfiledoesntexist.ini' -Destination 'c:\temp' -ErrorAction Stop
}
Catch {
"Ran into an issue: $_"
}

This will work fine to trap the error for a non-existent source file. However the following will not - there's no error generated.

Try {
Copy-Item -LiteralPath '\\?\UNC\server\g$\thisfolder\thisfiledoesntexist.ini' -Destination 'c:\temp' -ErrorAction Stop
}
Catch {
"Ran into an issue: $_"
}

However...this WILL trap the error

Try {
Get-ChildItem -LiteralPath '\\?\UNC\server\g$\thisfolder\thisfiledoesntexist.ini' -ErrorAction Stop | Copy-Item
}
Catch {
"Ran into an issue: $_"
}

:)

 

How or where to report Windows / PowerShell bug

Hi,

unfortunately there is no publicly accessible way to report a bug. One may only sent feedback.

But few of us have access to bug reports so it is possible to enter bug if you'll clearly describe a step-by-step bug reproducing.

 

How or where to report Windows / PowerShell bug

Is there a publically accessible point where feedback / bugs can be reported relating to Windows / PowerShell? Can't use Feedback Hub as its blocked by our organisation's policies...

Bug relates to PowerShell not able to open scripts if certain characters are in the folder path as it doesn't escape them correctly...

 

PowerShell instead of Commandline in Creators Update

Interestingly enough my personal laptop just got the update...and still has Command Prompt listed, not PowerShell...

Edit: Not that it matters...I use both regularly. *Toast :toast: