Bluetooth LE connectivity on windows 10 via service discoverdetails does not work on first connect

Seeing an odd issue, only on windows 10 (on linux it works fine) whereby bluetooth LE connectivity (central) seems to get stuck when discovering the details of a service. On the first connect, it just does not work but if I disconnect then reconnect, it works, here is the debug output from the application:

Connected!
Service! {00001801-0000-1000-8000-00805f9b34fb}
Service! {00001800-0000-1000-8000-00805f9b34fb}
Service! {8d53dc1d-1db7-4cd3-868b-8a527460aa84}
Finished!
State: 2
State: 1
finished
State: 0
Disconnected!
Connected!
Service! {00001801-0000-1000-8000-00805f9b34fb}
Service! {00001800-0000-1000-8000-00805f9b34fb}
Service! {8d53dc1d-1db7-4cd3-868b-8a527460aa84}
Finished!
State: 2
State: 3 

What makes no sense, is how can the first state emitted to the stateChanged callback be 2 when this means it is discovering services, but then the state changes to 1 which means discovery is required, this doesn't seem like it should be possible?

The code for this is available at https://github.com/thedjnK/AuTerm/blob/main/plugins/mcumgr/smp_bluetooth.cpp