Windows 10 Crash (0xc000027b) on connect/upgrade (Incompatibility with C++/WinRT 2.0)

[mecoj]

Summary

Fatal crash occurs only on Windows 10 when calling UniBLE.connect() on a paired BLE device. The identical code works perfectly on Windows 11.

This issue does not happen on app start. It occurs when a specific action (like a firmware upgrade) is triggered while already connected to a device.

What Works: Scanning and basic connections work correctly, even on Windows 10.

What Fails: Calling a specific function (e.g., firmware upgrade logic) while connected causes a 100% crash on Windows 10.

Crash Details

Faulting application name: MYAPP.exe
Faulting module name: universal_ble_plugin.dll
Exception code: 0xc000027b (STATUS_INVALID_IMAGE_HASH)
Fault offset: 0x0000000000028394

Description

The app crashes with error code 0xc000027b (STATUS_INVALID_IMAGE_HASH) when attempting to connect to a paired Bluetooth LE device on Windows 10. The same code works perfectly on Windows 11.

Environment

• OS: Windows 10 (Build 19045 and lower)
• Plugin Version: universal_ble: ^0.21.1
• Works on: Windows 11 (Build 22000+)
• Fails on: Windows 10 (all builds)
• Unpackaged Win32 EXE (built with flutter build windows)

Steps to Reproduce

1. Pair a BLE device in Windows Settings (Device shows as "Paired: true")
2. Run Flutter app with universal_ble
3. Scan for devices successfully
4. Attempt to connect to paired device:

   await UniBle.connect(deviceId);

5. App crashes immediately with 0xc000027b

Logs

...

[SUCCESS] BLE scan initiated
[SUCCESS] Device discovered: LS_LOADER_OTA (00:0B:29:00:03:01)
[INFO] Device paired: true
[INFO] Attempting connection...
11:02:57: UniBLE.connect() - bleDevice: 00:0B:29:00:03:01, connected: false
11:02:57: ConnectionLog: Device found

[FATAL] App terminated - no exception caught

[rohitsangwan01]

@mecoj are you able to replicate this on Example app ?

[Silvesterrr]

I have exact same issue but on windows 11. Its running on win version: 25H2 (26200.7171), I cannot run in debug too see more details cause this laptop wont handle it.
It crashes my whole app. Sometimes it does work but sometimes the crush is immidiet
I will try to run example.

[Silvesterrr]

i could not replicate the issue on the example app...

[rohitsangwan01]

@Silvesterrr so Pairing works fine with example app even on Windows 10 for you ?
also you can try the latest version ( from git )

[Silvesterrr]

Im so sorry, I dont have this device any more where this problem was persisted

[mecoj]

A windows 10 test environment is currently unavailable, i cannot run the sample code immediately, i will test on Windows 10 as soon as possible and provide further comments.

I think that the application crashes when attempting to reconnect after a service UUID change. This occurs when the device mode is switched (following a disconnection), even though it is the same physical hardware. Are there any known causes for this behavior?

[mecoj]

I tested the connection using your sample source code and virtual peripheral created with the "nRF Connect for Mobile" app on a Android device.

initially, the connection worked fine. However, after I added a new service UUID to the virtual device, the connection failed. Even if I restart the sample app or toggle the advertiser in nRF Connect off and on, the issue persists, and I keep getting the following logs:
_handleConnectionChange false

[ERROR:flutter/runtime/dart_vm_initializer.cc(40)] Unhandled Exception: UniversalBleException: Code: UniversalBleErrorCode.failed, Message: Unreachable, Details: Unreachable_handleConnectionChange false

[ERROR:flutter/runtime/dart_vm_initializer.cc(40)] Unhandled Exception: UniversalBleException: Code: UniversalBleErrorCode.failed, Message: Unreachable, Details: Unreachable

However, in this case, the app does not actually crash and terminate. Instead, it seems to trigger a breakpoint and just freeze/stop at that point.