Windows - Changing into directory by omitting `cd` results in instant crash `exit code 0x65`

Describe the bug

I have a symlinked directory, dir_a. If I call cd dir_a, I get directory not found. If I call ./dir_a, my WezTerm terminal closes.
Same thing happens with Windows Terminal Preview:

❯ ./dir_a
thread 'main' panicked at 'internal error: cannot canonicalize known path: Os { code: 1, kind: Uncategorized, message: "Incorrect function." }', crates\nu-cli\src\repl.rs:507:30
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[process exited with code 101 (0x00000065)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

I tried calling the following, and got the following error:

❯ with-env { RUST_BACKTRACE: 1 } { ./dir_a }
Error: nu::shell::external_command

  × External command failed
   ╭─[entry #1:1:1]
 1 │ with-env { RUST_BACKTRACE: 1 } { ./dir_a }
   ·                                  ───┬───
   ·                                     ╰── can't run executable
   ╰────
  help: Access is denied. (os error 5)

Calling the above command but with cd ./dir_a instead results in directory not found.

How to reproduce

1. Create a symlinked directory.
2. Call cd symlinked_dir
3. Get directory not found error
4. Try calling ./symlinked_dir
5. Experience crashing terminal

Expected behavior

I expected to change directory to where the symlink points to.

Screenshots

No response

Configuration

Additional context

I am currently playing around with starship, but the behaviour was consistent before I installed it IIRC.

Reproduce the symlinked-directory commands on Windows, then start at crates/nu-cli/src/repl.rs:507 where the reported panic occurs. Trace how cd and ./dir_a are dispatched, and verify that entering the symlinked directory reports no directory-not-found error and does not crash the terminal.