It is a bug in the new Windows 11 Terminal. It does not occur in old Windows 10. If your version of Terminal is not fully compatible with Powershell 5.1, you can work around the issue by switching back to the old Powershell console.

https://support.microsoft.com/en-us/windows/command-prompt-and-windows-powershell-for-windows-11-6453ce98-da91-476f-8651-5c14d5777c20

describes the process to do so.