Dynamic param is silently ignored, and no errors are thrown when CmdletBinding is not defined.

[CmdletBinding()]
Param()

The following code should either run successfully, or throw an error:

Function Add-Control() {
DynamicParam {
$ParamAttribute = New-Object Parameter
$ParamAttribute.Mandatory = $true
$ParamAttribute.ParameterSetName = '__AllParameterSets'

$AttributeCollection = New-Object System.Collections.ObjectModel.Collection[System.Attribute]

$AttributeCollection.Add($ParamAttribute)

$controlTypes = @("TextBox", "Label", "DataGrid")

$AttributeCollection.Add((New-Object ValidateSet($controlTypes)))

$RuntimeParam = New-Object System.Management.Automation.RuntimeDefinedParameter('Type', [string], $AttributeCollection)

$RuntimeParamDictionary = New-Object System.Management.Automation.RuntimeDefinedParameterDictionary

$RuntimeParamDictionary.Add('Type', $RuntimeParam)

return $RuntimeParamDictionary
}

Process {
Write-Host ($PSBoundParameters['Type'])
}
}

Add-Control -Type "Test"
# $null

Note: This may ultimately require resolution in the .NET framework.

Recent versions of Windows 10 support mixed culture values such as `en-DE` (sic) (since version 1703 - see https://msdn.microsoft.com/en-us/library/cc233982.aspx)

After using, e.g., `Set-Culture en-DE` to set the culture for future PowerShell sessions (which in itself succeeds, as you can verify at registry location [HKEY_CURRENT_USER\Control Panel\International]), subsequent PowerShell sessions quietly fall back onto culture 'en-US', as reflected in $PSCulture and [cultureinfo]::CurrentCulture.

Note that such a mixed culture *is* honored in PowerShell *Core*.

Anaconda (Python Environments) Syntax Support

Setup group policy to enable PowerShell Transcripting. From a machine that has that policy applied, launch ADAC. The error "Cannot connect to any domain. Refresh or try again when connection is available." pops up and ADAC can't be used.

https://github.com/PowerShell/PowerShell/issues/3021

Provide a means to specify an alternative Subject Alternative Name in the Certificate request. I have a need for requesting certificates with a specific CN for the subject name and they need to be supplied with a UPN in the subject Alternative Name Field. Currently the only option appears to be a -DNSName flag

This bug may present a low-risk security concern for unaware end users, as reported in openssl here: https://github.com/openssl/openssl/issues/5864
This bug should provide enough detail about the "password paste" problem we were seeing in powershell. In my opinion clipboard text should be able to be pasted (though not visible, as is the case with regular keyboard typing).

When executing the Set-SqlAvailabilityReplica with the -ReadOnlyRoutingList parameter it doesn't update the read only routing list.

If I supply the -script parameter the script is correct.

Bug: Scripts encoded with utf-8 without bom are producing errors when the character "Ä" is used between double quotation marks.

Frequency: always

How to reproduce: Create a powershell file with the following contents:

$test = "Ä"

Save it with the encoding "utf-8 without bom" (often just called utf-8. The counterpart, utf-8 with bom, can also be called "utf-8 signature").

Run the file, and you will get the following error:

At C:\location\to\file\test.ps1:1 char:9
+ $test = "Ä"
+ ~~~~
The string is missing the terminator: ".
+ CategoryInfo : ParserError: (:) [], ParseException
+ FullyQualifiedErrorId : TerminatorExpectedAtEndOfString

Include System.Data.SQLite in PowerShell, so that we have an SQL database engine (SQLite) +ADO.NET provider built in in PowerShell.

See https://system.data.sqlite.org/

Hi,

I just noticed a strange thing. Get-User filter parameter doesn't seem to work when using a variable:

$email = user@domain.com
$dn = (Get-User $email).DistinguishedName
Get-Group -Filter { ManagedBy -eq $dn }

This returns a bunch of groups that has nothing to do with the user. It works correctly when I specify the DistinguishedName manually, e.g. ManagedBy -eq "CN=User,OU=lalala, ..."

Is this a bug in the cmdlet? Because I know that Get-ADGroup works when I use a variable in the filter.

While running PowerShell script through SQL Agent Job I am getting below error . I am running script through account which has full permission on the path.

The error information returned by PowerShell is: 'Invalid Path: 'D:\'. '. Process Exit Code -1. The step failed.

The below is script :

$backuppath = "D:\MSSQL\BACKUP"

#$destpath = "D:\"

$file =get-childitem -path $backuppath -Filter "Test*.bak" |

where-object { -not $_.PSIsContainer } |

sort-object -Property $_.CreationTime |

select-object -last 1 |Copy-Item -Destination "D:\" -PassThru |
Rename-Item -NewName "Test_new.bak"

Thanks
Manoj

Current specs say -To address is required. This should be changed to "at least one address is required". I consistently, using other SMTP mailers, add all my addresses as BCC, with 'To' and "cc" empty. Everyone then sees only their address in their email. This thwarts a 'Reply All' going somewhere it shouldn't.

This is a standard SMTP option and glaring oversite in PowerShell.

https://github.com/PowerShell/PowerShell/issues/3021

Unable to use PowerShell Transcription with Active Directory Administrative Console (ADAC)