Hi there

I've never used the powershell very much. Today I discovered this graphical bug in the rendering of the console text output:
https://i.imgur.com/H40F15W.png
This bug was very confusing at first. Then it just kept getting more irritating.
The bug appears when I scroll up and down, at the bottom of the window. Sometimes text gets cut off at the sides too, but only if I change the window width.
I think I remember I had similiar issues years ago on a different computer.

I couldn't find anything related on google. Maybe I used the wrong search terms?

Although totally unrelated: Please unblock icw-mss setting in tcp for atleast one profile. (Doesn't hurt to keep pressing this)

I've tried putting my commands in an exe module, but could not get this module loaded in PowerShell.

1) If I try to load my module as-is, e.g. an .exe file I get "The extension '.exe' is not a valid module extension. "

2) If I create a .psd1 manifest and put RootModule = 'MyModule.exe' there I get Object reference not set to an instance of an object.
at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleNamedInManifest(PSModuleInfo parentModule, ModuleSpecification moduleSpecification, String moduleBase, Boolean searchModulePath, String prefix, SessionState ss, ImportModuleOptions options, ManifestProcessingFlags manifestProcessingFlags, Boolean loadTypesFiles, Boolean loadFormatFiles, Object privateData, Boolean& found, String shortModuleName, Nullable`1 manifestLanguageMode)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleManifest(String moduleManifestPath, ExternalScriptInfo manifestScriptInfo, Hashtable data, Hashtable localizedData, ManifestProcessingFlags manifestProcessingFlags, Version minimumVersion, Version maximumVersion, Version requiredVersion, Nullable`1 requiredModuleGuid, ImportModuleOptions& options, Boolean& containedErrors)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModule(PSModuleInfo parentModule, String fileName, String moduleBase, String prefix, SessionState ss, Object privateData, ImportModuleOptions& options, ManifestProcessingFlags manifestProcessingFlags, Boolean& found, Boolean& moduleFileFound)
at Microsoft.PowerShell.Commands.ImportModuleCommand.ImportModule_LocallyViaName(ImportModuleOptions importModuleOptions, String name)
at Microsoft.PowerShell.Commands.ImportModuleCommand.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()

Only Parallel, Queue, and IgnoreNew are supported right now. One would expect that the option available from the Task Scheduler GUI would be available in the powershell interface.

Steps to reproduce

$a = New-ScheduledTaskSettingsSet -MultipleInstances StopExisting

Expected behavior

The task's multiple instances policy is set to kill existing tasks before starting another instance.
Actual behavior

value "StopExisting" to type "Microsoft.PowerShell.Cmdletization.GeneratedTypes.ScheduledTask.MultipleInstancesEnum".
Error: "Unable to match the identifier name StopExisting to a valid enumerator name. Specify one of the following
enumerator names and try again:
Parallel, Queue, IgnoreNew"
At line:1 char:131
+ ... ngOnBatteries -ExecutionTimeLimit $b -MultipleInstances StopExisting
+ ~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [New-ScheduledTaskSettingsSet], ParameterBindingArgumentTransformationE
xception
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,New-ScheduledTaskSettingsSet

According to this question on stackoverflow, it has been reported, but Microsoft Connect no longer is alive, so I couldn't follow the bug. Google searching powershell bug report brought me here, not sure if it's the right place though.

When passing a hashtable to a function parameter that expects a PSCustomObject, PowerShell does not fully convert the hashtable to a PSCustomObject type.

function Test-1 {
param(
[PSCustomObject] $Foo
)

Write-Host "`$Foo's type is: $( $Foo.GetType().Name )" -Fore Green
Write-Host "`$Foo is a PSCustomObject: $( $Foo -is [PSCustomObject] )" -Fore Green
Write-Host "`$Foo has these properties:" -Fore Green

foreach ($prop in ($Foo | Get-Member -MemberType NoteProperty| Select -ExpandProperty Name))
{
Write-Host "`t$prop" -Fore Green
}
}

PS C:\Users\dabelc> Test-1 -Foo ( @{ "CustomProp" = "Value" } )
$Foo's type is: Hashtable
$Foo is a PSCustomObject: True
$Foo has these properties:

PS C:\Users\dabelc> Test-1 -Foo ( [PSCustomObject] @{ "CustomProp" = "Value" } )
$Foo's type is: PSCustomObject
$Foo is a PSCustomObject: True
$Foo has these properties:
CustomProp

SCENARIO
On Machine1:
SCHTASKS /Create /RU SYSTEM /SC ONSTART /TN "Map I drive" /TR "net use I: \\someServer\someShare somePassword /user:someDomain\someUser"

On Machine2 run:
$Script = { Write-Output "Hello world!" }
Invoke-Command -ComputerName Machine1 -ScriptBlock $Script

