ls: File not found exception with wildcard (expression) is not caught in Windows.

Coreutils: 0.0.27 Release
Windows 11 23H2 (OS Build 22631.4169)
Debian 12

Windows:

PS C:\Users\hanbings\test> coreutils ls
a.txt
PS C:\Users\hanbings\test> coreutils ls "a.txtt"
ls: cannot access 'a.txtt': No such file or directory
PS C:\Users\hanbings\test> coreutils ls "a.txtt*"
ls: unknown io error: '"a.txtt*"', 
'Os { 
    code: 123, 
    kind: InvalidFilename, 
    message: "The filename, directory name, or volume label syntax is incorrect." 
}'
PS C:\Users\hanbings\test>

Debian:

root@application:~/test# ./coreutils ls
a.txt  coreutils
root@application:~/test# ./coreutils ls "a.txtt"
ls: cannot access 'a.txtt': No such file or directory
root@application:~/test# ./coreutils ls "a.txtt*"
ls: cannot access 'a.txtt*': No such file or directory
root@application:~/test# ./coreutils ls a.txtt
ls: cannot access 'a.txtt': No such file or directory
root@application:~/test# ./coreutils ls a.txt
a.txt

Start by reproducing the Windows 11 command coreutils ls "a.txtt*" and compare it with the Debian behavior shown in the report. Trace the ls wildcard and file-not-found error handling, then verify that an unmatched wildcard produces the expected no-such-file message on Windows.