Get-PSReadLineOption : The type initializer for 'Microsoft.PowerShell.PSConsoleReadLine' threw an exception.

[LaurentDardenne]

Environment data

& {
    "PS version: $($PSVersionTable.PSVersion)"
    "PSReadline version: $((Get-Module PSReadline).Version)"
    if ($IsLinux -or $IsOSX) {
        "os: $(uname -a)"
    } else {
        "os: $((dir $env:SystemRoot\System32\cmd.exe).VersionInfo.FileVersion)"
    }
    "PS file version: $((dir $pshome\pwsh.exe).VersionInfo.FileVersion)"
}

PS version: 6.0.0-rc.2
PSReadline version: 2.0.0
os: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
PS file version: 6.0.0

$PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.0.0-rc.2
PSEdition                      Core
GitCommitId                    v6.0.0-rc.2
OS                             Microsoft Windows 6.1.7601 S
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0, 5.0, 5.1.10032.0, 6.0.0-rc.2}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Steps to reproduce or exception report

Get-PSReadLineOption

Get-PSReadLineOption : The type initializer for 'Microsoft.PowerShell.PSConsoleReadLine' threw an exception.
At line:1 char:1
+ Get-PSReadLineOption
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Get-PSReadLineOption], TypeInitializationException
+ FullyQualifiedErrorId : System.TypeInitializationException,Microsoft.PowerShell.GetPSReadLineOption

Get-PSReadLineKeyHandler

Get-PSReadLineKeyHandler : The type initializer for 'Microsoft.PowerShell.PSConsoleReadLine' threw an exception.
At line:1 char:1
+ Get-PSReadLineKeyHandler
+ ~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Get-PSReadLineKeyHandler], TypeInitializationException
+ FullyQualifiedErrorId : System.TypeInitializationException,Microsoft.PowerShell.GetKeyHandlerCommand

note : the issue template dont reference 'pwsh.exe'

[lzybkr]

It looks like you built PSReadLine yourself - can you try with beta1 from the PSGallery?

And if that doesn't repro, but it does repro with the latest, do let me know.