As a result you get "Hello world!" but also an error
"Attempting to perform the InitializeDefaultDrives operation on the 'FileSystem' provider failed."

The error belongs to I drive which should have been returned as a warning and not error. The invoke does not even use the I drive so why fail on it (we in this case dont even want the invoke to have access to the I drive why using credssp is not a solution)

OUR REQUEST
Dont return FileSystem errors (for at least network drives) as errors, but warning/Information.

COMMENT
The command runs perfect locally on Machine1 and can list drives with [System.IO.DriveInfo]::getdrives() which shows the I drive is not ready from remote (and we dont want it to be either).

I am grateful for the addition of classes in PS, and I know why PowerShell classes do not support true data hiding, but it is a significant shortcoming. It does not allow full control of setting a property for example. I can write my own class method for setting it, but it can be changed outside of that method. And if that method also updates the value of another class property, it can get changed directly, without going through the desired logic so the class method can be bypassed.
And it is nice to have the get_ and set_ automatically defined for class properties, but at times I want to disallow a set_ and I am unable to do so (as far as I can tell). If there is a way to do so already, please let me know.
So I would like hidden to be hidden or a private attribute or whatever. Without it, we are reduced to a somewhat cleaner bit of procedural programming.

The following codes were extracted to test a simple $arrayName += $NewObject code that kept replacing the entire array with each new $NewObject.
# *** START
$dataArray = @() # Array to store data
$outputProperty = @{
Hostname = $Null
IPv4 = $Null
MAC = $Null
MACDesc = $Null
}

$dataObject = New-Object -TypeName PSObject -Property $outputProperty

$dataObject.Hostname = 'Computer 1'
$dataObject.IPv4 = '111.111.111.1111'
$dataObject.MAC = '11:11:11:11:11:11'
$dataObject.MACDesc = 'NIC 1'

"Content of dataObject: $dataObject"
# Line 1 **********
$dataArray += $dataObject
"Content of dataArray: $dataArray"

$dataObject.Hostname = 'Computer 2'
$dataObject.IPv4 = '222.222.222.222'
$dataObject.MAC = '22:22:22:22:22:22'
$dataObject.MACDesc = 'NIC 2'

"Content of dataObject: $dataObject"
# Line 2 **********
$dataArray += $dataObject
"Content of dataArray: $dataArray"
# *** END

# ********** Problem Reporting **********
# Problem reporting
# Line 1 and Line 2
$dataArray += $dataObject
$dataArray += $dataObject
# Script ran $dataArray is empty
# OUTPUT: No error and didn't work
Content of dataObject: @{MAC=11:11:11:11:11:11; Hostname=Computer 1; IPv4=111.111.111.1111; MACDesc=NIC 1}
Content of dataArray:
Content of dataObject: @{MAC=22:22:22:22:22:22; Hostname=Computer 2; IPv4=222.222.222.222; MACDesc=NIC 2}
Content of dataArray:

# ********** Problem Reporting **********
# Minor code change in Line 1 [result in error message]
# Line 1 and Line 2
$dataArray = $dataObject
$dataArray += $dataObject
# OUTPUT: Error message
Content of dataObject: @{MAC=11:11:11:11:11:11; Hostname=Computer 1; IPv4=111.111.111.1111; MACDesc=NIC 1}
Content of dataArray: @{MAC=11:11:11:11:11:11; Hostname=Computer 1; IPv4=111.111.111.1111; MACDesc=NIC 1}
Content of dataObject: @{MAC=22:22:22:22:22:22; Hostname=Computer 2; IPv4=222.222.222.222; MACDesc=NIC 2}
Method invocation failed because [System.Management.Automation.PSObject] does not contain a method named 'op_Addition'.
At line:28 char:1
+ $dataArray += $dataObject
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (op_Addition:String) [], RuntimeException
+ FullyQualifiedErrorId : MethodNotFound

Content of dataArray: @{MAC=22:22:22:22:22:22; Hostname=Computer 2; IPv4=222.222.222.222; MACDesc=NIC 2}

# ********** Problem Reporting **********
# Minor code change in Line 2 [result in no error message]
$dataArray += $dataObject
$dataArray = $dataObject
# OUTPUT: It ran, inconsistent output - Notice the empty $dataArray
Content of dataObject: @{MAC=11:11:11:11:11:11; Hostname=Computer 1; IPv4=111.111.111.1111; MACDesc=NIC 1}
Content of dataArray:
Content of dataObject: @{MAC=22:22:22:22:22:22; Hostname=Computer 2; IPv4=222.222.222.222; MACDesc=NIC 2}
Content of dataArray: @{MAC=22:22:22:22:22:22; Hostname=Computer 2; IPv4=222.222.222.222; MACDesc=NIC 2}