transports "internal" type credential windows hello PIN pop-up issue

Steps to reproduce the problem

Prepare two Windows PCs. Called PC A and PC B for distinction (both PCs, using WIN1022H2 version)

Go to the webuathn.io site

PC A attempted to register FIDO2 with test_account account.

When registering FIDO2, create credentials with Windows Hello PIN

PC A attempts to authenticate FIDO2 with the "test_account" account to check whether the credentials have been generated normally.

PC B attempted to authenticate FIDO2 with "test_account" account. The Windows Hello PIN input UI is generated, and an error message is generated when entering the PIN, "The operation earner timed out or was not allowed. See: https://www.w3.org/TR/webauthn-2/ #sctn-privacy-considers-client."

Problem Description

Windows Hello PIN Input UI window is provided when attempting FIDO2 authentication on a PCB that does not generate credentials in Windows Hello PIN FIDO2 authentication naturally fails when PIN is entered from the provided Windows Hello PIN input window.

Providing a Windows hello PIN input UI window on a PC that does not have credentials can cause confusion to the user. The user cannot determine if such an error is "authentication fails because there are no valid credentials" or "Is it an RP or FIDO2 server error?"

※ This ISSUE CASE occurs on Windows hello PINs whose transports value is "internal".

All I want is that this kind of TEST CASE does not generate a Windows hello PIN input screen. For example, instead of providing a Windows Hello PIN input UI window during FIDO2 authentication, it provides a Windows Hello Security Key screen.

Incidentally, for macOS on the same TEST CASE, PCs that do not have credentials do not provide the Touch ID input UI.

Additional Data

I already raised the issue through the chromium forum and received the following response.

https://issues.chromium.org/issues/365245827