I've done minimal testing on Win7 and haven't seen this. I have also done some testing with the "legacy" console on Win10 (from the console properties menu, on the Options tab, select "Use legacy console (requires relaunch)" - that option tends to help behavior specific to pre-Win10 systems.

[LaurentDardenne]

can you try with beta1 from the PSGallery?
This version comes from PSGallery, via Install-Module.
I can test again on Win7 and on a new VM with Server 2016.

[lzybkr]

Thanks - I updated the issue template so the script now reports the prerelease version properly and also checks pwsh.exe.

[LaurentDardenne]

Same error on Windows 7 (via Install-Module)

Same error on Windows Server 2016 :
New Azure VM : Windows Server 2016 Datacenter - with Containers

Install PowerShell-6.0.0-win-x64.msi

PS C:\Program Files\PowerShell\6.0.0> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.0.0
PSEdition                      Core
GitCommitId                    v6.0.0
OS                             Microsoft Windows 10.0.14393
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

PS C:\Program Files\PowerShell\6.0.0> get-module

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Manifest   3.1.0.0    Microsoft.PowerShell.Management     {Add-Content, Clear-Content, Clear-Item, Clear-ItemPropert...
Manifest   3.1.0.0    Microsoft.PowerShell.Utility        {Add-Member, Add-Type, Clear-Variable, Compare-Object...}
Script     1.1.7.0    PackageManagement                   {Find-Package, Find-PackageProvider, Get-Package, Get-Pack...
Script     1.6.0      PowerShellGet                       {Find-Command, Find-DscResource, Find-Module, Find-RoleCap...
Script     1.2        PSReadLine                          {Get-PSReadlineKeyHandler, Get-PSReadlineOption, Remove-PS...


PS C:\Program Files\PowerShell\6.0.0> install-module psreadline -verbose -force -SkipPublisherCheck  -AllowPrerelease
...
VERBOSE: InstallPackageLocal' - name='PSReadLine', version='2.0.0-beta1',destination='C:\Users\Laurent\AppData\Local\Temp\2\1222363818'
VERBOSE: Skipping the Publisher check for the version '2.0.0' of module 'PSReadLine'.
VERBOSE: Module 'PSReadLine' was installed successfully to path 'C:\Program Files\PowerShell\Modules\PSReadLine\2.0.0'.

#Close pwsh.exe
#run pwsh.exe 
PS C:\Program Files\PowerShell\6.0.0> get-module

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     2.0.0      PSReadLine                          {Get-PSReadLineKeyHandler, Get-PSReadLineOption, Remove-PS...


PS C:\Program Files\PowerShell\6.0.0> dir 'C:\Program Files\PowerShell\Modules\PSReadLine\2.0.0'


    Directory: C:\Program Files\PowerShell\Modules\PSReadLine\2.0.0


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----        1/17/2018  11:27 AM                en-US
-a----        12/5/2017  11:22 PM          14164 Changes.txt
-a----        12/5/2017  11:22 PM           1322 License.txt
-a----        12/5/2017  11:22 PM         249856 Microsoft.PowerShell.PSReadLine2.dll
-a----        12/5/2017  11:22 PM           8770 PSReadLine.format.ps1xml
-a----        12/5/2017  11:22 PM            869 PSReadLine.psd1
-a----        12/5/2017  11:22 PM            180 PSReadLine.psm1
-a----        12/5/2017  11:22 PM          21379 SamplePSReadLineProfile.ps1
-a----        12/5/2017  11:22 PM          33256 System.Runtime.InteropServices.RuntimeInformation.dll

PS C:\Program Files\PowerShell\6.0.0> Get-PSReadLineOption
Get-PSReadLineOption : The type initializer for 'Microsoft.PowerShell.PSConsoleReadLine' threw an exception.
At line:1 char:1
+ Get-PSReadLineOption
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Get-PSReadLineOption], TypeInitializationException
+ FullyQualifiedErrorId : System.TypeInitializationException,Microsoft.PowerShell.GetPSReadLineOption

[tobiasdiez]

I've the same issue after a upgrade of Windows 10 (insider preview). I'm not aware that I've installed PSReadLine so I think that it comes bundled with Win 10 (in fact, I cannot remove it via Remove/Uninstall-Module)

 Name                           Value
----                           -----
PSVersion                      6.1.0-rc.1
PSEdition                      Core
GitCommitId                    6.1.0-rc.1
OS                             Microsoft Windows 10.0.17744
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

PSReadLine version: 2.0.0

[KurtDeGreeff]

I have the same issue here on Windows 7 with latest Powershell 6.1 installed :

[KurtDeGreeff]

Get-PSReadLineOption : The type initializer for 'Microsoft.PowerShell.PSConsoleReadLine' threw an exception.
At line:1 char:1

• Get-PSReadLineOption
• CategoryInfo : NotSpecified: (:) [Get-PSReadLineOption], TypeInitializationException
• FullyQualifiedErrorId : System.TypeInitializationException,Microsoft.PowerShell.GetPSReadLineOption

[RobertSpir]

Same thing happens in latest win10 1809 insider build (build 17763.1) which will likely be the RTM build, any of the PSReadline commands throws an exception making it entirely useless

PS version: 5.1.17763.1
PSReadline version: 2.0.0-beta2
os: 10.0.17763.1 (WinBuild.160101.0800)
PS file version: 10.0.17763.1 (WinBuild.160101.0800)

Get-PSReadLineOption : The type initializer for 'Microsoft.PowerShell.PSConsoleReadLine' threw an exception.
At line:1 char:1
+ Get-PSReadLineOption
+ ~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-PSReadLineOption], TypeInitializationException
    + FullyQualifiedErrorId : System.TypeInitializationException,Microsoft.PowerShell.GetPSReadLineOption

[lzybkr]

@RobertSpir - I'll need some help tracking this down, I'm always using the latest and never hit this problem.

A memory dump or time trace debug trace would be very helpful if you don't have time to investigate yourself.

[RobertSpir]

Set-PSDebug -Trace 2; Get-PSReadLineOption
DEBUG:    1+ Set-PSDebug -Trace 2;  >>>> Get-PSReadLineOption
DEBUG:   19+                                         if ( &  >>>> { Set-StrictMode -Version 1; $_.PSMessageDetails } )
{
DEBUG:     ! CALL function '<ScriptBlock>'
DEBUG:   19+                                         if ( & {  >>>> Set-StrictMode -Version 1; $_.PSMessageDetails } )
{
DEBUG:   19+                                         if ( & { Set-StrictMode -Version 1;  >>>> $_.PSMessageDetails } )
{
DEBUG:    1+ &  >>>> { Set-StrictMode -Version 1; $this.Exception.InnerException.PSMessageDetails }
DEBUG:     ! CALL function '<ScriptBlock>'
DEBUG:    1+ & {  >>>> Set-StrictMode -Version 1; $this.Exception.InnerException.PSMessageDetails }
DEBUG:    1+ & { Set-StrictMode -Version 1;  >>>> $this.Exception.InnerException.PSMessageDetails }
DEBUG:    1+ & { Set-StrictMode -Version 1; $this.Exception.InnerException.PSMessageDetails  >>>> }
DEBUG:   19+                                         if ( & { Set-StrictMode -Version 1; $_.PSMessageDetails  >>>> } )
{
DEBUG:   26+                                         $errorCategoryMsg = &  >>>> { Set-StrictMode -Version 1;
$_.ErrorCategory_Message }
DEBUG:     ! CALL function '<ScriptBlock>'
DEBUG:   26+                                         $errorCategoryMsg = & {  >>>> Set-StrictMode -Version 1;
$_.ErrorCategory_Message }
DEBUG:   26+                                         $errorCategoryMsg = & { Set-StrictMode -Version 1;  >>>>
$_.ErrorCategory_Message }
DEBUG:   26+                                         $errorCategoryMsg = & { Set-StrictMode -Version 1;
$_.ErrorCategory_Message  >>>> }
DEBUG:   42+                                         $originInfo = &  >>>> { Set-StrictMode -Version 1; $_.OriginInfo
}
DEBUG:     ! CALL function '<ScriptBlock>'
DEBUG:   42+                                         $originInfo = & {  >>>> Set-StrictMode -Version 1; $_.OriginInfo
}
DEBUG:   42+                                         $originInfo = & { Set-StrictMode -Version 1;  >>>> $_.OriginInfo
}
DEBUG:   42+                                         $originInfo = & { Set-StrictMode -Version 1; $_.OriginInfo  >>>>
}
Get-PSReadLineOption : The type initializer for 'Microsoft.PowerShell.PSConsoleReadLine' threw an exception.
At line:1 char:23
+ Set-PSDebug -Trace 2; Get-PSReadLineOption
+                       ~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-PSReadLineOption], TypeInitializationException
    + FullyQualifiedErrorId : System.TypeInitializationException,Microsoft.PowerShell.GetPSReadLineOption

this happens on all three machines that are upgraded to 17763

[RobertSpir]

downgrading to 1.2 fixed this issue

[lzybkr]

Unfortunately the PowerShell debug trace isn't useful because PSReadLine is written in C#.

Ideally I could get a TTD trace, but I could probably also debug from a memory dump.

Note that if you can provide either - they both could contain secrets, e.g. all of your environment variables. Also note that either method will produce very large files, probably too large to email. If you can collect either the .run file form TTD or the .dmp file from .dump, then I can set up a secure location to share the file - you can email me or PM on twitter, whatever works for you.

[lzybkr]

@RobertSpir provided a TTD trace and I think I understand the issue now.

Can folks hitting this report back what keyboard layout or language you use?

[copdips]

@lzybkr,

Thx for your tips, when I'm on french layout, I have the issue. I switch the keyboard layout to english, no more issue.

[tobiasdiez]

The keyboard layout seems to be the issue, indeed. When using NEO 2.0 (special German layout) I experience the problem but switching to the ordinary built-in German layout fixes it (until switching back). Thanks for having a look at this!