Launching PowerShell after Upgrading from PowerShell v7.1.5 to PowerShell v7.2.0 Generates Error

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

Launching PowerShell after Upgrading from PowerShell v7.1.5 to PowerShell v7.2.0 Generates Error - Could not load type ‘System.Management.Automation.Subsystem.PredictionResult’ from assembly ‘Microsoft.PowerShell.PSReadLine.Polyfiller, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’.

Expected behavior

Prompt without error.

Actual behavior

Error:

Oops, something went wrong.
Please report this bug with ALL the details below, including both the 'Environment' and 'Exception' sections.
Please report on GitHub: https://github.com/PowerShell/PSReadLine/issues/new?template=Bug_Report.md
Thank you!

Error details

Oops, something went wrong.
Please report this bug with ALL the details below, including both the 'Environment' and 'Exception' sections.
Please report on GitHub: https://github.com/PowerShell/PSReadLine/issues/new?template=Bug_Report.md
Thank you!

### Environment
PSReadLine: 2.2.0-beta1
PowerShell: 7.2.0
OS: Microsoft Windows 10.0.22000
BufferWidth: 120
BufferHeight: 9001

Last 0 Keys

Exception

System.TypeLoadException: Could not load type 'System.Management.Automation.Subsystem.PredictionResult' from assembly 'Microsoft.PowerShell.PSReadLine.Polyfiller, Version=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)

### Environment data

```powershell
Unable to run command.

Visuals

No response

[Shigbeard]

1. Open an Powershell session in Administrator privilege

2. Run `Remove-Module PSReadLine` to remove the auto-loaded PSReadLine module.

3. Run `Import-Module PSReadLine` (use PSReadLine with capital L)

4. Then run `Update-Help -Module PSReadLine -Force`

source : https://devblogs.microsoft.com/powershell/updating-help-for-the-psreadline-module-in-windows-powershell-5-1/

This doesn’t work, you’re just reimporting the same PSReadLine module. In place of Step 3, instead of running Import-Module, run Install-Module -Name PSReadLine -RequiredVersion 2.2.0-beta4 -AllowPrerelease as this explicitly specifies the latest version of PSReadLine to install (At least at the time of writing)

After this, it’s safe to import the module again. This is what fixed it for me.

reference : https://www.powershellgallery.com/packages/PSReadLine/2.2.0-beta4

[ghost]

Am I the only one that thinks this is crazy? Why couldn’t the MSI do this automatically?