.
My PowerShell updated to the brand-new PowerShell 7.2.0 and it occurred instantly considering that I get PowerShell from the Windows Shop Nevertheless, my expensive timely usage PSReadLine with Predictive Autocomplete quit working unexpectedly.
Nevertheless, unexpectedly I began getting this mistake on every timely.
Might not pack type 'System.Management.Automation.Subsystem.PredictionResult' from assembly 'Microsoft.PowerShell.PSReadLine.Polyfiller, Variation= 1.0.0.0, Culture= neutral, PublicKeyToken= null'.
at Microsoft.PowerShell.PSConsoleReadLine.PredictionViewBase.Reset()
at Microsoft.PowerShell.PSConsoleReadLine.PredictionInlineView.Reset()
at Microsoft.PowerShell.PSConsoleReadLine.Prediction.Reset()
at Microsoft.PowerShell.PSConsoleReadLine.Initialize( Runspace runspace, EngineIntrinsics engineIntrinsics)
at Microsoft.PowerShell.PSConsoleReadLine.ReadLine( Runspace runspace, EngineIntrinsics engineIntrinsics, CancellationToken cancellationToken)
Well, you can see I’m utilizing a Beta of PSReadLine 2.2:
### Environment
PSReadLine: 2.2.0-beta2
PowerShell: 7.2.0
However I have actually stopped working to keep it approximately date, and when I entered into this state, I understood even if my timely wasn’t quite (for a little while) I might upgrade it with one line while still remaining on the Beta Train.
Install-Module PSReadLine -AllowPrerelease -Force
Now I’m on 2.2.0-beta4 and all is well and I have my cool forecast history back!
Sponsor: Couchbase Capella DBaaS is versatile, full-featured and completely handled with integrated gain access to by means of K/V, SQL and complete text search. It’s blazing quickly, yet remarkably cost effective. Attempt Capella today free of charge
.
.
.
.
About Scott
Scott Hanselman is a previous teacher, previous Chief Designer in financing, now speaker, expert, dad, diabetic, and Microsoft worker. He is an unsuccessful comic, a cornrower, and a book author.
.
.
.
.
.
.
.
.
.