ERROR: Could not parse display id: [mDisplayId

[ksgwxfan]

I think this used to work a few years ago for me; even on this same laptop I'm using. But FWIW, it is a different (newer) phone. It has Android 13 and my older phone had A11

But when I attempt to run this (using the powershell), I get the following output (with error):

[ startscreen.ps1 ]: Binary (adb) found in bin folder.
[ startscreen.ps1 ]: Binary (scrcpy) found in bin folder.
[ startscreen.ps1 ]: Waiting for a device...
[ startscreen.ps1 ]: Automatic screen resolution doesnt work thanks to powershell being bad
[ startscreen.ps1 ]: Automatic screen dpi doesnt work thanks to powershell being bad
scrcpy 2.4 <https://github.com/Genymobile/scrcpy>
ERROR: Could not parse display id: [mDisplayId
payload/stage1.sh: 1 file pushed, 0 skipped. 2.4 MB/s (881 bytes in 0.000s)
payload/stage2.sh: 1 file pushed, 0 skipped. 2.8 MB/s (1247 bytes in 0.000s)

Id     Name            PSJobTypeName   State         HasMoreData     Location             Command
--     ----            -------------   -----         -----------     --------             -------
1      ConnectionSt... BackgroundJob   Running       True            localhost            ...
[ startscreen.ps1 ]: -----------------------------------------------------
[ startscreen.ps1 ]: |                                                   |
[ startscreen.ps1 ]: |  Please unlock the phone once the screen appears  |
[ startscreen.ps1 ]: |                                                   |
[ startscreen.ps1 ]: -----------------------------------------------------
[ startscreen.ps1 ]: SCRCPY ended unexpectedly. Ending...


PS C:\scrcpy-desktop-main> Unknown input method com.wparam.nullkeyboard/.NullKeyboard cannot be enabled for user #0
Unknown input method com.wparam.nullkeyboard/.NullKeyboard cannot be selected for user #0

It gives an error that it could not parse the display ID.

Any ideas?

Things I tried:

• Ran Powershell as an administrator
• Tried 32-bit and 64-bit versions of scrcpy (and multiple versions: v2.1.1.1 and v2.4)

Thanks in advance for any possible remedies