Windows10 uwp program custom pairing device which set pin code BLE can not communicate normally?

I use the uwp program to connect and pair BLE (low power Bluetooth module) under win10, reference and test... / windows universal samples master / samples / device enumeration and pairing / CS / scenario 9_ CustomPairDevice Bluetooth custom pairing routine, for classic Bluetooth module and BLE module which do not set pin code, connection pairing is normal, and can communicate normally; for classic Bluetooth module with pin code setted, when connecting and pairing, a dialog box will pop up, after inputting pin code, normal communication can be achieved; but for BLE module with pin code setted, when connecting and pairing, no dialog box will pop up and prompt that the connection is successful, but communication is unnormal. Tracking found that the parameter pairing request processing function pairingrequestedhandler, pairingkind variable in devicepairingrequested EventArgs, is always "confirmonly" for ble modules, and it should be "providepin" for ble modules with pin code set. In this way, a dialog box will pop up to input pin code. Is this due to the windows10 system and bluetooth driver problem?

In addition, I can search the ble module with pin code in the settings interface of windows 10, Bluetooth and other device pages, select and connect, without prompting the dialog box of pin code input, directly prompt to connect, but unable to communicate; search and connect classic Bluetooth module with pin code, prompt to input pin code dialog box, after input, the connection is normal and can communicate;

In addition, using android app to connect and test ble Bluetooth module, if there is no pin code, it will be connected directly, and there will be no communication problem; if the pin code is set, a prompt box will pop up to input the password, and the communication will be OK after connection. It shows that BLE module has no problem.

That is to say, there is no problem connecting the ble device with pin code under Android, but there is a problem under Windows 10.